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

[I18N] *: export source terms

Browse Source 
closes odoo/documentation#4986

Signed-off-by: Martin Trigaux (mat) <mat@odoo.com>
This commit is contained in:
Martin Trigaux 2023-07-03 09:55:25 +00:00
parent f3e3490ba4
commit 11d8c153e2
11 changed files with 4408 additions and 1693 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

76
locale/sources/administration.pot
View File

@ -8,7 +8,7 @@ msgid ""
msgstr ""
"Project-Id-Version: Odoo 16.0\n"
"Report-Msgid-Bugs-To: \n"
"POT-Creation-Date: 2023-06-15 11:45+0000\n"
"POT-Creation-Date: 2023-07-03 09:37+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"
@ -192,7 +192,7 @@ msgstr ""
#: ../../content/administration/install/deploy.rst:58
#: ../../content/administration/install/deploy.rst:153
#: ../../content/administration/install/deploy.rst:276
msgid "in ``/etc/odoo.conf`` set:"
msgid "in :ref:`the configuration file <reference/cmdline/config_file>` set:"
msgstr ""
#: ../../content/administration/install/deploy.rst:53
@ -409,7 +409,7 @@ msgid "RAM = 9 * ((0.8*150) + (0.2*1024)) ~= 3Go RAM for Odoo"
msgstr ""
#: ../../content/administration/install/deploy.rst:241
msgid "in ``/etc/odoo.conf``:"
msgid "in :ref:`the configuration file <reference/cmdline/config_file>`:"
msgstr ""
#: ../../content/administration/install/deploy.rst:257
@ -2158,7 +2158,7 @@ msgid ":doc:`/applications/general/email_communication/email_servers`"
msgstr ""
#: ../../content/administration/maintain/enterprise.rst:6
msgid "Upgrade Community to Enterprise"
msgid "Switch from Community to Enterprise"
msgstr ""
#: ../../content/administration/maintain/enterprise.rst:8
@ -6670,44 +6670,68 @@ msgstr ""
msgid "If you are using the Website or Studio app, we recommend you always do a test upgrade before upgrading your production instance."
msgstr ""
#: ../../content/administration/upgrade/odoo_online.rst:6
msgid "Requesting a test upgrade"
#: ../../content/administration/upgrade/odoo_online.rst:5
msgid "Odoo databases can be manually upgraded directly from the main Odoo website. To upgrade an Odoo database, navigate to the `database manager <https://www.odoo.com/my/databases>`_ page and sign in."
msgstr ""
#: ../../content/administration/upgrade/odoo_online.rst:8
msgid "Go to your `database manager <https://www.odoo.com/my/databases/>`_"
msgid "The database manager page displays all of the Odoo databases associated with the user's account. Any databases that are not already on the most recent version of Odoo display an **arrow in a circle** icon next to the database name, indicating that the database can be upgraded."
msgstr ""
#: ../../content/administration/upgrade/odoo_online.rst:9
msgid "Click on your profile icon and select *My Databases*."
#: ../../content/administration/upgrade/odoo_online.rst:-1
msgid "The database manager page with an upgrade button next to the name of a database."
msgstr ""
#: ../../content/administration/upgrade/odoo_online.rst:0
msgid "Selecting My Databases under my profile"
msgstr ""
#: ../../content/administration/upgrade/odoo_online.rst:14
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
msgid "Selecting the action settings icon"
#: ../../content/administration/upgrade/odoo_online.rst:17
msgid "Test database"
msgstr ""
#: ../../content/administration/upgrade/odoo_online.rst:19
msgid "In the pop-up message that appears, select the target version and then :guilabel:`Test` as purpose."
msgid "Click on the **arrow in a circle** icon to start the upgrade process. On the :guilabel:`Upgrade your database` pop-up, select the version of Odoo that the platform will be upgraded to. In the :guilabel:`Email to notify` field, enter an email address that will receive email notifications about the database upgrade."
msgstr ""
#: ../../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."
#: ../../content/administration/upgrade/odoo_online.rst:24
msgid "There is also a :guilabel:`Purpose` section on the pop-up that is used to specify the reason for the upgrade. However, at this stage of the process, the only selectable option is :guilabel:`Test`, as Odoo requires users to create a test copy of the upgraded database before converting the actual database."
msgstr ""
#: ../../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."
#: ../../content/administration/upgrade/odoo_online.rst:-1
msgid "The \"Upgrade your database\" pop-up."
msgstr ""
#: ../../content/administration/upgrade/odoo_online.rst:30
msgid "You can also see and access your test database from your *My Databases* page."
#: ../../content/administration/upgrade/odoo_online.rst:33
msgid "After filling out the form, click the :guilabel:`Upgrade` button. The pop-up disappears and the database being upgraded shows a red :guilabel:`Upgrade in progress` tag next to its name. An email confirming that the upgrade is in progress is also sent to the email address specified on the pop-up."
msgstr ""
#: ../../content/administration/upgrade/odoo_online.rst:-1
msgid "The \"Upgrade in progress\" tag next to the database name."
msgstr ""
#: ../../content/administration/upgrade/odoo_online.rst:42
msgid "Once the upgrade is complete, a new test database appears on the `database manager <https://www.odoo.com/my/databases>`_ page. To access the test database, click the drop-down arrow (:guilabel:`⯆`) to the left of the main database's name. Doing so makes the test version appear below it. Finally, click the green :guilabel:`Connect` button on the right side of the test version's row to go to the database."
msgstr ""
#: ../../content/administration/upgrade/odoo_online.rst:-1
msgid "A test database on the database manager page."
msgstr ""
#: ../../content/administration/upgrade/odoo_online.rst:52
msgid "Except for being on the newer version of Odoo, the test database is an exact copy of the one being upgraded. It is important to do extensive testing in this database to ensure that the upgrade has not altered or corrupted any data, and that all workflows still proceed as expected."
msgstr ""
#: ../../content/administration/upgrade/odoo_online.rst:57
msgid "Production database"
msgstr ""
#: ../../content/administration/upgrade/odoo_online.rst:59
msgid "After confirming the integrity of the new version, return to the `database manager <https://www.odoo.com/my/databases>`_ page. Once again, click on the **arrow in a circle** icon next to the database being upgraded. The :guilabel:`Upgrade your database` pop-up appears as before, except that there is now a :guilabel:`Production` option under the :guilabel:`Purpose` section."
msgstr ""
#: ../../content/administration/upgrade/odoo_online.rst:64
msgid "Select the :guilabel:`Production` option and then click :guilabel:`Upgrade` to begin the upgrade process. As before, a notification email is sent to the email address provided and a red :guilabel:`Upgrade in progress` tag appears next to the name of the database."
msgstr ""
#: ../../content/administration/upgrade/odoo_online.rst:68
msgid "After the upgrade is finished, the :guilabel:`Upgrade in progress` tag disappears and the database is upgraded to the version specified."
msgstr ""
#: ../../content/administration/upgrade/odoo_sh.rst:10

2
locale/sources/contributing.pot
View File

@ -8,7 +8,7 @@ msgid ""
msgstr ""
"Project-Id-Version: Odoo 16.0\n"
"Report-Msgid-Bugs-To: \n"
"POT-Creation-Date: 2023-05-30 12:32+0000\n"
"POT-Creation-Date: 2023-07-03 09:37+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"

1741
locale/sources/finance.pot
View File

File diff suppressed because it is too large Load Diff

4
locale/sources/general.pot
View File

@ -8,7 +8,7 @@ msgid ""
msgstr ""
"Project-Id-Version: Odoo 16.0\n"
"Report-Msgid-Bugs-To: \n"
"POT-Creation-Date: 2023-05-30 12:32+0000\n"
"POT-Creation-Date: 2023-07-03 09:37+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"
@ -2571,7 +2571,7 @@ msgid "Grouping records on the Sales Analysis report"
msgstr ""
#: ../../content/applications/general/search.rst:95
msgid "You can also **custom groups** by using a wide selection of fields present on the model. To do so, click :menuselection:`Group By --> Add Custom Group`, select a field, and click :guilabel:`Apply`."
msgid "You can **customize groups** by using a wide selection of fields present on the model. To do so, click :menuselection:`Group By --> Add Custom Group`, select a field, and click :guilabel:`Apply`."
msgstr ""
#: ../../content/applications/general/search.rst:99

299
locale/sources/hr.pot
View File

@ -8,7 +8,7 @@ msgid ""
msgstr ""
"Project-Id-Version: Odoo 16.0\n"
"Report-Msgid-Bugs-To: \n"
"POT-Creation-Date: 2023-05-15 06:38+0000\n"
"POT-Creation-Date: 2023-07-03 09:37+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"
@ -100,3 +100,300 @@ msgstr ""
#: ../../content/applications/hr/attendances/hardware.rst:51
msgid "We recommend using the `Honeywell product line <https://sps.honeywell.com/us/en/products/productivity/barcode-scanners>`_. If the barcode scanner is connected directly to a computer, it must be configured to use the computer's keyboard layout."
msgstr ""
#: ../../content/applications/hr/employees.rst:7
msgid "Employees"
msgstr ""
#: ../../content/applications/hr/employees.rst:9
msgid "Odoo *Employees* organizes a company's employee records, contracts, and departments."
msgstr ""
#: ../../content/applications/hr/employees/new_employee.rst:3
msgid "Add a new employee"
msgstr ""
#: ../../content/applications/hr/employees/new_employee.rst:5
msgid "When a new employee is hired, the first step is to create a new employee form. Starting in the :menuselection:`Employees` app default view, click the :guilabel:`Create` button to access a new employee form. Fill out the required information (underlined in bold) and any additional details, then click :guilabel:`Save`."
msgstr ""
#: ../../content/applications/hr/employees/new_employee.rst:-1
msgid "Create a new employee card."
msgstr ""
#: ../../content/applications/hr/employees/new_employee.rst:15
msgid "The current company phone number and name is populated in the :guilabel:`Work Phone` and :guilabel:`Company` fields."
msgstr ""
#: ../../content/applications/hr/employees/new_employee.rst:19
msgid "General information"
msgstr ""
#: ../../content/applications/hr/employees/new_employee.rst:22
msgid "Required fields"
msgstr ""
#: ../../content/applications/hr/employees/new_employee.rst:24
msgid ":guilabel:`Name`: Enter the employee's name."
msgstr ""
#: ../../content/applications/hr/employees/new_employee.rst:25
msgid ":guilabel:`Company`: Select the company from the drop-down menu that the new employee is hired by, or create a new company by typing the name in the field."
msgstr ""
#: ../../content/applications/hr/employees/new_employee.rst:27
msgid ":guilabel:`Working Hours`: In the :guilabel:`Work Information` tab, select the desired :guilabel:`Working Hours` from the drop-down menu."
msgstr ""
#: ../../content/applications/hr/employees/new_employee.rst:-1
msgid "Working Hours are located in the Work Information tab."
msgstr ""
#: ../../content/applications/hr/employees/new_employee.rst:35
msgid ":guilabel:`Working Hours` are related to a company's working times, and an employee cannot have working hours that are outside of a company's working times."
msgstr ""
#: ../../content/applications/hr/employees/new_employee.rst:38
msgid "Each individual working time is company-specific, so for multi-company databases, each company needs to have its own working hours set."
msgstr ""
#: ../../content/applications/hr/employees/new_employee.rst:41
msgid "If an employee's working hours are not configured as a working time for the company, new working times can be added, or existing working times can be modified. To add or modify a working time, go to the :menuselection:`Payroll app --> Configuration --> Working Times`, and add a new working time or edit an existing one."
msgstr ""
#: ../../content/applications/hr/employees/new_employee.rst:46
msgid "After the new working time is created, set the working hours for the employee."
msgstr ""
#: ../../content/applications/hr/employees/new_employee.rst:49
msgid "Optional fields"
msgstr ""
#: ../../content/applications/hr/employees/new_employee.rst:51
msgid ":guilabel:`Photo`: In the top right image box of the employee card, click on the :guilabel:`✏️ (pencil)` edit icon to select a photo to upload."
msgstr ""
#: ../../content/applications/hr/employees/new_employee.rst:53
msgid ":guilabel:`Job Position`: Enter the employee's job position title."
msgstr ""
#: ../../content/applications/hr/employees/new_employee.rst:54
msgid "Tags: Click on a tag in the drop-down menu to add any tags applicable to the employee. Any tag can be created in this field by typing it in. Once created, the new tag is available for all employee cards. There is no limit to the amount of tags that can be added."
msgstr ""
#: ../../content/applications/hr/employees/new_employee.rst:57
msgid "Work Contact Information: Enter the employees :guilabel:`Work Mobile`, :guilabel:`Work Phone`, :guilabel:`Work Email`, and/or :guilabel:`Company` name."
msgstr ""
#: ../../content/applications/hr/employees/new_employee.rst:59
msgid ":guilabel:`Department`: Select the employee's department from the drop-down menu."
msgstr ""
#: ../../content/applications/hr/employees/new_employee.rst:60
msgid ":guilabel:`Manager`: Select the employee's manager from the drop-down menu."
msgstr ""
#: ../../content/applications/hr/employees/new_employee.rst:61
msgid ":guilabel:`Coach`: Select the employee's coach from the drop-down menu."
msgstr ""
#: ../../content/applications/hr/employees/new_employee.rst:64
msgid "After a :guilabel:`Manager` is selected, if the :guilabel:`Coach` field is blank, the selected manager automatically populates the :guilabel:`Coach` field."
msgstr ""
#: ../../content/applications/hr/employees/new_employee.rst:68
msgid "To make edits to the selected :guilabel:`Department`, :guilabel:`Manager`, :guilabel:`Coach`, or :guilabel:`Company`, click the :guilabel:`External Link` button next to the respective selection. The :guilabel:`External Link` button opens the selected form, allowing for modifications. Click :guilabel:`Save` after any edits are made."
msgstr ""
#: ../../content/applications/hr/employees/new_employee.rst:74
msgid "Additional information tabs"
msgstr ""
#: ../../content/applications/hr/employees/new_employee.rst:77
msgid "Resumé tab"
msgstr ""
#: ../../content/applications/hr/employees/new_employee.rst:80
msgid "Resumé"
msgstr ""
#: ../../content/applications/hr/employees/new_employee.rst:82
msgid "Next, the employee's work history is entered in the :guilabel:`Resumé` tab. Each previous experience must be entered individually. Click :guilabel:`Create a New Entry`, and the :guilabel:`Create Resumé lines` form appears. Enter the following information, then click the :guilabel:`Save & Close` button if there is only one entry to add, or click the :guilabel:`Save & New` button to save the current entry and create another line."
msgstr ""
#: ../../content/applications/hr/employees/new_employee.rst:-1
msgid "Add information for the previous work experience in this form."
msgstr ""
#: ../../content/applications/hr/employees/new_employee.rst:92
msgid ":guilabel:`Name`: Type in the name of the previous work experience."
msgstr ""
#: ../../content/applications/hr/employees/new_employee.rst:93
msgid ":guilabel:`Type`: From the drop-down menu, select either :guilabel:`Experience`, :guilabel:`Education`, :guilabel:`Internal Certification`, :guilabel:`Internal Training`, or type in a new entry."
msgstr ""
#: ../../content/applications/hr/employees/new_employee.rst:96
msgid ":guilabel:`Display Type`: Select either :guilabel:`Classic`, :guilabel:`Certification`, or :guilabel:`Course` from the drop-down menu."
msgstr ""
#: ../../content/applications/hr/employees/new_employee.rst:98
msgid ":guilabel:`Date Start` and :guilabel:`Date End`: Enter the start and end dates for the work experience. To select a date, use the :guilabel:`< (left)` and :guilabel:`> (right)` arrow icons to scroll to the desired month, then click on the day to select it."
msgstr ""
#: ../../content/applications/hr/employees/new_employee.rst:101
msgid ":guilabel:`Description`: Enter any relevant details in the field."
msgstr ""
#: ../../content/applications/hr/employees/new_employee.rst:104
msgid "Skills"
msgstr ""
#: ../../content/applications/hr/employees/new_employee.rst:106
msgid "An employee's skills can be entered in the :guilabel:`Resumé` tab in the same manner a resumé line is created. Click the :guilabel:`Create a New Entry` button under :guilabel:`Skills` and a :guilabel:`Create Skills` form appears. Fill in the information, then click the :guilabel:`Save & Close` button if there is only one entry to add, or click the :guilabel:`Save & New` button to save the current entry and immediately create a new entry."
msgstr ""
#: ../../content/applications/hr/employees/new_employee.rst:-1
msgid "Create a new skill for the employee."
msgstr ""
#: ../../content/applications/hr/employees/new_employee.rst:116
msgid ":guilabel:`Skill Type`: Select from the drop-down menu either :guilabel:`Languages`, :guilabel:`Dev`, :guilabel:`Music`, :guilabel:`Marketing`, or type in a new skill type. After entering the new skill type, an option to :guilabel:`Create` the skill or :guilabel:`Create and Edit` the skill appears. Click :guilabel:`Create and Edit`, and a pop-up for the specific skill type appears. This can also be accessed with the :guilabel:`External Link` button next to the new skill. This form allows for the creation of specific skills and levels. Click :guilabel:`Add a line` and enter the information for the new skill, then repeat for all other added skills. Repeat this process for the :guilabel:`Levels` section. Click :guilabel:`Add a line` to add each level and progress."
msgstr ""
#: ../../content/applications/hr/employees/new_employee.rst:0
msgid "Add a new skill and levels."
msgstr ""
#: ../../content/applications/hr/employees/new_employee.rst:131
msgid "To add a math skill set, enter `Math` in the :guilabel:`Name` field. In the :guilabel:`Skills` field, enter `Algebra`, `Calculus`, and `Trigonometry`. And, in the :guilabel:`Levels` field enter `beginner`, `intermediate`, and `expert`. Then, either click :guilabel:`Save & Close` or :guilabel:`Save & New`."
msgstr ""
#: ../../content/applications/hr/employees/new_employee.rst:136
msgid ":guilabel:`Skill`: The corresponding skills associated with the selected :guilabel:`Skill Type` appear in a drop-down menu. For example, selecting :guilabel:`Language` as the :guilabel:`Skill Type` presents a variety of languages to select from under the :guilabel:`Skills` field. Select the appropriate pre-configured skill, or type in a new one."
msgstr ""
#: ../../content/applications/hr/employees/new_employee.rst:140
msgid ":guilabel:`Skill Level`: Pre-defined skill levels associated with the selected :guilabel:`Skill Type` appear in a drop-down menu. Select a level or create a new skill level by typing it in."
msgstr ""
#: ../../content/applications/hr/employees/new_employee.rst:142
msgid ":guilabel:`Progress`: Progress is automatically selected based on the selected :guilabel:`Skill Level`. Skill levels and progress can be modified in the :guilabel:`Skill Type` pop-up form, which is accessed via the :guilabel:`External Link` button next to :guilabel:`Skill Type` field."
msgstr ""
#: ../../content/applications/hr/employees/new_employee.rst:146
msgid "To delete any line from the :guilabel:`Resumé` tab, click the :guilabel:`🗑️ (trash can)` delete icon to delete the entry. Add a new line by clicking the :guilabel:`ADD` button next to the corresponding section."
msgstr ""
#: ../../content/applications/hr/employees/new_employee.rst:151
msgid "Work information tab"
msgstr ""
#: ../../content/applications/hr/employees/new_employee.rst:153
msgid ":guilabel:`Location`: Select the :guilabel:`Work Address` from the drop-down menu. The :guilabel:`External Link` button opens up the selected company form in a window, and allows for editing. The :guilabel:`Work Location` is where any specific location details should be noted, such as a floor, or building."
msgstr ""
#: ../../content/applications/hr/employees/new_employee.rst:157
msgid ":guilabel:`Approvers`: Using the drop-down menus, select the employees responsible for approving :guilabel:`Time Off`, :guilabel:`Expenses`, and :guilabel:`Timesheets` for the employee. The :guilabel:`External Link` button opens a form with the approver's :guilabel:`Name`, :guilabel:`Email Address`, :guilabel:`Company`, :guilabel:`Phone`, and :guilabel:`Mobile` fields. These can be modified, if needed. Click :guilabel:`Save` after making any edits."
msgstr ""
#: ../../content/applications/hr/employees/new_employee.rst:162
msgid ":guilabel:`Schedule`: Select the :guilabel:`Working Hours` (required) and :guilabel:`Timezone` for the employee. The :guilabel:`External Link` button opens up a detailed view of the specific daily working hours. Working hours can be created, modified, or deleted here. Global time off (such as holidays) can be entered in the :guilabel:`Global Time Off` tab. Click :guilabel:`Add a line` to add a new global time off."
msgstr ""
#: ../../content/applications/hr/employees/new_employee.rst:167
msgid ":guilabel:`Planning`: Click on a planning role from the drop-down menu for both the :guilabel:`Default Planning Role` and the :guilabel:`Planning Roles` fields to add a role. There is no limit to the amount of :guilabel:`Planning Roles` that can be selected for an employee, but there can only be one :guilabel:`Default Planning Role`. The default is the *typical* role that the employee performs, where the :guilabel:`Planning Roles` are *all* the specific roles the employee is able to perform."
msgstr ""
#: ../../content/applications/hr/employees/new_employee.rst:0
msgid "Add the work information to the Work Information tab."
msgstr ""
#: ../../content/applications/hr/employees/new_employee.rst:179
msgid "Private information tab"
msgstr ""
#: ../../content/applications/hr/employees/new_employee.rst:181
msgid "No information in the :guilabel:`Private Information` tab is required, however, some information in this section may be critical for the company's payroll department. In order to properly process payslips and ensure all deductions are accounted for, the employee's personal information should be entered."
msgstr ""
#: ../../content/applications/hr/employees/new_employee.rst:186
msgid "Here, the employee's :guilabel:`Private Contact`, :guilabel:`Marital Status`, :guilabel:`Emergency Contact`, :guilabel:`Education`, :guilabel:`Citizenship`, :guilabel:`Dependant`, and :guilabel:`Work Permit` information is entered. Fields are entered either using a drop-down menu, clicking a check box, or typing in the information."
msgstr ""
#: ../../content/applications/hr/employees/new_employee.rst:191
msgid ":guilabel:`Private Contact`: Enter the :guilabel:`Address` for the employee. The selection can be made with the drop-down menu. If the information is not available, type in the name for the new address. To edit the new address, click the :guilabel:`External Link` button to open the address form. On the address form, enter the necessary details, then click :guilabel:`Save`. Some other information in the :guilabel:`Private Contact` section may auto-populate, if the address is already listed in the drop-down menu."
msgstr ""
#: ../../content/applications/hr/employees/new_employee.rst:197
msgid ":guilabel:`Marital Status`: Select either :guilabel:`Single`, :guilabel:`Married`, :guilabel:`Legal Cohabitant`, :guilabel:`Widower`, or :guilabel:`Divorced` from the drop-down menu."
msgstr ""
#: ../../content/applications/hr/employees/new_employee.rst:200
msgid ":guilabel:`Emergency Contact`: Type in the name and phone number of the employee's emergency contact."
msgstr ""
#: ../../content/applications/hr/employees/new_employee.rst:202
msgid ":guilabel:`Education`: Select the highest level of education completed by the employee from the :guilabel:`Certificate Level` drop-down menu. Options include :guilabel:`Graduate`, :guilabel:`Bachelor`, :guilabel:`Master`, :guilabel:`Doctor`, or :guilabel:`Other`. Type in the :guilabel:`Field of Study`, and the name of the :guilabel:`School` in the respective fields."
msgstr ""
#: ../../content/applications/hr/employees/new_employee.rst:206
msgid ":guilabel:`Citizenship`: This section houses all the information relevant to the citizenship of the employee. Some selections use a drop-down menu, as does the :guilabel:`Nationality (Country)`, :guilabel:`Gender`, and :guilabel:`Country of Birth` sections. The :guilabel:`Date of Birth` uses a calendar module to select the date. First, click on the name of the month, then the year, to access the year ranges. Use the :guilabel:`< (left)` and :guilabel:`> (right)` arrow icons, navigate to the correct year range, and click on the year. Next, click on the month. Last, click on the day to select the date. Type in the information for the :guilabel:`Identification No`, :guilabel:`Passport No`, and :guilabel:`Place of Birth` fields. If the employee is :guilabel:`Disabled` or a :guilabel:`Nonresident`, click the check box next to the respective fields."
msgstr ""
#: ../../content/applications/hr/employees/new_employee.rst:216
msgid ":guilabel:`Dependant`: If the employee has any dependants, that information is entered here. Type in the number of children the employee has, and check the boxes next to :guilabel:`Disabled Children` and/or :guilabel:`Other Dependent People` if applicable."
msgstr ""
#: ../../content/applications/hr/employees/new_employee.rst:219
msgid ":guilabel:`Work Permit`: If the employee has a work permit, enter the information in this section. Type in the :guilabel:`Visa No` and/or :guilabel:`Work Permit No` in the corresponding fields. Using the calendar module, select the :guilabel:`Visa Expire Date` to enter the expiration date."
msgstr ""
#: ../../content/applications/hr/employees/new_employee.rst:-1
msgid "Add the private information to the Private Information tab."
msgstr ""
#: ../../content/applications/hr/employees/new_employee.rst:228
msgid "HR settings tab"
msgstr ""
#: ../../content/applications/hr/employees/new_employee.rst:230
msgid "This tab provides various fields for different information, depending on the country the company is located. Different fields are configured for different locations, however some sections appear regardless."
msgstr ""
#: ../../content/applications/hr/employees/new_employee.rst:234
msgid ":guilabel:`Status`: If applicable, select a :guilabel:`Related User`, :guilabel:`Job Position`, and :guilabel:`Language` with the drop-down menus. Type in the :guilabel:`Registration Number of the Employee`, and the :guilabel:`NIF Country Code` if available."
msgstr ""
#: ../../content/applications/hr/employees/new_employee.rst:237
msgid ":guilabel:`Fleet`: If the employee has access to a company car, enter the :guilabel:`Mobility Card` information here."
msgstr ""
#: ../../content/applications/hr/employees/new_employee.rst:239
msgid ":guilabel:`Timesheets`: Enter the employee's cost per hour in a $XX.XX format. This is factored in when the employee is working at a work center. This value affects the employee's pay, and may also affect manufacturing costs for a product, if the value of the manufactured product is not a fixed amount."
msgstr ""
#: ../../content/applications/hr/employees/new_employee.rst:243
msgid ":guilabel:`Attendance`: This section may only appear for Belgian companies. Enter the :guilabel:`INSZ or BIS` number if applicable. :guilabel:`Badge ID` and a :guilabel:`PIN Code` can be entered here, if the employee needs/has one. Click :guilabel:`Generate` next to the :guilabel:`Badge ID` to create a badge ID."
msgstr ""
#: ../../content/applications/hr/employees/new_employee.rst:-1
msgid "Enter any information prompted in the HR Settings tab for the employee."
msgstr ""
#: ../../content/applications/hr/employees/new_employee.rst:253
msgid "Personal documents tab"
msgstr ""
#: ../../content/applications/hr/employees/new_employee.rst:255
msgid "The :guilabel:`Personal Documents` tab is only displayed for certain countries. If this tab is not visible, it is not applicable to the company's location."
msgstr ""
#: ../../content/applications/hr/employees/new_employee.rst:258
msgid "Add a file for the employee's :guilabel:`ID Card Copy`, :guilabel:`Driving License`, :guilabel:`Mobile Subscription Invoice`, :guilabel:`SIM Card Copy`, and :guilabel:`Internet Subscription Invoice` by clicking the :guilabel:`Upload Your File` button next to the corresponding field. File types that can be accepted are :file:`.jpg`, :file:`.png`, and :file:`.pdf`."
msgstr ""
#: ../../content/applications/hr/employees/new_employee.rst:-1
msgid "Upload personal documents for the employee in the Personal Documents tab, either a jpg,\n"
"png, or pdf."
msgstr ""

803
locale/sources/inventory_and_mrp.pot
View File

File diff suppressed because it is too large Load Diff

267
locale/sources/marketing.pot
View File

@ -8,7 +8,7 @@ msgid ""
msgstr ""
"Project-Id-Version: Odoo 16.0\n"
"Report-Msgid-Bugs-To: \n"
"POT-Creation-Date: 2023-05-02 14:02+0000\n"
"POT-Creation-Date: 2023-07-03 09:37+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"
@ -779,124 +779,131 @@ 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."
msgid "Delivering marketing campaigns to the right audience is paramount when trying to grow a business. The Odoo *Marketing Automation* application helps marketers to do just that by providing detailed filtering tools, which 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"
msgid "Configure 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."
msgid "When configuring the target filters on a marketing campaign, there are some options that have an :guilabel:`> (arrow)` icon beside them. The :guilabel:`> (arrow)` icon signifies that the particular filter has more refined parameters within it that can be customized."
msgstr ""
#: ../../content/applications/marketing/marketing_automation/getting_started/target_audience.rst:-1
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:"
#: ../../content/applications/marketing/marketing_automation/getting_started/target_audience.rst:21
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 :guilabel:`ANY` or :guilabel:`ALL` statements."
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)."
msgid "Every time a new branch is created, there are two options:"
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)."
#: ../../content/applications/marketing/marketing_automation/getting_started/target_audience.rst:28
msgid "Either the records can match :guilabel:`ALL` criteria for the upcoming rules (creating an AND statement where *all* 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`."
#: ../../content/applications/marketing/marketing_automation/getting_started/target_audience.rst:30
msgid "Or, the records can match :guilabel:`ANY` criteria for the upcoming rules (creating an OR statement where *only one* of the criteria must match)."
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)`."
#: ../../content/applications/marketing/marketing_automation/getting_started/target_audience.rst:33
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:44
#: ../../content/applications/marketing/marketing_automation/getting_started/target_audience.rst:36
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 node or a branch, click on :guilabel:`✖ (delete)` icon to delete it."
msgstr ""
#: ../../content/applications/marketing/marketing_automation/getting_started/target_audience.rst:45
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."
#: ../../content/applications/marketing/marketing_automation/getting_started/target_audience.rst:47
msgid "The following scenarios 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"
#: ../../content/applications/marketing/marketing_automation/getting_started/target_audience.rst:51
msgid "Scenario #1: Narrow 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."
#: ../../content/applications/marketing/marketing_automation/getting_started/target_audience.rst:53
msgid "While in *Edit mode* on a campaign template form (by clicking the :guilabel:`Edit` button), 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`."
#: ../../content/applications/marketing/marketing_automation/getting_started/target_audience.rst:57
msgid "Next, click :guilabel:`Add Filter` in the :guilabel:`Filter` field. Then, 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)`."
#: ../../content/applications/marketing/marketing_automation/getting_started/target_audience.rst:62
msgid "Keep the second portion of the filter equation on the default :guilabel:`🟰 (equal sign)` icon."
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."
#: ../../content/applications/marketing/marketing_automation/getting_started/target_audience.rst:64
msgid "Next, 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 changes 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."
#: ../../content/applications/marketing/marketing_automation/getting_started/target_audience.rst:68
msgid "Add another node to this filter by clicking the :guilabel:`➕ (plus sign)` icon 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."
#: ../../content/applications/marketing/marketing_automation/getting_started/target_audience.rst:71
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)`."
#: ../../content/applications/marketing/marketing_automation/getting_started/target_audience.rst:76
msgid "Once again, leave the second portion of the filter equation on :guilabel:`🟰 (equal sign)` icon."
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."
#: ../../content/applications/marketing/marketing_automation/getting_started/target_audience.rst:78
msgid "Lastly, highlight the default value in the third (and final) portion of the second filter equation, and type in `New`. With that in place, Odoo only targets opportunities that are in the \"New\" stage of the pipeline."
msgstr ""
#: ../../content/applications/marketing/marketing_automation/getting_started/target_audience.rst:-1
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"
#: ../../content/applications/marketing/marketing_automation/getting_started/target_audience.rst:87
msgid "Scenario #2: Narrow down target to event attendees who 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."
#: ../../content/applications/marketing/marketing_automation/getting_started/target_audience.rst:89
msgid "While in *Edit mode* on a campaign template form (by clicking the :guilabel:`Edit` button), 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
#: ../../content/applications/marketing/marketing_automation/getting_started/target_audience.rst:93
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`."
#: ../../content/applications/marketing/marketing_automation/getting_started/target_audience.rst:98
msgid "Click the default :guilabel:`🟰 (equal sign)` icon in the second portion of the filter equation. This reveals a drop-down menu. From this drop-down 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."
#: ../../content/applications/marketing/marketing_automation/getting_started/target_audience.rst:101
msgid "In the third (and final) empty portion of the filter equation, type in the name of the event(s) that Odoo should 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`."
#: ../../content/applications/marketing/marketing_automation/getting_started/target_audience.rst:104
msgid "Then, add another node to this filter by clicking the :guilabel:`➕ (plus sign)` icon to the right of the equation."
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`."
#: ../../content/applications/marketing/marketing_automation/getting_started/target_audience.rst:107
msgid "The second node will focus on targeting this campaign to attendees who purchase a specific type of ticket to the aforementioned event(s) mentioned in the first filter equation."
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."
#: ../../content/applications/marketing/marketing_automation/getting_started/target_audience.rst:110
msgid "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:114
msgid "Once again, click the default :guilabel:`🟰 (equal sign)` icon in the second portion of the filter equation, and select :guilabel:`contains`."
msgstr ""
#: ../../content/applications/marketing/marketing_automation/getting_started/target_audience.rst:117
msgid "Lastly, in the third (and final) portion of the second filter equation, which is 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:-1
@ -904,7 +911,7 @@ 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"
msgid "Testing/running campaigns"
msgstr ""
#: ../../content/applications/marketing/marketing_automation/getting_started/testing_running.rst:5
@ -912,39 +919,51 @@ msgid "Odoo gives users the ability to test marketing campaigns (and mailings) b
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."
msgid "First, open the :menuselection:`Marketing Automation` application, and select the desired campaign, which reveals that campaign's detail form."
msgstr ""
#: ../../content/applications/marketing/marketing_automation/getting_started/testing_running.rst:11
msgid "On the campaign detail form, make sure the campaign already has activities configured (or build a campaign by following the directions here on :doc:`this documentation </applications/marketing/marketing_automation/getting_started/workflow_activities>`)."
msgstr ""
#: ../../content/applications/marketing/marketing_automation/getting_started/testing_running.rst:15
msgid "To start a test, click the :guilabel:`Launch a Test` button at the top of the campaign form."
msgstr ""
#: ../../content/applications/marketing/marketing_automation/getting_started/testing_running.rst:-1
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."
#: ../../content/applications/marketing/marketing_automation/getting_started/testing_running.rst:21
msgid "When clicked, a :guilabel:`Launch a test` pop-up window appears. In the drop-down field, choose an existing record (or create a new one) to run the test on. To create a brand new record, click the :guilabel:`Search More...` link at the bottom of the drop-down menu, and then click the :guilabel:`Create` button."
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."
#: ../../content/applications/marketing/marketing_automation/getting_started/testing_running.rst:26
msgid "Doing so reveals a blank contact form, in which the :guilabel:`Name` and :guilabel:`Email` **must** be entered. When all the necessary information has been entered, click :guilabel:`Save`, and Odoo returns to the :guilabel:`Launch a test` pop-up, with that new record in the :guilabel:`Choose an existing record or create a new one to test` field."
msgstr ""
#: ../../content/applications/marketing/marketing_automation/getting_started/testing_running.rst:31
msgid "Once a record is selected, click :guilabel:`Continue`, and Odoo reveals the campaign test page."
msgstr ""
#: ../../content/applications/marketing/marketing_automation/getting_started/testing_running.rst:-1
msgid "Test screen in Odoo Marketing Automation."
msgstr ""
#: ../../content/applications/marketing/marketing_automation/getting_started/testing_running.rst: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."
#: ../../content/applications/marketing/marketing_automation/getting_started/testing_running.rst:37
msgid "On the campaign test page, the name of the :guilabel:`Record` being tested is visible, along with the precise time this test workflow was started in the :guilabel:`Workflow Started On` field. Beneath that, in the :guilabel:`Workflow` section is the first activity (or activities) in the workflow that's being tested."
msgstr ""
#: ../../content/applications/marketing/marketing_automation/getting_started/testing_running.rst: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."
#: ../../content/applications/marketing/marketing_automation/getting_started/testing_running.rst:42
msgid "To start a test, click the :guilabel:`Run` button, represented by a :guilabel:`▶️ (play button)` icon beside the first activity in the workflow. When clicked, the page reloads, and Odoo shows the various results (and analytics) connected to that specific activity as they occur, in real-time."
msgstr ""
#: ../../content/applications/marketing/marketing_automation/getting_started/testing_running.rst:-1
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."
#: ../../content/applications/marketing/marketing_automation/getting_started/testing_running.rst:50
msgid "Once all the workflow activities are completed, the test will end, and move to the :guilabel:`Completed` stage. To stop a test before all the workflow activities are completed, click the :guilabel:`Stop` button in the upper-left corner of the campaign test page."
msgstr ""
#: ../../content/applications/marketing/marketing_automation/getting_started/workflow_activities.rst:3
@ -952,115 +971,127 @@ 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."
msgid "When creating a campaign in the *Marketing Automation* app, users can plan marketing activities, such as email or SMS campaigns."
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:"
#: ../../content/applications/marketing/marketing_automation/getting_started/workflow_activities.rst:8
msgid "To get started, navigate to the bottom of a marketing automation campaign detail form, and click :guilabel:`Add New Activity`. Doing so reveals a :guilabel:`Create Activities` pop-up window. This pop-up window is a blank activity template, where specific parameters can be set for that particular activity."
msgstr ""
#: ../../content/applications/marketing/marketing_automation/getting_started/workflow_activities.rst:13
msgid "The following fields are available in the :guilabel:`Create Activities` pop-up window (when :guilabel:`Add New Activity` is clicked):"
msgstr ""
#: ../../content/applications/marketing/marketing_automation/getting_started/workflow_activities.rst:-1
msgid "An activity template in Odoo Marketing Automation."
msgstr ""
#: ../../content/applications/marketing/marketing_automation/getting_started/workflow_activities.rst:17
#: ../../content/applications/marketing/marketing_automation/getting_started/workflow_activities.rst:20
msgid ":guilabel:`Activity Name`: the title of the activity."
msgstr ""
#: ../../content/applications/marketing/marketing_automation/getting_started/workflow_activities.rst:18
msgid ":guilabel:`Activity Type`: choose between Email, Server Action (internal Odoo operation), or SMS."
#: ../../content/applications/marketing/marketing_automation/getting_started/workflow_activities.rst:21
msgid ":guilabel:`Activity Type`: choose between `Email`, `Server Action` (internal Odoo operation), or `SMS`."
msgstr ""
#: ../../content/applications/marketing/marketing_automation/getting_started/workflow_activities.rst:19
#: ../../content/applications/marketing/marketing_automation/getting_started/workflow_activities.rst:23
msgid ":guilabel:`Mail Template`: choose from pre-configured templates (or create a new one on-the-fly)."
msgstr ""
#: ../../content/applications/marketing/marketing_automation/getting_started/workflow_activities.rst:20
#: ../../content/applications/marketing/marketing_automation/getting_started/workflow_activities.rst:24
msgid ":guilabel:`Trigger`: choose when this activity should be triggered."
msgstr ""
#: ../../content/applications/marketing/marketing_automation/getting_started/workflow_activities.rst:21
#: ../../content/applications/marketing/marketing_automation/getting_started/workflow_activities.rst:25
msgid ":guilabel:`Expiry Duration`: configure to stop the actions after a specific amount of time (after the scheduled date). When selected, a :guilabel:`Cancel after` field appears, in which the user can choose how many :guilabel:`Hours, Days, Weeks, or Months` they want the actions to cease after the initial date."
msgstr ""
#: ../../content/applications/marketing/marketing_automation/getting_started/workflow_activities.rst:25
msgid ":guilabel:`Activity Filter`: domain related to this activity (and all subsequent Child Activities)."
#: ../../content/applications/marketing/marketing_automation/getting_started/workflow_activities.rst:29
msgid ":guilabel:`Activity Filter`: domain related to this activity (and all subsequent child activities)."
msgstr ""
#: ../../content/applications/marketing/marketing_automation/getting_started/workflow_activities.rst:27
#: ../../content/applications/marketing/marketing_automation/getting_started/workflow_activities.rst:31
msgid ":guilabel:`Applied Filter`: activity will *only* be performed if it satisfies the specified domain (filter)."
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."
msgid "After the activity's settings are fully configured, click :guilabel:`Save & Close` to save the activity and return to the marketing automation campaign form, :guilabel:`Save & New` to save the activity and immediately create another one in a fresh :guilabel:`Create Activities` pop-up window, or :guilabel:`Discard` to delete the activity and return to the marketing automation campaign form."
msgstr ""
#: ../../content/applications/marketing/marketing_automation/getting_started/workflow_activities.rst: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)."
msgid "Workflow activity"
msgstr ""
#: ../../content/applications/marketing/marketing_automation/getting_started/workflow_activities.rst:42
msgid "Once an activity is saved, the :guilabel:`Workflow Activity` section appears at the bottom of the marketing automation campaign form. Each activity is displayed as a line graph."
msgstr ""
#: ../../content/applications/marketing/marketing_automation/getting_started/workflow_activities.rst:45
msgid "The configured :guilabel:`Trigger` time for that activity can be found to the left of the :guilabel:`Workflow Activity` card in the :guilabel:`Workflow` section."
msgstr ""
#: ../../content/applications/marketing/marketing_automation/getting_started/workflow_activities.rst:48
msgid "Once the activity has been triggered, a figure representing the number of :guilabel:`Success` or :guilabel:`Rejected` activities will be displayed to the right of the graph."
msgstr ""
#: ../../content/applications/marketing/marketing_automation/getting_started/workflow_activities.rst:-1
msgid "Typical workflow activity in Odoo Marketing Automation."
msgstr ""
#: ../../content/applications/marketing/marketing_automation/getting_started/workflow_activities.rst: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`."
#: ../../content/applications/marketing/marketing_automation/getting_started/workflow_activities.rst:56
msgid "If the :guilabel:`Activity Type` of the activity is set to :guilabel:`Email`, there are more in-depth analytics beneath the activity graph data, detailing how many emails have been :guilabel:`Sent`, and what percentage of those have been :guilabel:`Clicked`, :guilabel:`Replied` to, or :guilabel:`Bounced`."
msgstr ""
#: ../../content/applications/marketing/marketing_automation/getting_started/workflow_activities.rst:55
#: ../../content/applications/marketing/marketing_automation/getting_started/workflow_activities.rst:62
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."
#: ../../content/applications/marketing/marketing_automation/getting_started/workflow_activities.rst:64
msgid "There is also the option to add a *child activity* by clicking :guilabel:`Add child activity`, located at the bottom of each activity block in the :guilabel:`Workflow` section of a marketing automation form."
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."
msgid "Child activities are sub-activities that are connected to (and triggered by) the activity above it, which is also known as its *parent activity*."
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."
msgid "Odoo provides a number of triggering options to launch a child activity - all of which depend on the trigger configurations related to the parent activity. Under the desired parent activity, hover over :guilabel:`Add child activity`, and select any of the following triggers:"
msgstr ""
#: ../../content/applications/marketing/marketing_automation/getting_started/workflow_activities.rst:75
msgid ":guilabel:`Add Another Activity`: instantly add another activity."
msgstr ""
#: ../../content/applications/marketing/marketing_automation/getting_started/workflow_activities.rst:76
msgid ":guilabel:`Opened`: the next activity will be triggered if the (email) recipient opens the mailing."
msgstr ""
#: ../../content/applications/marketing/marketing_automation/getting_started/workflow_activities.rst:78
msgid ":guilabel:`Not Opened`: the next activity will be triggered if the recipient does not open the mailing."
msgstr ""
#: ../../content/applications/marketing/marketing_automation/getting_started/workflow_activities.rst:80
msgid ":guilabel:`Replied`: the next activity will be triggered if the recipient replies to the mailing."
msgstr ""
#: ../../content/applications/marketing/marketing_automation/getting_started/workflow_activities.rst:81
msgid ":guilabel:`Not Replied`: the next activity will be triggered if the recipient does not reply to the mailing."
msgstr ""
#: ../../content/applications/marketing/marketing_automation/getting_started/workflow_activities.rst:83
msgid ":guilabel:`Clicked`: the next activity will be triggered if the recipient clicks on a link included in the mailing."
msgstr ""
#: ../../content/applications/marketing/marketing_automation/getting_started/workflow_activities.rst:85
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
#: ../../content/applications/marketing/marketing_automation/getting_started/workflow_activities.rst:87
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."
#: ../../content/applications/marketing/marketing_automation/getting_started/workflow_activities.rst:89
msgid "Once a trigger is selected, the user can configure the child activity (it has the same configuration options as a regular activity), and click :guilabel:`Save & Close` to finish creating the child activity, which will then be displayed in the :guilabel:`Workflow` section, in a slightly indented position beneath its parent activity."
msgstr ""
#: ../../content/applications/marketing/sms_marketing.rst:8

920
locale/sources/productivity.pot
View File

File diff suppressed because it is too large Load Diff

644
locale/sources/sales.pot
View File

@ -8,7 +8,7 @@ msgid ""
msgstr ""
"Project-Id-Version: Odoo 16.0\n"
"Report-Msgid-Bugs-To: \n"
"POT-Creation-Date: 2023-06-15 11:45+0000\n"
"POT-Creation-Date: 2023-07-03 09:37+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"
@ -58,6 +58,7 @@ msgstr ""
#: ../../content/applications/sales/crm/track_leads/prospect_visits.rst:12
#: ../../content/applications/sales/point_of_sale/configuration.rst:6
#: ../../content/applications/sales/point_of_sale/employee_login.rst:13
#: ../../content/applications/sales/point_of_sale/payment_methods/terminals.rst:11
#: ../../content/applications/sales/point_of_sale/payment_methods/terminals/adyen.rst:13
#: ../../content/applications/sales/point_of_sale/payment_methods/terminals/ingenico.rst:12
#: ../../content/applications/sales/point_of_sale/payment_methods/terminals/six.rst:16
@ -77,7 +78,6 @@ msgstr ""
#: ../../content/applications/sales/sales/products_prices/products/variants.rst:23
#: ../../content/applications/sales/sales/send_quotations/orders_and_variants.rst:9
#: ../../content/applications/sales/sales/send_quotations/quote_template.rst:9
#: ../../content/applications/sales/sales/send_quotations/terms_and_conditions.rst:16
#: ../../content/applications/sales/subscriptions/closing.rst:31
#: ../../content/applications/sales/subscriptions/upselling.rst:25
msgid "Configuration"
@ -1836,46 +1836,66 @@ msgstr ""
msgid "Creating a new payment method for a POS."
msgstr ""
#: ../../content/applications/sales/point_of_sale/payment_methods.rst:21
msgid "Selecting a :guilabel:`bank` journal automatically adds the :guilabel:`Use a Payment Terminal` field in which you can add your terminal's information."
#: ../../content/applications/sales/point_of_sale/payment_methods.rst:18
msgid "Selecting a :guilabel:`bank` journal automatically adds the :guilabel:`Use a Payment Terminal` field in which you can add your :doc:`payment terminal's information <payment_methods/terminals>`."
msgstr ""
#: ../../content/applications/sales/point_of_sale/payment_methods.rst:23
msgid "Credentials are mandatory to use a payment terminal. To learn how to configure the different terminals, check out the following documentation pages:"
msgid ":doc:`payment_methods/terminals`."
msgstr ""
#: ../../content/applications/sales/point_of_sale/payment_methods.rst:26
msgid ":doc:`Adyen configuration <payment_methods/terminals/adyen>`"
msgstr ""
#: ../../content/applications/sales/point_of_sale/payment_methods.rst:27
msgid ":doc:`Ingenico configuration <payment_methods/terminals/ingenico>`"
msgstr ""
#: ../../content/applications/sales/point_of_sale/payment_methods.rst:28
msgid ":doc:`Six configuration <payment_methods/terminals/six>`"
msgstr ""
#: ../../content/applications/sales/point_of_sale/payment_methods.rst:29
msgid ":doc:`Stripe configuration <payment_methods/terminals/stripe>`"
msgstr ""
#: ../../content/applications/sales/point_of_sale/payment_methods.rst:30
msgid ":doc:`Vantiv configuration <payment_methods/terminals/vantiv>`"
msgstr ""
#: ../../content/applications/sales/point_of_sale/payment_methods.rst:31
msgid ":doc:`Worldline configuration <payment_methods/terminals/worldline>`"
msgstr ""
#: ../../content/applications/sales/point_of_sale/payment_methods.rst:33
msgid "Once the payment method is created, you can select it to be used in your POS. To do so, go to the :ref:`POS settings <configuration/settings>`, select the 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."
#: ../../content/applications/sales/point_of_sale/payment_methods.rst:25
msgid "Once the payment method is created, you can select it in your POS settings. To do so, go to the :ref:`POS' settings <configuration/settings>`, click :guilabel:`Edit`, and add the payment method under the :guilabel:`Payments` section."
msgstr ""
#: ../../content/applications/sales/point_of_sale/payment_methods/terminals.rst:5
msgid "Payment terminals"
msgstr ""
#: ../../content/applications/sales/point_of_sale/payment_methods/terminals.rst:7
msgid "Connecting and integrating a payment terminal with your POS system allows you to accept multiple payment options, including credit and debit cards, making the payment process more efficient."
msgstr ""
#: ../../content/applications/sales/point_of_sale/payment_methods/terminals.rst:13
msgid "Go to the :doc:`application settings <../configuration>`, scroll down to the :guilabel:`Payment Terminals` section, and tick your terminal's checkbox."
msgstr ""
#: ../../content/applications/sales/point_of_sale/payment_methods/terminals.rst:-1
msgid "checkbox in the settings to enable a payment terminal"
msgstr ""
#: ../../content/applications/sales/point_of_sale/payment_methods/terminals.rst:19
msgid "Then, follow the corresponding documentation to configure your device:"
msgstr ""
#: ../../content/applications/sales/point_of_sale/payment_methods/terminals.rst:21
msgid ":doc:`Adyen configuration <terminals/adyen>`"
msgstr ""
#: ../../content/applications/sales/point_of_sale/payment_methods/terminals.rst:22
msgid ":doc:`Ingenico configuration <terminals/ingenico>`"
msgstr ""
#: ../../content/applications/sales/point_of_sale/payment_methods/terminals.rst:23
msgid ":doc:`SIX configuration <terminals/six>`"
msgstr ""
#: ../../content/applications/sales/point_of_sale/payment_methods/terminals.rst:24
msgid ":doc:`Stripe configuration <terminals/stripe>`"
msgstr ""
#: ../../content/applications/sales/point_of_sale/payment_methods/terminals.rst:25
msgid ":doc:`Vantiv configuration <terminals/vantiv>`"
msgstr ""
#: ../../content/applications/sales/point_of_sale/payment_methods/terminals.rst:26
msgid ":doc:`Worldline configuration <terminals/worldline>`"
msgstr ""
#: ../../content/applications/sales/point_of_sale/payment_methods/terminals.rst:28
msgid "Once the terminal is configured, you can :doc:`create the corresponding payment method and add it to the POS <../payment_methods>`."
msgstr ""
#: ../../content/applications/sales/point_of_sale/payment_methods/terminals/adyen.rst:3
msgid "Adyen"
msgstr ""
@ -4156,107 +4176,204 @@ msgid "Invoicing Method"
msgstr ""
#: ../../content/applications/sales/sales/invoicing/down_payment.rst:3
msgid "Request a down payment"
msgid "Down payments"
msgstr ""
#: ../../content/applications/sales/sales/invoicing/down_payment.rst:5
msgid "A down payment is a partial payment made by the buyer when a sales contract is concluded. This implies both parties' full commitment (seller and buyer) to honor the contract. With a down payment, the buyers show their will to acquire the product and agree to pay the rest later, while the sellers are obliged to provide the goods by accepting it."
msgid "A down payment is a partial payment made by the buyer when a sales contract is concluded. This implies both parties' (seller and buyer) full commitment to honor the contract."
msgstr ""
#: ../../content/applications/sales/sales/invoicing/down_payment.rst:10
msgid "Sometimes a down payment is required for expensive orders or projects. That way, you can protect yourself and make sure that your customer is reliable."
#: ../../content/applications/sales/sales/invoicing/down_payment.rst:8
msgid "With a down payment, the buyer pays a portion of the total amount owed while agreeing to pay the remaining amount at a later date. In turn, the seller provides goods or services to the buyer after accepting the down payment, trusting that the remaining amount will be paid later on."
msgstr ""
#: ../../content/applications/sales/sales/invoicing/down_payment.rst:14
msgid "First time you request a down payment"
#: ../../content/applications/sales/sales/invoicing/down_payment.rst:13
msgid "Initial down payment request"
msgstr ""
#: ../../content/applications/sales/sales/invoicing/down_payment.rst:16
msgid "When a sales order is confirmed, you then have the possibility to create an invoice. Invoices are automatically created in drafts so that you can review them before validation. To create an invoice, Odoo Sales offers you 3 options:"
#: ../../content/applications/sales/sales/invoicing/down_payment.rst:15
msgid "When a sales order is confirmed, the option to create an invoice becomes available, via the :guilabel:`Create Invoice` button, located in the upper-left corner of the sales order form. When clicked, a :guilabel:`Create invoices` pop-up appears."
msgstr ""
#: ../../content/applications/sales/sales/invoicing/down_payment.rst:20
msgid "Regular invoice"
msgstr ""
#: ../../content/applications/sales/sales/invoicing/down_payment.rst:21
msgid "Down payment (percentage)"
msgid "Invoices are automatically created in drafts, so they can be reviewed before validation."
msgstr ""
#: ../../content/applications/sales/sales/invoicing/down_payment.rst:22
msgid "Down payment (fixed amount)"
msgid "On the :guilabel:`Create invoices` pop-up, there are 3 options to choose from in the :guilabel:`Create Invoice` field:"
msgstr ""
#: ../../content/applications/sales/sales/invoicing/down_payment.rst:24
msgid "In terms of down payment, it can either be a fixed amount or a percentage of the total amount. The first time you request a down payment, you can set a percentage or a fixed amount of your choice, and select the right income account and taxes. These settings will be reused for future down payments."
#: ../../content/applications/sales/sales/invoicing/down_payment.rst:27
msgid ":guilabel:`Regular invoice`"
msgstr ""
#: ../../content/applications/sales/sales/invoicing/down_payment.rst:-1
msgid "How can you do a down payment on Odoo Sales?"
#: ../../content/applications/sales/sales/invoicing/down_payment.rst:27
msgid "If :guilabel:`Regular Invoice` is selected the other fields disappear, as they only pertain to down payment configurations."
msgstr ""
#: ../../content/applications/sales/sales/invoicing/down_payment.rst:29
msgid ":guilabel:`Down payment (percentage)`"
msgstr ""
#: ../../content/applications/sales/sales/invoicing/down_payment.rst:30
msgid ":guilabel:`Down payment (fixed amount)`"
msgstr ""
#: ../../content/applications/sales/sales/invoicing/down_payment.rst:32
msgid "In terms of a down payment, it can either be a fixed amount or a percentage of the total amount."
msgstr ""
#: ../../content/applications/sales/sales/invoicing/down_payment.rst:34
msgid "When you request your first down payment, a new product called **Down payment** will be created. This product will be registered as a **service** product with an invoicing policy of **ordered quantities**. As a reminder, you can edit this product and modify it at any time. Please note that if you choose **delivered quantities** as invoicing policy, **you will not be able to create an invoice**."
msgid "Once the desired down payment option is selected in the :guilabel:`Create Invoice` field, designate the desired amount (either as a percentage or fixed amount) in the :guilabel:`Down Payment Amount` field."
msgstr ""
#: ../../content/applications/sales/sales/invoicing/down_payment.rst:41
msgid "Basic sales flow using down payments"
msgstr ""
#: ../../content/applications/sales/sales/invoicing/down_payment.rst:43
msgid "For this first example, we will use a 50% amount down payment with a product using **ordered quantities** as invoicing policy. Make sure to check out our documentation about invoicing policies here: :doc:`invoicing_policy` , before requesting your first down payment. When it comes to create and view the invoice, you will only have access to a draft invoice mentioning the down payment (as you can see below)."
#: ../../content/applications/sales/sales/invoicing/down_payment.rst:38
msgid "Then, select the appropriate income account for the invoice in the :guilabel:`Income Account` field, and add a tax amount, if necessary, in the :guilabel:`Customer Taxes` field. These settings will be reused for future down payments."
msgstr ""
#: ../../content/applications/sales/sales/invoicing/down_payment.rst:-1
msgid "What is a basic sales flow using down payments on Odoo Sales (1)?"
msgid "How to configure a down payment on Odoo Sales."
msgstr ""
#: ../../content/applications/sales/sales/invoicing/down_payment.rst:53
msgid "There, you can post the invoice and register the payment of your customer. But, we all know that in real life this flow does not happen immediately. So, for now, you can return to the sales order. There, you will have the possibility to see the order as a customer with the **Customer preview** button or to reach easily the previous draft invoice with the **Invoice** button. In any case, the down payment will be mentioned on both (sales order and draft invoice)."
#: ../../content/applications/sales/sales/invoicing/down_payment.rst:47
msgid "When a down payment is first requested, a new product called :guilabel:`Down payment` is created. This product is registered as a :guilabel:`Service` product, with an invoicing policy of :guilabel:`Ordered quantities`. This product can be edited and modified at any time."
msgstr ""
#: ../../content/applications/sales/sales/invoicing/down_payment.rst:52
msgid "If :guilabel:`Delivered quantities` is chosen as the invoicing policy, an invoice will **not** be able to be created."
msgstr ""
#: ../../content/applications/sales/sales/invoicing/down_payment.rst:56
msgid "Request a 50% down payment"
msgstr ""
#: ../../content/applications/sales/sales/invoicing/down_payment.rst:58
msgid "For the following example, the flow involves a 50% amount down payment on a product with :guilabel:`Ordered quantities` as the invoicing policy."
msgstr ""
#: ../../content/applications/sales/sales/invoicing/down_payment.rst:62
#: ../../content/applications/sales/sales/invoicing/down_payment.rst:184
msgid ":doc:`/applications/sales/sales/invoicing/invoicing_policy`"
msgstr ""
#: ../../content/applications/sales/sales/invoicing/down_payment.rst:64
msgid "When the order is confirmed (via the :guilabel:`Confirm` button), it's time to create/view the invoice, by clicking :guilabel:`Create Invoice`."
msgstr ""
#: ../../content/applications/sales/sales/invoicing/down_payment.rst:67
msgid "Then, on the :guilabel:`Create invoices` pop-up window that appears, select :guilabel:`Down payment (percentage)`, and type `50` in the :guilabel:`Down Payment Amount` field. Lastly, click :guilabel:`Create and View Invoice` to create and view the invoice."
msgstr ""
#: ../../content/applications/sales/sales/invoicing/down_payment.rst:-1
msgid "What is a basic sales flow using down payments on Odoo Sales (2)?"
msgid "Create invoices pop up window in Odoo Sales."
msgstr ""
#: ../../content/applications/sales/sales/invoicing/down_payment.rst:63
msgid "To complete the flow, when the customer wants to pay the rest of his sales order, you must create another invoice. Once again, you will have the choice to make another down payment or to deduct all the down payments and so, paying the rest of the invoice as a regular invoice."
#: ../../content/applications/sales/sales/invoicing/down_payment.rst:75
msgid "Doing so reveals the draft invoice, which mentions the down payment."
msgstr ""
#: ../../content/applications/sales/sales/invoicing/down_payment.rst:-1
msgid "What is a basic sales flow using down payments on Odoo Sales (3)?"
msgid "A sample draft invoice with down payment mentioned in Odoo Sales."
msgstr ""
#: ../../content/applications/sales/sales/invoicing/down_payment.rst:71
msgid "This flow is also possible with a down payment taking into account a fixed amount."
msgstr ""
#: ../../content/applications/sales/sales/invoicing/down_payment.rst:74
msgid "Be careful that if you do a down payment with a product using **delivered quantities** as invoicing policy, you won’t be able to deduct all the down payments when it comes to invoicing your customer. Indeed, you have to deliver a product before creating the final invoice. If nothing has been delivered, you create a **credit note** that cancels the draft invoice created after the down payment. To do so, you have to install the **Inventory App** to confirm the delivery. Otherwise, you can enter the delivered quantity manually on the sales order."
msgstr ""
#: ../../content/applications/sales/sales/invoicing/down_payment.rst:82
msgid "Modify the income account and customer taxes"
#: ../../content/applications/sales/sales/invoicing/down_payment.rst:81
msgid "From there, the invoice can be confirmed/posted, and the payment can be registered. Return to the sales order, via the breadcrumbs."
msgstr ""
#: ../../content/applications/sales/sales/invoicing/down_payment.rst:84
msgid "From the products list, search for the **Down Payment** product."
msgid "On the sales order, the option to view what the customer will see is available, via the :guilabel:`Customer Preview` smart button, and the :guilabel:`Invoice` button reveals the drafted invoice. In either case, the down payment is mentioned on both the sales order and draft invoice."
msgstr ""
#: ../../content/applications/sales/sales/invoicing/down_payment.rst:-1
msgid "Creation of a down payment product on Odoo Sales"
msgid "How the down payment is mentioned on the sales order in Odoo Sales."
msgstr ""
#: ../../content/applications/sales/sales/invoicing/down_payment.rst:90
msgid "You can edit it and under the **General Information Tab** you will be able to change the customer taxes. Now, to change the income account, you will need to install the **Accounting App** to have the possibility to see the **Accounting Tab** on the product form."
#: ../../content/applications/sales/sales/invoicing/down_payment.rst:92
msgid "To confirm and register the first payment of the down payment, click the :guilabel:`Invoices` smart button to return to the invoice. On the :guilabel:`Customer Invoice` page, click :guilabel:`Confirm`, then :guilabel:`Register Payment` to open a :guilabel:`Register Payment` pop-up form."
msgstr ""
#: ../../content/applications/sales/sales/invoicing/down_payment.rst:-1
msgid "How the register payment pop up looks in Odoo Sales."
msgstr ""
#: ../../content/applications/sales/sales/invoicing/down_payment.rst:101
msgid "On this form, select the appropriate :guilabel:`Journal` and confirm that the down payment amount is correct in the :guilabel:`Amount` field. Then, make any other modifications to the other fields, if necessary, before clicking :guilabel:`Create Payment`."
msgstr ""
#: ../../content/applications/sales/sales/invoicing/down_payment.rst:105
msgid "Odoo returns to the invoice, which now has a green :guilabel:`In Payment` banner visible in the upper-right corner."
msgstr ""
#: ../../content/applications/sales/sales/invoicing/down_payment.rst:-1
msgid "How the initial down payment invoice has a green paid banner in Odoo Sales."
msgstr ""
#: ../../content/applications/sales/sales/invoicing/down_payment.rst:112
msgid "Now, when the customer wants to pay the remaining amount of the order, another invoice must be created. To do that, return to the sales order, and click :guilabel:`Create Invoice`."
msgstr ""
#: ../../content/applications/sales/sales/invoicing/down_payment.rst:115
msgid "On the :guilabel:`Create invoices` pop-up window, there is now an option to :guilabel:`Deduct down payments`, which is selected by default."
msgstr ""
#: ../../content/applications/sales/sales/invoicing/down_payment.rst:-1
msgid "The deduct down payment option on the create invoices pop up in Odoo Sales."
msgstr ""
#: ../../content/applications/sales/sales/invoicing/down_payment.rst:122
msgid "If the remaining amount is ready to be paid, the :guilabel:`Regular Invoice` option should be selected, and the :guilabel:`Deduct down payments` option should *stay* selected. Then, click :guilabel:`Create and View Invoice`."
msgstr ""
#: ../../content/applications/sales/sales/invoicing/down_payment.rst:126
msgid "Doing so reveals a separate :guilabel:`Invoices` page, listing all the invoices for that specific sales order. Each invoice line item displays all the necessary information related to each invoice, along with the current :guilabel:`Payment Status`."
msgstr ""
#: ../../content/applications/sales/sales/invoicing/down_payment.rst:-1
msgid "The down payment invoices page in Odoo Sales."
msgstr ""
#: ../../content/applications/sales/sales/invoicing/down_payment.rst:134
msgid "To complete the flow, select the invoice with the :guilabel:`Not Paid` status, which opens that invoice. On the invoice page, click :guilabel:`Confirm`, then :guilabel:`Register Payment`, and confirm that the remaining :guilabel:`Amount` is correct. Then, click :guilabel:`Create Payment`."
msgstr ""
#: ../../content/applications/sales/sales/invoicing/down_payment.rst:138
msgid "That pop-up window disappears, and a green :guilabel:`In Payment` banner is now present on the invoice. The line items on the invoice show that the total amount has been paid, including mentions of the down payment, and the flow is complete."
msgstr ""
#: ../../content/applications/sales/sales/invoicing/down_payment.rst:142
msgid "This flow is also possible with the :guilabel:`Fixed amount` down payment option."
msgstr ""
#: ../../content/applications/sales/sales/invoicing/down_payment.rst:145
msgid "If a down payment is used with a product that has a :guilabel:`Delivered quantities` invoicing policy, the down payments will **not** be able to be deducted when it comes time to invoice the customer. This is because, due to the invoicing policy, the product(s) would have to be delivered *before* creating the final invoice."
msgstr ""
#: ../../content/applications/sales/sales/invoicing/down_payment.rst:150
msgid "If nothing has been delivered, a :guilabel:`Credit Note` is created, which cancels the draft invoice that was created after the down payment. To utilize the :guilabel:`Credit Note` option, the *Inventory* application must be installed, in order to confirm the delivery. Otherwise, the delivered quantity can be entered manually directly on the sales order."
msgstr ""
#: ../../content/applications/sales/sales/invoicing/down_payment.rst:156
msgid "Income account and customer taxes modifications"
msgstr ""
#: ../../content/applications/sales/sales/invoicing/down_payment.rst:158
msgid "To adjust the income account and customer taxes attached to a down payment, navigate to the :guilabel:`Products` page (:menuselection:`Sales app --> Products --> Products`), search for the `Down Payment` product in the search bar, and select it to reveal the product detail page."
msgstr ""
#: ../../content/applications/sales/sales/invoicing/down_payment.rst:162
msgid "On the :guilabel:`Down Payment` product page, click :guilabel:`Edit`, then scroll down to the :guilabel:`General Information` tab. In this tab, the customer taxes can be modified in the :guilabel:`Customer Taxes` field."
msgstr ""
#: ../../content/applications/sales/sales/invoicing/down_payment.rst:-1
msgid "How to modify the income account link to down payments"
msgstr ""
#: ../../content/applications/sales/sales/invoicing/down_payment.rst:99
msgid ":doc:`invoicing_policy`"
#: ../../content/applications/sales/sales/invoicing/down_payment.rst:170
msgid "To change or adjust the income account attached to the :guilabel:`Down Payment` product page, the *Accounting* app **must** be installed. With the *Accounting* app installed, the :guilabel:`Accounting` tab becomes available on the product page. That tab will **not** be accessible without the *Accounting* app installed."
msgstr ""
#: ../../content/applications/sales/sales/invoicing/down_payment.rst:175
msgid "In the :guilabel:`Accounting` tab, the income account can be changed in the :guilabel:`Income Account` field, in the :guilabel:`Receivables` section. Once all desired changes are complete, click :guilabel:`Save`."
msgstr ""
#: ../../content/applications/sales/sales/invoicing/expense.rst:3
@ -4446,28 +4563,59 @@ msgid "You can then invoice that first milestone."
msgstr ""
#: ../../content/applications/sales/sales/invoicing/proforma.rst:3
#: ../../content/applications/sales/sales/invoicing/proforma.rst:22
msgid "Send a pro-forma invoice"
msgid "Pro-forma invoices"
msgstr ""
#: ../../content/applications/sales/sales/invoicing/proforma.rst:5
msgid "A pro-forma invoice is an abridged or estimated invoice in advance of a delivery of goods. It notes the kind and quantity of goods, their value, and other important information such as weight and transportation charges. Pro-forma invoices are commonly used as preliminary invoices with a quotation, or for customs purposes in importation. They differ from a normal invoice in not being a demand or request for payment."
msgid "A *pro-forma invoice* is an abridged or estimated invoice sent in advance of a delivery of goods. It notes the kind and quantity of goods, their value, and other important information, such as weight and transportation charges."
msgstr ""
#: ../../content/applications/sales/sales/invoicing/proforma.rst:13
#: ../../content/applications/sales/sales/invoicing/proforma.rst:9
msgid "Pro-forma invoices are commonly used as preliminary invoices with a quotation. They are also used for customs purposes during importation. They differ from a normal invoice in that they are not a demand (or request) for payment."
msgstr ""
#: ../../content/applications/sales/sales/invoicing/proforma.rst:14
msgid "Activate the feature"
msgstr ""
#: ../../content/applications/sales/sales/invoicing/proforma.rst:15
msgid "Go to :menuselection:`SALES --> Configuration --> Settings` and activate the *Pro-Forma Invoice* feature."
#: ../../content/applications/sales/sales/invoicing/proforma.rst:16
msgid "In order to utilize pro-forma invoices, the *Pro-Forma Invoice* feature **must** be activated. To do that, navigate to :menuselection:`Sales app --> Configuration --> Settings`, and in the :guilabel:`Quotations & Orders` section, click the checkbox next to :guilabel:`Pro-Forma Invoice`. Then, click :guilabel:`Save` to save all changes."
msgstr ""
#: ../../content/applications/sales/sales/invoicing/proforma.rst:24
msgid "From any quotation or sales order, you know have an option to send a pro-forma invoice."
#: ../../content/applications/sales/sales/invoicing/proforma.rst:-1
msgid "The Pro-Forma Invoice feature setting in the Odoo Sales application."
msgstr ""
#: ../../content/applications/sales/sales/invoicing/proforma.rst:30
msgid "When you click on send, Odoo will send an email with the pro-forma invoice in attachment."
#: ../../content/applications/sales/sales/invoicing/proforma.rst:26
msgid "Send a pro-forma invoice"
msgstr ""
#: ../../content/applications/sales/sales/invoicing/proforma.rst:28
msgid "With the :guilabel:`Pro-Forma Invoice` feature activated, the option to send a pro-forma invoice is now available on any quotation or sales order, via the :guilabel:`Send Pro-Forma Invoice` button."
msgstr ""
#: ../../content/applications/sales/sales/invoicing/proforma.rst:-1
msgid "The Send Pro-Forma Invoice button on a typical sales order in Odoo Sales."
msgstr ""
#: ../../content/applications/sales/sales/invoicing/proforma.rst:35
msgid "When the :guilabel:`Send Pro-Forma Invoice` button is clicked, an email pop-up appears. The :guilabel:`Recipients` field is auto-populated with the customer from the sales order or quotation. Then, if needed, modify the :guilabel:`Subject` field and the body of the email. The pro-forma invoice is automatically added as an attachment to the email."
msgstr ""
#: ../../content/applications/sales/sales/invoicing/proforma.rst:40
msgid "When ready, click :guilabel:`Send`, and Odoo instantly sends the email, with the attached pro-forma invoice, to the customer."
msgstr ""
#: ../../content/applications/sales/sales/invoicing/proforma.rst:-1
msgid "The email pop-up window that appears with pro-forma invoice attached in Odoo Sales."
msgstr ""
#: ../../content/applications/sales/sales/invoicing/proforma.rst:48
msgid "To preview what the pro-forma invoice looks like, click on the PDF at the bottom of the email pop-up window *before* clicking :guilabel:`Send`. When clicked, the pro-forma invoice is downloaded instantly. Open that PDF to view (and review) the pro-forma invoice."
msgstr ""
#: ../../content/applications/sales/sales/invoicing/proforma.rst:0
msgid "Sample pro-forma invoice PDF from Odoo Sales."
msgstr ""
#: ../../content/applications/sales/sales/invoicing/time_materials.rst:3
@ -4767,7 +4915,6 @@ msgid "The Odoo *Sales*, *eCommerce*, and *Point of Sale* applications allow use
msgstr ""
#: ../../content/applications/sales/sales/products_prices/loyalty_discount.rst:11
#: ../../content/applications/sales/sales/send_quotations/different_addresses.rst:10
msgid "Configure the settings"
msgstr ""
@ -5802,78 +5949,9 @@ msgstr ""
#: ../../content/applications/sales/sales/send_quotations/get_paid_to_validate.rst:50
#: ../../content/applications/sales/sales/send_quotations/get_signature_to_validate.rst:51
#: ../../content/applications/sales/sales/send_quotations/optional_products.rst:65
#: ../../content/applications/sales/sales/send_quotations/terms_and_conditions.rst:115
msgid ":doc:`quote_template`"
msgstr ""
#: ../../content/applications/sales/sales/send_quotations/different_addresses.rst:3
msgid "Deliver and invoice to different addresses"
msgstr ""
#: ../../content/applications/sales/sales/send_quotations/different_addresses.rst:5
msgid "People and businesses often use separate addresses for billing (invoicing) and shipping (delivery) purposes. With the Odoo *Sales* app, contacts can have different specified addresses for delivery and invoicing."
msgstr ""
#: ../../content/applications/sales/sales/send_quotations/different_addresses.rst:12
msgid "Go to :menuselection:`Invoicing --> Configuration --> Settings` and scroll down to the :guilabel:`Customer Invoices` section. Then, check the box next to :guilabel:`Customer Addresses`, and click :guilabel:`Save`."
msgstr ""
#: ../../content/applications/sales/sales/send_quotations/different_addresses.rst:17
msgid "Navigating through the *Invoicing* app will not be possible if the *Accounting* app has been installed. Instead, go through :menuselection:`Accounting --> Configuration --> Settings` to enable the :guilabel:`Customer Addresses` feature."
msgstr ""
#: ../../content/applications/sales/sales/send_quotations/different_addresses.rst:-1
msgid "Activate the Customer Addresses setting."
msgstr ""
#: ../../content/applications/sales/sales/send_quotations/different_addresses.rst:26
msgid "Configure the contact form"
msgstr ""
#: ../../content/applications/sales/sales/send_quotations/different_addresses.rst:28
msgid "Navigate to the :menuselection:`Contacts` app (or to :menuselection:`Sales --> Orders --> Customers`), and click on a customer to open their contact form."
msgstr ""
#: ../../content/applications/sales/sales/send_quotations/different_addresses.rst:31
msgid "Under the :guilabel:`Contacts & Addresses` tab, click :guilabel:`Add`."
msgstr ""
#: ../../content/applications/sales/sales/send_quotations/different_addresses.rst:-1
msgid "Add a contact/address to the contact form"
msgstr ""
#: ../../content/applications/sales/sales/send_quotations/different_addresses.rst:37
msgid "Then, select which type of address to add to the contact form (i.e. :guilabel:`Invoice Address` or :guilabel:`Delivery Address`)."
msgstr ""
#: ../../content/applications/sales/sales/send_quotations/different_addresses.rst:-1
msgid "Create a new contact/address on a contact form."
msgstr ""
#: ../../content/applications/sales/sales/send_quotations/different_addresses.rst:44
msgid "Enter the address information. Then click :guilabel:`Save & Close` to save the address and close the :guilabel:`Create Contact` window. Or, click :guilabel:`Save & New` to save this address and immediately input another one."
msgstr ""
#: ../../content/applications/sales/sales/send_quotations/different_addresses.rst:49
msgid "Add addresses to the quotation"
msgstr ""
#: ../../content/applications/sales/sales/send_quotations/different_addresses.rst:51
msgid "When a customer is added to a quotation, the :guilabel:`Invoice Address` and :guilabel:`Delivery Address` fields will autopopulate according to the addresses specified on the customer's contact form."
msgstr ""
#: ../../content/applications/sales/sales/send_quotations/different_addresses.rst:-1
msgid "Invoice and Delivery Addresses autopopulate on a quotation."
msgstr ""
#: ../../content/applications/sales/sales/send_quotations/different_addresses.rst:59
msgid "The :guilabel:`Invoice Address` and :guilabel:`Delivery Address` can also be edited directly from the quotation by clicking on the :guilabel:`Internal link` buttons next to each address line."
msgstr ""
#: ../../content/applications/sales/sales/send_quotations/different_addresses.rst:62
msgid "These addresses can be updated at any time to ensure accurate invoicing and delivery."
msgstr ""
#: ../../content/applications/sales/sales/send_quotations/get_paid_to_validate.rst:3
msgid "Get paid to confirm an order"
msgstr ""
@ -6112,217 +6190,99 @@ msgid "Line items for grid variants."
msgstr ""
#: ../../content/applications/sales/sales/send_quotations/quote_template.rst:3
msgid "Use quotation templates"
msgid "Quotation templates"
msgstr ""
#: ../../content/applications/sales/sales/send_quotations/quote_template.rst:5
msgid "By creating custom quotation templates, you will save a lot of time. Indeed, with the use of templates, you will be able to send complete quotations at a fast pace."
msgid "Using quotation templates speeds up the creation of sales orders by filling in most quotation fields automatically."
msgstr ""
#: ../../content/applications/sales/sales/send_quotations/quote_template.rst:11
msgid "To enable this feature, go to :menuselection:`Sales --> Configuration --> Settings` and activate **Quotation Templates**."
msgid "Go to :menuselection:`Sales --> Configuration --> Settings` and enable :guilabel:`Quotation Templates`."
msgstr ""
#: ../../content/applications/sales/sales/send_quotations/quote_template.rst:-1
msgid "How to enable quotation templates on Odoo Sales?"
#: ../../content/applications/sales/sales/send_quotations/quote_template.rst:15
msgid "Create a template"
msgstr ""
#: ../../content/applications/sales/sales/send_quotations/quote_template.rst:19
msgid "For even more convenience, it is also recommended to add the **Quotation Builder** feature which will help you design your quotation templates very easily. This option will automatically install the Odoo Website App."
#: ../../content/applications/sales/sales/send_quotations/quote_template.rst:17
msgid "Go to :menuselection:`Sales --> Configuration --> Quotations Templates` and click :guilabel:`New`."
msgstr ""
#: ../../content/applications/sales/sales/send_quotations/quote_template.rst:-1
msgid "How to enable quotation builder on Odoo Sales?"
#: ../../content/applications/sales/sales/send_quotations/quote_template.rst:20
msgid "Apart from the name, all template fields are optional."
msgstr ""
#: ../../content/applications/sales/sales/send_quotations/quote_template.rst:22
msgid "After having named the template, choose default values for the following fields:"
msgstr ""
#: ../../content/applications/sales/sales/send_quotations/quote_template.rst:24
msgid ":guilabel:`Quotation expires after`: choose the number of days for which the quotation is valid."
msgstr ""
#: ../../content/applications/sales/sales/send_quotations/quote_template.rst:25
msgid ":guilabel:`Online confirmation`: after sending the quotation by email, it is possible to ask the customer to confirm it online on their customer portal:"
msgstr ""
#: ../../content/applications/sales/sales/send_quotations/quote_template.rst:28
msgid "by providing a :guilabel:`Signature`,"
msgstr ""
#: ../../content/applications/sales/sales/send_quotations/quote_template.rst:29
msgid "Create your first template"
msgid "by making a :guilabel:`Payment`,"
msgstr ""
#: ../../content/applications/sales/sales/send_quotations/quote_template.rst:31
msgid "Quotation templates are under :menuselection:`Sales --> Configuration`."
#: ../../content/applications/sales/sales/send_quotations/quote_template.rst:30
msgid "or both."
msgstr ""
#: ../../content/applications/sales/sales/send_quotations/quote_template.rst:33
msgid "You can create a new template or edit an existing one. Once named, you will be able to select products and quantities as well as the expiration time of the quotation."
#: ../../content/applications/sales/sales/send_quotations/quote_template.rst:32
msgid ":guilabel:`Confirmation Mail`: select an email template to automatically send an email to the customer upon confirming the quotation."
msgstr ""
#: ../../content/applications/sales/sales/send_quotations/quote_template.rst:35
msgid "On the :guilabel:`Lines` tab, add the default products and their quantity. Add :doc:`optional products <optional_products>` in the :guilabel:`Optional Products` tab."
msgstr ""
#: ../../content/applications/sales/sales/send_quotations/quote_template.rst:38
msgid "Finally, add any specific sales terms and conditions on the :guilabel:`Terms & Conditions` tab."
msgstr ""
#: ../../content/applications/sales/sales/send_quotations/quote_template.rst:41
msgid "If the terms and conditions are standard across all quotations, :doc:`set them globally in the Accounting/Invoicing settings </applications/finance/accounting/customer_invoices/terms_conditions>` instead."
msgstr ""
#: ../../content/applications/sales/sales/send_quotations/quote_template.rst:46
msgid "Design a template"
msgstr ""
#: ../../content/applications/sales/sales/send_quotations/quote_template.rst:48
msgid "Customize the appearance of quotations on the customer portal by going to :menuselection:`Sales --> Configuration --> Settings` and enabling the :guilabel:`Quotation Builder` feature."
msgstr ""
#: ../../content/applications/sales/sales/send_quotations/quote_template.rst:52
msgid "If necessary, Odoo automatically activates the :doc:`Website </applications/websites/website>` app when enabling this feature."
msgstr ""
#: ../../content/applications/sales/sales/send_quotations/quote_template.rst:55
msgid "Select a template by going to :menuselection:`Sales --> Configuration --> Quotations Templates` and clicking on a template. Then click the :guilabel:`Design Template` button. On the website builder, click :guilabel:`Edit`. Drag and drop the building blocks, edit the content, and :guilabel:`Save`."
msgstr ""
#: ../../content/applications/sales/sales/send_quotations/quote_template.rst:-1
msgid "Create a new quotation template on Odoo Sales"
msgstr ""
#: ../../content/applications/sales/sales/send_quotations/quote_template.rst:42
msgid "Design your template"
msgstr ""
#: ../../content/applications/sales/sales/send_quotations/quote_template.rst:44
msgid "You will have the possibility to design your template and edit the customer interface in order to manage what clients will see before accepting and paying the quotation. For example, you will be able to describe your company, your services and your products. To do so, you can click on **Edit** and you will be brought to the quotation builder."
msgstr ""
#: ../../content/applications/sales/sales/send_quotations/quote_template.rst:-1
msgid "Design your quotation template on Odoo Sales"
msgstr ""
#: ../../content/applications/sales/sales/send_quotations/quote_template.rst:54
msgid "You can easily edit the content of your template by dragging & dropping different building blocks to organize your quotation. For example, you can add a content block to describe your products."
msgstr ""
#: ../../content/applications/sales/sales/send_quotations/quote_template.rst:-1
msgid "Drag & drop building blocks to create your quotation template on Odoo Sales"
msgid "Using the quotation builder"
msgstr ""
#: ../../content/applications/sales/sales/send_quotations/quote_template.rst:63
msgid "Use a quotation template"
msgid "Use a template"
msgstr ""
#: ../../content/applications/sales/sales/send_quotations/quote_template.rst:65
msgid "When creating a quotation, you can choose a specific template."
msgid "When creating a quotation, choose a template under the :guilabel:`Quotation Template` field. All the fields are then filled accordingly. Manually edit any pre-filled field if needed."
msgstr ""
#: ../../content/applications/sales/sales/send_quotations/quote_template.rst:-1
msgid "Select a specific template on Odoo Sales"
msgstr ""
#: ../../content/applications/sales/sales/send_quotations/quote_template.rst:73
msgid "You can select any template of your choice and suggest it as the default template in the **Sales** settings."
msgstr ""
#: ../../content/applications/sales/sales/send_quotations/quote_template.rst:77
msgid "Confirm the quotation"
msgstr ""
#: ../../content/applications/sales/sales/send_quotations/quote_template.rst:79
msgid "Templates facilitate the confirmation process by allowing customers to sign electronically or to pay online. You can activate these two options directly in the quotation template itself."
msgstr ""
#: ../../content/applications/sales/sales/send_quotations/quote_template.rst:-1
msgid "Allow your customers to sign electronically or to pay online on Odoo Sales"
msgstr ""
#: ../../content/applications/sales/sales/send_quotations/quote_template.rst:88
msgid "Every quotation will now have this setting. Of course you can always change it and make it specific for each quotation."
msgstr ""
#: ../../content/applications/sales/sales/send_quotations/quote_template.rst:92
#: ../../content/applications/sales/sales/send_quotations/terms_and_conditions.rst:116
msgid ":doc:`get_signature_to_validate`"
msgstr ""
#: ../../content/applications/sales/sales/send_quotations/quote_template.rst:93
#: ../../content/applications/sales/sales/send_quotations/terms_and_conditions.rst:117
msgid ":doc:`get_paid_to_validate`"
msgstr ""
#: ../../content/applications/sales/sales/send_quotations/terms_and_conditions.rst:3
msgid "Add terms & conditions"
msgstr ""
#: ../../content/applications/sales/sales/send_quotations/terms_and_conditions.rst:5
msgid "Specifying terms and conditions is essential to set out important contractual points such as payment terms, limitation of liability and delivery terms between customers and sellers. Every seller must declare all formal information concerning products and company policy. On the other hand, each customer must take note of all these conditions before committing to anything. With Odoo Sales, it is very easy to include your default terms and conditions on every quotation, sales order, and invoice that you manage."
msgstr ""
#: ../../content/applications/sales/sales/send_quotations/terms_and_conditions.rst:13
msgid "Default Terms & Conditions"
msgstr ""
#: ../../content/applications/sales/sales/send_quotations/terms_and_conditions.rst:18
msgid "Go to :menuselection:`Accounting --> Configuration --> Settings` and activate *Default Terms & Conditions*."
msgstr ""
#: ../../content/applications/sales/sales/send_quotations/terms_and_conditions.rst:-1
msgid "How to enable Default Terms & Conditions on Odoo Sales?"
msgstr ""
#: ../../content/applications/sales/sales/send_quotations/terms_and_conditions.rst:27
msgid "Please note that this feature is activated via the settings of the **Invoicing App** and **not** via the settings of the **Sales App**. Moreover, you don't need to install the invoicing application since it is done automatically with the installation of the sales application."
msgstr ""
#: ../../content/applications/sales/sales/send_quotations/terms_and_conditions.rst:32
msgid "DT&C on your quotations, sales orders, and invoices"
msgstr ""
#: ../../content/applications/sales/sales/send_quotations/terms_and_conditions.rst:34
msgid "In the settings of the **Invoicing App**, you have the possibility to insert your default terms and conditions."
msgstr ""
#: ../../content/applications/sales/sales/send_quotations/terms_and_conditions.rst:-1
msgid "Default Terms & Conditions on quotation on Odoo Sales"
msgstr ""
#: ../../content/applications/sales/sales/send_quotations/terms_and_conditions.rst:42
msgid "They appear subsequently on every quotation, sales order, and invoice."
msgstr ""
#: ../../content/applications/sales/sales/send_quotations/terms_and_conditions.rst:45
msgid "DT&C on your quotation templates"
msgstr ""
#: ../../content/applications/sales/sales/send_quotations/terms_and_conditions.rst:47
msgid "According to your business needs, you can specify your terms and conditions on your quotation templates. This is interesting if you have different terms and conditions within your company."
msgstr ""
#: ../../content/applications/sales/sales/send_quotations/terms_and_conditions.rst:-1
msgid "Add Default Terms & Conditions to your quotation templates on Odoo Sales"
msgstr ""
#: ../../content/applications/sales/sales/send_quotations/terms_and_conditions.rst:56
msgid "Be sure to check out our documentation about quotation templates: :doc:`quote_template`, to master each step of this amazing feature."
msgstr ""
#: ../../content/applications/sales/sales/send_quotations/terms_and_conditions.rst:60
msgid "General Terms & Conditions"
msgstr ""
#: ../../content/applications/sales/sales/send_quotations/terms_and_conditions.rst:63
msgid "GT&C on your website"
msgstr ""
#: ../../content/applications/sales/sales/send_quotations/terms_and_conditions.rst:65
msgid "Use the **Website App** and create your own general terms and conditions page. For example, here is the Odoo terms and conditions page:"
msgstr ""
#: ../../content/applications/sales/sales/send_quotations/terms_and_conditions.rst:-1
msgid "General Terms & Conditions on your website"
msgstr ""
#: ../../content/applications/sales/sales/send_quotations/terms_and_conditions.rst:73
msgid "You can refer to this page in the footer of all your documents. The layout is available in the **General Settings** under the **Business Documents** category. For example, this footer appears in every document from Odoo."
msgstr ""
#: ../../content/applications/sales/sales/send_quotations/terms_and_conditions.rst:-1
msgid "General Terms & Conditions in your business documents"
msgstr ""
#: ../../content/applications/sales/sales/send_quotations/terms_and_conditions.rst:83
msgid "GT&C as attachment in your emails"
msgstr ""
#: ../../content/applications/sales/sales/send_quotations/terms_and_conditions.rst:85
msgid "Attach an external document with your general terms and conditions when you are about to send your quotation by email to your customers."
msgstr ""
#: ../../content/applications/sales/sales/send_quotations/terms_and_conditions.rst:-1
msgid "General Terms & conditions as attachment in your email"
msgstr ""
#: ../../content/applications/sales/sales/send_quotations/terms_and_conditions.rst:94
msgid "GT&C as attachment in your quotation templates"
msgstr ""
#: ../../content/applications/sales/sales/send_quotations/terms_and_conditions.rst:96
msgid "Create and edit email templates to set a default attachment for all quotation emails that you will send in the future. To do so, you have to go to :menuselection:`Sales --> Configuration --> Quotation templates` and create a new quotation template or modify an existing one. Under the confirmation tab, you are now able to activate online signatures, online payments and to set a confirmation mail in which you have the possibility to configure the default attachment. There, you can put your general terms & conditions."
msgstr ""
#: ../../content/applications/sales/sales/send_quotations/terms_and_conditions.rst:-1
msgid "General Terms & conditions as attachment in your quotation templates"
msgstr ""
#: ../../content/applications/sales/sales/send_quotations/terms_and_conditions.rst:109
msgid "To customize your email templates, activate the **developer mode** and go to :menuselection:`Settings --> Technical --> Email --> Templates`."
msgstr ""
#: ../../content/applications/sales/sales/send_quotations/terms_and_conditions.rst:112
msgid "With Odoo Sales it is now very simple to deal with terms & conditions."
#: ../../content/applications/sales/sales/send_quotations/quote_template.rst:69
msgid "Go to :menuselection:`Sales --> Configuration --> Settings` to select a :guilabel:`Default Template`."
msgstr ""
#: ../../content/applications/sales/subscriptions.rst:5
@ -6390,7 +6350,7 @@ msgid "Fill out the quotation normally, making sure to select a recurrence and a
msgstr ""
#: ../../content/applications/sales/subscriptions.rst:42
msgid "You can define different invoice and delivery addresses by enabling the :doc:`Customer Addresses </applications/sales/sales/send_quotations/different_addresses>` feature."
msgid "You can define different invoice and delivery addresses by enabling the :doc:`Customer Addresses </applications/finance/accounting/customer_invoices/customer_addresses>` feature."
msgstr ""
#: ../../content/applications/sales/subscriptions.rst:48
@ -6763,7 +6723,7 @@ msgid "In the :guilabel:`Optional Products` tab, enter any optional products tha
msgstr ""
#: ../../content/applications/sales/subscriptions/plans.rst:77
msgid "If the subscription plan has unique :doc:`terms and conditions </applications/sales/sales/send_quotations/terms_and_conditions>`, add them in the :guilabel:`Terms & Conditions` tab. If terms conditions are specified on a plan, these will be used instead of the default terms and conditions set up in the *Sales* app settings."
msgid "If the subscription plan has unique :doc:`terms and conditions </applications/finance/accounting/customer_invoices/terms_conditions>`, add them in the :guilabel:`Terms & Conditions` tab. If terms conditions are specified on a plan, these will be used instead of the default terms and conditions set up in the *Sales* app settings."
msgstr ""
#: ../../content/applications/sales/subscriptions/plans.rst:-1

645
locale/sources/services.pot
View File

@ -8,7 +8,7 @@ msgid ""
msgstr ""
"Project-Id-Version: Odoo 16.0\n"
"Report-Msgid-Bugs-To: \n"
"POT-Creation-Date: 2023-06-02 08:43+0000\n"
"POT-Creation-Date: 2023-07-03 09:37+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"
@ -882,93 +882,6 @@ msgstr ""
msgid "Overview"
msgstr ""
#: ../../content/applications/services/helpdesk/overview/forum_and_elearning.rst:3
msgid "Forum and eLearning"
msgstr ""
#: ../../content/applications/services/helpdesk/overview/forum_and_elearning.rst:6
msgid "Forum"
msgstr ""
#: ../../content/applications/services/helpdesk/overview/forum_and_elearning.rst:8
msgid "To go above and beyond email, live chat, web forms, and phone lines, offer your customers a support forum. This way, customers might become more attached to your company as they would be investing time to get into details of your business. You also encourage the exchange of experiences and knowledge, supporting the feeling of belonging to a community (your community!)."
msgstr ""
#: ../../content/applications/services/helpdesk/overview/forum_and_elearning.rst:14
#: ../../content/applications/services/helpdesk/overview/forum_and_elearning.rst:52
msgid "Set up"
msgstr ""
#: ../../content/applications/services/helpdesk/overview/forum_and_elearning.rst:16
msgid "Go to :menuselection:`Helpdesk --> Configuration --> Helpdesk Team` and enable *Help Center*."
msgstr ""
#: ../../content/applications/services/helpdesk/overview/forum_and_elearning.rst:-1
msgid "Overview of the settings page of a helpdesk team emphasizing the help center feature in\n"
"Odoo Helpdesk"
msgstr ""
#: ../../content/applications/services/helpdesk/overview/forum_and_elearning.rst:23
msgid "Create, or edit a forum by clicking on the external link. Among the editing options, choose if you would like the *Forum Mode* to be *Questions*: only one answer is allowed per question or *Discussions*: multiple answers are allowed per question."
msgstr ""
#: ../../content/applications/services/helpdesk/overview/forum_and_elearning.rst:-1
msgid "Overview of a forum’s settings page in Odoo Helpdesk"
msgstr ""
#: ../../content/applications/services/helpdesk/overview/forum_and_elearning.rst:31
msgid "From now on, logged in users can start their discussions. To keep track of posts, go to :menuselection:`Website --> Forum --> Posts`."
msgstr ""
#: ../../content/applications/services/helpdesk/overview/forum_and_elearning.rst:-1
msgid "Overview of the Forums page of a website to show the available ones in Odoo Helpdesk"
msgstr ""
#: ../../content/applications/services/helpdesk/overview/forum_and_elearning.rst:38
msgid "Turn tickets into forum posts by simply clicking on *Share on the Forum* on the ticket's page."
msgstr ""
#: ../../content/applications/services/helpdesk/overview/forum_and_elearning.rst:45
msgid "eLearning"
msgstr ""
#: ../../content/applications/services/helpdesk/overview/forum_and_elearning.rst:47
msgid "In addition to a forum, offer online courses. When doing so, you link your customers and users’ needs and questions to useful content, helping to boost efficiency as they can also find their answers there."
msgstr ""
#: ../../content/applications/services/helpdesk/overview/forum_and_elearning.rst:54
msgid "Go to :menuselection:`Helpdesk --> Configuration --> Helpdesk Teams` and enable *eLearning*."
msgstr ""
#: ../../content/applications/services/helpdesk/overview/forum_and_elearning.rst:-1
msgid "Overview of the settings page of a customer care team emphasizing the feature elearning in\n"
"Odoo Helpdesk"
msgstr ""
#: ../../content/applications/services/helpdesk/overview/forum_and_elearning.rst:61
msgid "Once the structure and content of your course are ready, *Publish* it by clicking on *Unpublished*."
msgstr ""
#: ../../content/applications/services/helpdesk/overview/forum_and_elearning.rst:-1
msgid "View of a course being published for Odoo Helpdesk"
msgstr ""
#: ../../content/applications/services/helpdesk/overview/forum_and_elearning.rst:67
msgid "To keep track of your course statistics, go to *eLearning* and *View Course*."
msgstr ""
#: ../../content/applications/services/helpdesk/overview/forum_and_elearning.rst:-1
msgid "View of the elearning applications dashboard for Odoo Helpdesk"
msgstr ""
#: ../../content/applications/services/helpdesk/overview/forum_and_elearning.rst:73
msgid "Todo"
msgstr ""
#: ../../content/applications/services/helpdesk/overview/forum_and_elearning.rst:73
msgid "DETAILS/INFO SHOULD COME FROM ELEARNING DOCS. THEREFORE, LINK DOCS ONCE AVAILABLE!"
msgstr ""
#: ../../content/applications/services/helpdesk/overview/getting_started.rst:3
msgid "Getting started with Helpdesk"
msgstr ""
@ -1171,6 +1084,562 @@ msgstr ""
msgid "Manually folding a stage from the kanban view will not close the tickets in the stage."
msgstr ""
#: ../../content/applications/services/helpdesk/overview/help_center.rst:3
msgid "Help center"
msgstr ""
#: ../../content/applications/services/helpdesk/overview/help_center.rst:5
msgid "Odoo *Helpdesk* integrates with the *Forums*, *eLearning*, and *Knowledge* apps to create the *help center*."
msgstr ""
#: ../../content/applications/services/helpdesk/overview/help_center.rst:-1
msgid "Overview of the settings page of a team emphasizing the help center features."
msgstr ""
#: ../../content/applications/services/helpdesk/overview/help_center.rst:12
msgid "The *help center* is a centralized location where teams and customers can search for and share detailed information about products and services."
msgstr ""
#: ../../content/applications/services/helpdesk/overview/help_center.rst:16
msgid "In order to activate any of these features on a *Helpdesk* team, (*Forums*, *eLearning*, or *Knowledge*), the :guilabel:`Visibility` of the team has to be set to :guilabel:`Invited portal users and all internal users`. See :doc:`Getting Started </applications/services/helpdesk/overview/getting_started>` for more information on *Helpdesk* team settings and configuration."
msgstr ""
#: ../../content/applications/services/helpdesk/overview/help_center.rst:23
msgid "Since all of the *help center* features require integration with other applications, enabling any of them may result in the installation of additional modules or applications."
msgstr ""
#: ../../content/applications/services/helpdesk/overview/help_center.rst:26
msgid "Installing a new application on a *One-App-Free* database will trigger a 15-day trial. At the end of the trial, if a paid subscription has not been added to the database, it will no longer be active or accessible."
msgstr ""
#: ../../content/applications/services/helpdesk/overview/help_center.rst:31
msgid "Knowledge"
msgstr ""
#: ../../content/applications/services/helpdesk/overview/help_center.rst:33
msgid "Odoo's *Knowledge* application is a collaborative library where users can store, edit, and share information. The *Knowledge* app is represented throughout the database by a *book* icon."
msgstr ""
#: ../../content/applications/services/helpdesk/overview/help_center.rst:-1
msgid "View of a message in Helpdesk focusing on the Knowledge book icon."
msgstr ""
#: ../../content/applications/services/helpdesk/overview/help_center.rst:41
msgid "Enable Knowledge on a Helpdesk team"
msgstr ""
#: ../../content/applications/services/helpdesk/overview/help_center.rst:43
msgid "To enable the *Knowledge* feature on a *Helpdesk* team, go to :menuselection:`Helpdesk --> Configuration --> Teams` and select a team, or create a :doc:`new one </applications/services/helpdesk/overview/getting_started>`."
msgstr ""
#: ../../content/applications/services/helpdesk/overview/help_center.rst:47
msgid "When a team has been selected or created, Odoo displays that team's detail form."
msgstr ""
#: ../../content/applications/services/helpdesk/overview/help_center.rst:49
msgid "On the team's detail form, scroll down to the :guilabel:`Self-Service` section. Click the box next to :guilabel:`Knowledge` to activate the *Knowledge* feature. When clicked, a new field labeled :guilabel:`Article` appears."
msgstr ""
#: ../../content/applications/services/helpdesk/overview/help_center.rst:53
msgid "Clicking the :guilabel:`Article` field reveals a drop-down menu. At first, there is only one option in the drop-down menu titled :guilabel:`Help`, which Odoo provides by default. Select :guilabel:`Help` from the drop-down menu to choose this article."
msgstr ""
#: ../../content/applications/services/helpdesk/overview/help_center.rst:58
msgid "To create a new article, go to the :menuselection:`Knowledge app`, then hover the cursor next to the :guilabel:`Workspace` section heading, located in the left sidebar. Moving the cursor there reveals a hidden :guilabel:`➕ (plus sign)` icon."
msgstr ""
#: ../../content/applications/services/helpdesk/overview/help_center.rst:62
msgid "Click the :guilabel:`➕ (plus sign)` to create a new article in the :guilabel:`Workspace`. In the upper right corner of the page, click the :guilabel:`Share` button, and slide the :guilabel:`Share to Web` toggle switch until it reads :guilabel:`Article Published`. It can then be added to a *Helpdesk* team."
msgstr ""
#: ../../content/applications/services/helpdesk/overview/help_center.rst:67
msgid "Once an article has been created and assigned to a *Helpdesk* team, content can be added and organized through the *Knowledge* app."
msgstr ""
#: ../../content/applications/services/helpdesk/overview/help_center.rst:71
msgid ":doc:`Editing Knowledge articles </applications/productivity/knowledge/articles_editing>`"
msgstr ""
#: ../../content/applications/services/helpdesk/overview/help_center.rst:74
msgid "Search articles from a Helpdesk ticket"
msgstr ""
#: ../../content/applications/services/helpdesk/overview/help_center.rst:76
msgid "When members of a *Helpdesk* team are trying to solve a ticket, they can search through the content in the *Knowledge* app for more information on the issue."
msgstr ""
#: ../../content/applications/services/helpdesk/overview/help_center.rst:79
msgid "To search *Knowledge* articles, open a ticket — either from the *Helpdesk* app dashboard, or by going to :menuselection:`Helpdesk app --> Tickets --> All Tickets`, and selecting a :guilabel:`Ticket` from the list."
msgstr ""
#: ../../content/applications/services/helpdesk/overview/help_center.rst:83
msgid "When a :guilabel:`Ticket` is selected, Odoo reveals that ticket's detail form."
msgstr ""
#: ../../content/applications/services/helpdesk/overview/help_center.rst:85
msgid "Click the :guilabel:`Knowledge (book)` icon, located above the chatter to open a search window."
msgstr ""
#: ../../content/applications/services/helpdesk/overview/help_center.rst:-1
msgid "View of knowledge search window from a helpdesk ticket."
msgstr ""
#: ../../content/applications/services/helpdesk/overview/help_center.rst:92
msgid "*Knowledge* articles can also be searched by pressing :command:`Ctrl + K` to open the command palette, then typing :command:`?`, followed by the name of the desired article."
msgstr ""
#: ../../content/applications/services/helpdesk/overview/help_center.rst:95
msgid "When Odoo reveals the desired article, click it, or highlight the :guilabel:`Article` title, and press :command:`Enter`. This will open the article in the :guilabel:`Knowledge` application."
msgstr ""
#: ../../content/applications/services/helpdesk/overview/help_center.rst:98
msgid "To open the article in a new tab, press :command:`Ctrl + Enter`."
msgstr ""
#: ../../content/applications/services/helpdesk/overview/help_center.rst:101
msgid "If a more in-depth search is required, press :command:`Alt + B`. That will reveal a separate page, in which a more detailed search can occur."
msgstr ""
#: ../../content/applications/services/helpdesk/overview/help_center.rst:105
msgid "Share articles to the help center"
msgstr ""
#: ../../content/applications/services/helpdesk/overview/help_center.rst:107
msgid "In order for a *Knowledge* article to be available to customers and website visitors, it has to be published."
msgstr ""
#: ../../content/applications/services/helpdesk/overview/help_center.rst:111
msgid "Even though the *Help* article has been enabled on a team, Odoo will not share all the nested articles to the web. Individual articles intended for customers **must** be published for them to be viewable on the website."
msgstr ""
#: ../../content/applications/services/helpdesk/overview/help_center.rst:115
msgid "To publish an article, navigate to the desired article, by following the above steps, and click the :guilabel:`Share` icon in the upper-right corner. This will reveal a menu. Slide the toggle button labeled :guilabel:`Share to Web` to read :guilabel:`Article Published`."
msgstr ""
#: ../../content/applications/services/helpdesk/overview/help_center.rst:-1
msgid "View of a knowledge article focused on sharing and publishing options."
msgstr ""
#: ../../content/applications/services/helpdesk/overview/help_center.rst:124
msgid "Solve tickets with templates"
msgstr ""
#: ../../content/applications/services/helpdesk/overview/help_center.rst:126
msgid "*Template* boxes can be added to *Knowledge* articles to allow content to be reused, copied, sent as messages, or added to the description on a ticket. This allows teams to maintain consistency when answering customer tickets, and minimize the amount of time spent on responding to repeat questions."
msgstr ""
#: ../../content/applications/services/helpdesk/overview/help_center.rst:131
msgid "Add templates to articles"
msgstr ""
#: ../../content/applications/services/helpdesk/overview/help_center.rst:133
msgid "To create a template, go to :menuselection:`Knowledge --> Help`. Click on an existing nested article or create a new one by clicking the :guilabel:`➕ (plus sign)` icon next to *Help*."
msgstr ""
#: ../../content/applications/services/helpdesk/overview/help_center.rst:136
msgid "Type `/` to open the :guilabel:`Powerbox` and view a list of :doc:`commands </applications/productivity/knowledge/articles_editing>`. Select or type `template`. A gray template block will be added to the page. Add any necessary content to this block."
msgstr ""
#: ../../content/applications/services/helpdesk/overview/help_center.rst:-1
msgid "View of a template in knowledge with focus on send and copy options."
msgstr ""
#: ../../content/applications/services/helpdesk/overview/help_center.rst:145
msgid "Templates will only display the :guilabel:`Use as description` or :guilabel:`Send as Message` options if they are accessed directly from *Helpdesk*."
msgstr ""
#: ../../content/applications/services/helpdesk/overview/help_center.rst:149
msgid "Use templates in tickets"
msgstr ""
#: ../../content/applications/services/helpdesk/overview/help_center.rst:151
msgid "Templates can be used to respond directly to a *Helpdesk* ticket as a message, or to add information to the ticket's description."
msgstr ""
#: ../../content/applications/services/helpdesk/overview/help_center.rst:154
msgid "To use templates in a *Helpdesk* ticket, first, open a ticket, either from the :guilabel:`Helpdesk` dashboard or by going to :menuselection:`Helpdesk --> Tickets --> All Tickets` and selecting a :guilabel:`Ticket` from the list."
msgstr ""
#: ../../content/applications/services/helpdesk/overview/help_center.rst:158
msgid "Click on the :guilabel:`Knowledge (book)` icon above the chatter for the ticket. This opens a search window. In this search window, select, or search for the desired article. Doing so reveals that article page in the Odoo *Knowledge* application."
msgstr ""
#: ../../content/applications/services/helpdesk/overview/help_center.rst:162
msgid "To use a template to respond to a ticket, click :guilabel:`Send as message` in the upper right corner of the template box, located in the body of the article."
msgstr ""
#: ../../content/applications/services/helpdesk/overview/help_center.rst:165
msgid "Doing so opens a :guilabel:`Compose email` pop-up window. In this window, select the recipients, make any necessary additions or edits to the template, then click :guilabel:`Send`."
msgstr ""
#: ../../content/applications/services/helpdesk/overview/help_center.rst:169
msgid "To use a template to add information to a ticket's description, click :guilabel:`Use as description` in the upper right corner of the template box, located in the body of the article. Doing so will not replace the existing text in a ticket's description. The template will be added as additional text."
msgstr ""
#: ../../content/applications/services/helpdesk/overview/help_center.rst:175
msgid "Community Forum"
msgstr ""
#: ../../content/applications/services/helpdesk/overview/help_center.rst:177
msgid "A *Community Forum* provides a space for customers to answer each other's questions and share information. By integrating a forum with a *Helpdesk* team, tickets submitted by customers can be converted to posts and shared."
msgstr ""
#: ../../content/applications/services/helpdesk/overview/help_center.rst:182
msgid "Enable forums on a Helpdesk team"
msgstr ""
#: ../../content/applications/services/helpdesk/overview/help_center.rst:184
msgid "To enable :guilabel:`Community Forums` on a *Helpdesk* team, start by navigating to :menuselection:`Helpdesk app --> Configuration --> Teams` and select a team, or create a :doc:`new one </applications/services/helpdesk/overview/getting_started>`."
msgstr ""
#: ../../content/applications/services/helpdesk/overview/help_center.rst:188
msgid "Selecting or creating a team reveals that team's detail form. Scroll down to the :guilabel:`Self-Service` section of features, and enable :guilabel:`Community Forum`, by checking the box beside it."
msgstr ""
#: ../../content/applications/services/helpdesk/overview/help_center.rst:192
msgid "When activated, a new field labeled :guilabel:`Forums` appears beneath."
msgstr ""
#: ../../content/applications/services/helpdesk/overview/help_center.rst:194
msgid "Click the empty :guilabel:`Forums` field to reveal a drop-down menu. By default, there is only one option to begin with, labeled :guilabel:`Help`. That is the option Odoo automatically created when the :guilabel:`Community Forums` feature was enabled. Select :guilabel:`Help` from the drop-down menu to enable that forum."
msgstr ""
#: ../../content/applications/services/helpdesk/overview/help_center.rst:199
msgid "To create a new forum, type a name into the blank :guilabel:`Forums` field, then click the :guilabel:`Create and Edit` option. Multiple forums can be selected in this field."
msgstr ""
#: ../../content/applications/services/helpdesk/overview/help_center.rst:203
msgid "Set up a forum"
msgstr ""
#: ../../content/applications/services/helpdesk/overview/help_center.rst:205
msgid "The settings on a forum are managed through either the *Website* or *eLearning* applications. From the Odoo Dashboard, navigate to :menuselection:`Website --> Configuration --> Forums` or :menuselection:`eLearning --> Forum --> Forums`. In either case, select a forum to edit from the list."
msgstr ""
#: ../../content/applications/services/helpdesk/overview/help_center.rst:210
msgid "On the forum detail form, select a mode."
msgstr ""
#: ../../content/applications/services/helpdesk/overview/help_center.rst:212
msgid "The :guilabel:`Questions` mode allows for one answer/response for each post, while :guilabel:`Discussion` mode allows for multiple responses. To limit the forum to a single website, select it from the :guilabel:`Website` field."
msgstr ""
#: ../../content/applications/services/helpdesk/overview/help_center.rst:216
msgid "Under the :guilabel:`Order and Visibility` section, in the :guilabel:`Options` tab, choose how the posts should be sorted, by modifying the :guilabel:`Default Sort` field. Change the :guilabel:`Privacy` setting to change which users will have access to the forum."
msgstr ""
#: ../../content/applications/services/helpdesk/overview/help_center.rst:220
msgid "Below these settings, there is space to add a description for the forum. This description will be visible on the website where the forum is published."
msgstr ""
#: ../../content/applications/services/helpdesk/overview/help_center.rst:-1
msgid "Overview of a forum's settings page in Odoo Helpdesk."
msgstr ""
#: ../../content/applications/services/helpdesk/overview/help_center.rst:228
msgid "Karma gains and karma related rights"
msgstr ""
#: ../../content/applications/services/helpdesk/overview/help_center.rst:230
msgid "When users interact on forums - either through posting questions, submitting answers, or upvoting responses - they earn points, called *karma*."
msgstr ""
#: ../../content/applications/services/helpdesk/overview/help_center.rst:233
msgid "Karma points are used to build the credibility of a user within the community. The more positive interactions a user has on the forum, the more karma points they gain. Certain activities, such as posting without validation, or editing posts, require users to have earned a specific level of karma points to prove their legitimacy and trustworthiness."
msgstr ""
#: ../../content/applications/services/helpdesk/overview/help_center.rst:238
msgid "These figures can be adjusted on the :guilabel:`Karma gains` and :guilabel:`Karma related rights` tabs, located on the forums detail form."
msgstr ""
#: ../../content/applications/services/helpdesk/overview/help_center.rst:243
msgid "Karma gains"
msgstr ""
#: ../../content/applications/services/helpdesk/overview/help_center.rst:245
msgid "In the :guilabel:`Karma gains` tab, there are listed actions that will cause users to gain (or lose) karma points. Those actions are:"
msgstr ""
#: ../../content/applications/services/helpdesk/overview/help_center.rst:248
msgid "Asking a question"
msgstr ""
#: ../../content/applications/services/helpdesk/overview/help_center.rst:249
msgid "Question upvoted"
msgstr ""
#: ../../content/applications/services/helpdesk/overview/help_center.rst:250
msgid "Question downvoted"
msgstr ""
#: ../../content/applications/services/helpdesk/overview/help_center.rst:251
msgid "Answer upvoted"
msgstr ""
#: ../../content/applications/services/helpdesk/overview/help_center.rst:252
msgid "Answer downvoted"
msgstr ""
#: ../../content/applications/services/helpdesk/overview/help_center.rst:253
msgid "Accepting an answer"
msgstr ""
#: ../../content/applications/services/helpdesk/overview/help_center.rst:254
msgid "Answer accepted"
msgstr ""
#: ../../content/applications/services/helpdesk/overview/help_center.rst:255
msgid "Answer flagged"
msgstr ""
#: ../../content/applications/services/helpdesk/overview/help_center.rst:257
msgid "Karma related rights"
msgstr ""
#: ../../content/applications/services/helpdesk/overview/help_center.rst:259
msgid "In the :guilabel:`Karma related rights` tab, there are listed activities that users cannot complete, without having a specific level of karma points. Those activities are:"
msgstr ""
#: ../../content/applications/services/helpdesk/overview/help_center.rst:262
msgid "Ask questions"
msgstr ""
#: ../../content/applications/services/helpdesk/overview/help_center.rst:263
msgid "Answer questions"
msgstr ""
#: ../../content/applications/services/helpdesk/overview/help_center.rst:264
msgid "Upvote"
msgstr ""
#: ../../content/applications/services/helpdesk/overview/help_center.rst:265
msgid "Downvote"
msgstr ""
#: ../../content/applications/services/helpdesk/overview/help_center.rst:266
msgid "Edit own posts"
msgstr ""
#: ../../content/applications/services/helpdesk/overview/help_center.rst:267
msgid "Edit all posts"
msgstr ""
#: ../../content/applications/services/helpdesk/overview/help_center.rst:268
msgid "Close own posts"
msgstr ""
#: ../../content/applications/services/helpdesk/overview/help_center.rst:269
msgid "Close all posts"
msgstr ""
#: ../../content/applications/services/helpdesk/overview/help_center.rst:270
msgid "Delete own posts"
msgstr ""
#: ../../content/applications/services/helpdesk/overview/help_center.rst:271
msgid "Delete all posts"
msgstr ""
#: ../../content/applications/services/helpdesk/overview/help_center.rst:272
msgid "Nofollow links"
msgstr ""
#: ../../content/applications/services/helpdesk/overview/help_center.rst:273
msgid "Accept an answer on own question"
msgstr ""
#: ../../content/applications/services/helpdesk/overview/help_center.rst:274
msgid "Accept an answer to all questions"
msgstr ""
#: ../../content/applications/services/helpdesk/overview/help_center.rst:275
msgid "Editor features: image and links"
msgstr ""
#: ../../content/applications/services/helpdesk/overview/help_center.rst:276
msgid "Comment on own posts"
msgstr ""
#: ../../content/applications/services/helpdesk/overview/help_center.rst:277
msgid "Comment on all posts"
msgstr ""
#: ../../content/applications/services/helpdesk/overview/help_center.rst:278
msgid "Convert own answers to comments (and vice versa)"
msgstr ""
#: ../../content/applications/services/helpdesk/overview/help_center.rst:279
msgid "Convert all answers to comments (and vice versa)"
msgstr ""
#: ../../content/applications/services/helpdesk/overview/help_center.rst:280
msgid "Unlink own comments"
msgstr ""
#: ../../content/applications/services/helpdesk/overview/help_center.rst:281
msgid "Unlink all comments"
msgstr ""
#: ../../content/applications/services/helpdesk/overview/help_center.rst:282
msgid "Ask questions without validation"
msgstr ""
#: ../../content/applications/services/helpdesk/overview/help_center.rst:283
msgid "Flag a post as offensive"
msgstr ""
#: ../../content/applications/services/helpdesk/overview/help_center.rst:284
msgid "Moderate posts"
msgstr ""
#: ../../content/applications/services/helpdesk/overview/help_center.rst:285
msgid "Change question tags"
msgstr ""
#: ../../content/applications/services/helpdesk/overview/help_center.rst:286
msgid "Create new tags"
msgstr ""
#: ../../content/applications/services/helpdesk/overview/help_center.rst:289
msgid "Create a forum post from a Helpdesk ticket"
msgstr ""
#: ../../content/applications/services/helpdesk/overview/help_center.rst:291
msgid "When a *Helpdesk* team has a *Forum* enabled, tickets submitted to that team can be converted to forum posts."
msgstr ""
#: ../../content/applications/services/helpdesk/overview/help_center.rst:294
msgid "To do that, select a ticket, either from a team's pipeline or from :menuselection:`Tickets --> All Tickets` in the :guilabel:`Helpdesk` application."
msgstr ""
#: ../../content/applications/services/helpdesk/overview/help_center.rst:297
msgid "At the top of the ticket detail form, click the :guilabel:`Share on Forum` button."
msgstr ""
#: ../../content/applications/services/helpdesk/overview/help_center.rst:-1
msgid "Overview of the Forums page of a website to show the available ones in Odoo Helpdesk."
msgstr ""
#: ../../content/applications/services/helpdesk/overview/help_center.rst:303
msgid "When clicked, a pop-up appears. Here, the post and title can be edited to correct any typos, or modified to remove any proprietary or client information. :guilabel:`Tags` can also be added to help organize the post in the forum, making it easier for users to locate during a search. When all adjustments have been made, click :guilabel:`Create and View Post`."
msgstr ""
#: ../../content/applications/services/helpdesk/overview/help_center.rst:309
msgid "eLearning"
msgstr ""
#: ../../content/applications/services/helpdesk/overview/help_center.rst:311
msgid "Odoo *eLearning* courses offer customers additional training and content in the form of videos, presentations, and certifications/quizzes. Providing additional training enables customers to work through issues and find solutions on their own. They can also develop a deeper understanding of the services and products they are using."
msgstr ""
#: ../../content/applications/services/helpdesk/overview/help_center.rst:317
msgid "Enable eLearning courses on a Helpdesk team"
msgstr ""
#: ../../content/applications/services/helpdesk/overview/help_center.rst:319
msgid "To enable *eLearning* courses on a *Helpdesk* team, go to :menuselection:`Helpdesk --> Configuration --> Teams` and select a team, or create a :doc:`new one </applications/services/helpdesk/overview/getting_started>`."
msgstr ""
#: ../../content/applications/services/helpdesk/overview/help_center.rst:323
msgid "On the team's settings page, scroll to the :guilabel:`Self-Service` section, and check the box next to :guilabel:`eLearning`. A new field will appear below, labeled :guilabel:`Courses`."
msgstr ""
#: ../../content/applications/services/helpdesk/overview/help_center.rst:326
msgid "Click the empty field next to :guilabel:`Courses` beneath the :guilabel:`eLearning` feature to reveal a drop-down menu. Select an available course from the drop-down menu, or type a title into the field, and click :guilabel:`Create and edit` to create a new course from this page. Multiple courses can be assigned to a single team."
msgstr ""
#: ../../content/applications/services/helpdesk/overview/help_center.rst:332
msgid "Create an eLearning course"
msgstr ""
#: ../../content/applications/services/helpdesk/overview/help_center.rst:334
msgid "A new *eLearning* course can be created from the :guilabel:`Helpdesk` team's settings page, as in the step above, or from the *eLearning* app."
msgstr ""
#: ../../content/applications/services/helpdesk/overview/help_center.rst:337
msgid "To create a course directly through the *eLearning* application, navigate to :menuselection:`eLearning --> New`. This reveals a blank course template that can be customized and modified as needed."
msgstr ""
#: ../../content/applications/services/helpdesk/overview/help_center.rst:341
msgid "On the course template page, add a :guilabel:`Course Title`, and below that, :guilabel:`Tags`."
msgstr ""
#: ../../content/applications/services/helpdesk/overview/help_center.rst:343
msgid "Click on the :guilabel:`Options` tab. Under :guilabel:`Access Rights`, choose the :guilabel:`Enroll Policy`. This determines which users will be allowed to take the course. Under :guilabel:`Display`, choose the course :guilabel:`Type` and :guilabel:`Visibility`. The :guilabel:`Visibility` setting determines whether the course will be available to public site visitors or members."
msgstr ""
#: ../../content/applications/services/helpdesk/overview/help_center.rst:349
msgid "Add content to an eLearning course"
msgstr ""
#: ../../content/applications/services/helpdesk/overview/help_center.rst:351
msgid "To add content to a course, click the :guilabel:`Content` tab and select :guilabel:`Add Content`. Choose the :guilabel:`Content Type` from the drop-down menu and upload the file, or paste the link, where instructed. Click :guilabel:`Save` when finished. Click :guilabel:`Add Section` to organize the course in sections."
msgstr ""
#: ../../content/applications/services/helpdesk/overview/help_center.rst:-1
msgid "View of a course being published for Odoo Helpdesk."
msgstr ""
#: ../../content/applications/services/helpdesk/overview/help_center.rst:361
msgid "In order to add a certification to a course, go to :menuselection:`eLearning --> Configuration --> Settings`, check the box labeled :guilabel:`Certifications`, and :guilabel:`Save` to activate the setting."
msgstr ""
#: ../../content/applications/services/helpdesk/overview/help_center.rst:366
msgid "`Odoo Tutorials: eLearning <https://www.odoo.com/slides/elearning-56>`_"
msgstr ""
#: ../../content/applications/services/helpdesk/overview/help_center.rst:369
msgid "Publish an eLearning course"
msgstr ""
#: ../../content/applications/services/helpdesk/overview/help_center.rst:371
msgid "To allow customers to enroll in a course, both the course and the contents need to be published."
msgstr ""
#: ../../content/applications/services/helpdesk/overview/help_center.rst:373
msgid "If the course is published, but the contents of the course are not published, customers can enroll in the course on the website, but they won't be able to view any of the course content. Knowing this, it may be beneficial to publish the course first if the course contents are intended to be released over time, such as classes with a weekly schedule."
msgstr ""
#: ../../content/applications/services/helpdesk/overview/help_center.rst:378
msgid "To make the entire course available at once, each piece of course content must be published first, then the course can be published."
msgstr ""
#: ../../content/applications/services/helpdesk/overview/help_center.rst:381
msgid "To publish a course, choose a course from the *eLearning* dashboard. On the course template page, click the :guilabel:`Go to Website` smart button."
msgstr ""
#: ../../content/applications/services/helpdesk/overview/help_center.rst:384
msgid "This will reveal the front end of the course's web page. At the top of the course web page, move the :guilabel:`Unpublished` toggle switch to :guilabel:`Published`."
msgstr ""
#: ../../content/applications/services/helpdesk/overview/help_center.rst:388
msgid "Publish eLearning course contents from the back-end"
msgstr ""
#: ../../content/applications/services/helpdesk/overview/help_center.rst:390
msgid "To publish *eLearning* course content from the back-end, choose a course from the *eLearning* dashboard. On the course template page, click the :guilabel:`Published Contents` smart button."
msgstr ""
#: ../../content/applications/services/helpdesk/overview/help_center.rst:393
msgid "Doing so reveals a separate page displaying all the published content related to that course. Remove the default :guilabel:`Published` filter from the search bar in the upper-right corner, to reveal all the content related to the course - even the non-published content."
msgstr ""
#: ../../content/applications/services/helpdesk/overview/help_center.rst:397
msgid "Click the :guilabel:`≣ (List View)` icon in the upper-right corner, directly beneath the search bar to switch to list view."
msgstr ""
#: ../../content/applications/services/helpdesk/overview/help_center.rst:400
msgid "While in :guilabel:`List View`, there is a checkbox on the far left of the screen, above the listed courses, to the left of the :guilabel:`Title` column. When that checkbox is clicked, all the course contents are selected at once."
msgstr ""
#: ../../content/applications/services/helpdesk/overview/help_center.rst:404
msgid "With all the course content selected, double click any of the boxes in the :guilabel:`Is Published` column. This reveals a pop-up window, asking for confirmation that all selected records are intended to be published. Click :guilabel:`OK` to automatically publish all course content."
msgstr ""
#: ../../content/applications/services/helpdesk/overview/help_center.rst:-1
msgid "View of a course contents being published in Odoo Helpdesk back-end."
msgstr ""
#: ../../content/applications/services/helpdesk/overview/ratings.rst:3
msgid "Customer ratings"
msgstr ""

700
locale/sources/websites.pot
View File

@ -8,7 +8,7 @@ msgid ""
msgstr ""
"Project-Id-Version: Odoo 16.0\n"
"Report-Msgid-Bugs-To: \n"
"POT-Creation-Date: 2023-06-15 11:45+0000\n"
"POT-Creation-Date: 2023-07-03 09:37+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"
@ -349,6 +349,7 @@ msgstr ""
#: ../../content/applications/websites/ecommerce/managing_products/price_management.rst:95
#: ../../content/applications/websites/website/configuration.rst:5
#: ../../content/applications/websites/website/configuration/cookies_bar.rst:24
#: ../../content/applications/websites/website/configuration/recaptcha.rst:16
#: ../../content/applications/websites/website/reporting/link_tracker.rst:10
msgid "Configuration"
msgstr ""
@ -1772,107 +1773,335 @@ msgid "Live Chat"
msgstr ""
#: ../../content/applications/websites/livechat.rst:8
msgid "Live Chat has the highest satisfaction rating of any communication tool. It allows fast responses and it is accessible and convenient, as your customers can keep doing what they are doing while interacting with you. Remember: your customers want to talk to you, so let's make it easy."
msgstr ""
#: ../../content/applications/websites/livechat.rst:13
msgid "`Live Chat: product page <https://www.odoo.com/app/live-chat>`_"
msgid "Odoo *Live Chat* allows users to communicate with website visitors in real time. With *Live Chat*, leads can be qualified for their sales potential, support questions can be answered quickly, and issues can be directed to the appropriate team for further investigation (or follow up). *Live Chat* also provides the opportunity for instant feedback from customers."
msgstr ""
#: ../../content/applications/websites/livechat.rst:14
msgid ":doc:`livechat/ratings`"
msgid "Enable Live Chat"
msgstr ""
#: ../../content/applications/websites/livechat.rst:15
msgid ":doc:`livechat/responses`"
#: ../../content/applications/websites/livechat.rst:16
msgid "In order to enable *Live Chat*, the *Live Chat* application needs to be installed. This can be done in one of two ways."
msgstr ""
#: ../../content/applications/websites/livechat.rst:18
msgid "Set up"
#: ../../content/applications/websites/livechat.rst:19
msgid "Go to :menuselection:`Apps --> Live Chat` and click :guilabel:`Install`."
msgstr ""
#: ../../content/applications/websites/livechat.rst:20
msgid "Once *Live Chat* is installed on your database, if your website was created with Odoo, the application is automatically added to it. All that is left to do is to go to :menuselection:`Website --> Configuration --> Settings --> Live Chat`."
msgid "In the :menuselection:`Website` application, go to :menuselection:`Configuration --> Settings`, scroll to the :guilabel:`Email & Marketing` section, check the box next to :guilabel:`Livechat`, and click :guilabel:`Save`."
msgstr ""
#: ../../content/applications/websites/livechat.rst:-1
msgid "View of the settings page and the live chat feature for Odoo Live Chat"
msgid "View of the settings page and the live chat feature for Odoo Live Chat."
msgstr ""
#: ../../content/applications/websites/livechat.rst:28
msgid "Select the channel to be linked to your website or create one on the fly."
msgid "After the :guilabel:`Live Chat` application is installed, a live chat :guilabel:`Channel` will be created by default and automatically selected in the drop-down."
msgstr ""
#: ../../content/applications/websites/livechat.rst:32
msgid "Create a new live chat channel"
msgstr ""
#: ../../content/applications/websites/livechat.rst:34
msgid "To create a new live chat *Channel*, go to :menuselection:`Main Odoo Dashboard --> Live Chat app --> New`. This will open a blank channel detail form. Enter the name of the new channel in the :guilabel:`Channel Name` field."
msgstr ""
#: ../../content/applications/websites/livechat.rst:-1
msgid "View of a live chat channel form for Odoo Live Chat"
msgstr ""
#: ../../content/applications/websites/livechat.rst:33
msgid "For both scenarios, under:"
msgstr ""
#: ../../content/applications/websites/livechat.rst:36
msgid "- **Operators**: add agents to respond to the chat requests. Add as many as you like, and keep in mind that operators that do not show any activity in Odoo for more than 30min are considered disconnected."
msgstr ""
#: ../../content/applications/websites/livechat.rst:39
msgid "- **Options**: set the default text to be shown on the live chat button; an automated welcome message to be seen by visitors when a conversation is initiated, and the text that prompts the user to initiate a chat."
msgid "View of a live chat channel form for Odoo Live Chat."
msgstr ""
#: ../../content/applications/websites/livechat.rst:42
msgid "- **Channel Rules**: choose an action for a given URL, and/or per country. In the example below, the chat window automatically pops-up 3 seconds after users (from any country) land on the contact us page."
msgid "To configure the remaining tabs on the channel detail form (:guilabel:`Operators`, :guilabel:`Options`, :guilabel:`Channel Rules`, and :guilabel:`Widgets`), follow the steps below."
msgstr ""
#: ../../content/applications/websites/livechat.rst:-1
msgid "View of a channel’s rules form for Odoo Live Chat"
#: ../../content/applications/websites/livechat.rst:46
msgid "Operators"
msgstr ""
#: ../../content/applications/websites/livechat.rst:48
msgid "GeoIP, which refers to the process of finding a computer terminal’s geographical location by its IP address, must be installed on your server. Otherwise, under *Channel Rules*, countries are not taken into account."
msgid "*Operators* are the users who will respond to live chat requests from customers. When a user is added as an operator in a live chat channel, they will be able to receive chats from website visitors wherever they are in the database. Chat windows will open in the bottom right corner of the screen."
msgstr ""
#: ../../content/applications/websites/livechat.rst:53
msgid "External options"
msgstr ""
#: ../../content/applications/websites/livechat.rst:56
msgid "If your website was not created with Odoo, you can find the code to be added to your own, under the *Widget* tab."
#: ../../content/applications/websites/livechat.rst:-1
msgid "View of a live chat pop up window in an Odoo database."
msgstr ""
#: ../../content/applications/websites/livechat.rst:57
msgid "Odoo also offers an URL you can send to users so they can have access to a single live chat page."
msgid "The user who originally created the live chat channel will be added as an operator by default."
msgstr ""
#: ../../content/applications/websites/livechat.rst:-1
msgid "View of the widget tab for Odoo Live Chat"
#: ../../content/applications/websites/livechat.rst:59
msgid "To add additional users, navigate back to the :guilabel:`Website Live Chat Channels` dashboard via the breadcrumbs and click on the appropriate :guilabel:`Live Chat Channel`. Then, on the channel detail form, under the :guilabel:`Operators` tab, click :guilabel:`ADD` to reveal an :guilabel:`Add: Operators` pop-up window."
msgstr ""
#: ../../content/applications/websites/livechat.rst:63
msgid "Managing chat requests"
#: ../../content/applications/websites/livechat.rst:64
msgid "In the pop-up window, search for the desired user(s). Then, click the checkbox next to the user(s) to be added, and click :guilabel:`SELECT`."
msgstr ""
#: ../../content/applications/websites/livechat.rst:65
msgid "Conversations initiated by visitors pop up as a direct message, and are shown in *Discuss*. Therefore, inquiries can be answered wherever you are in Odoo."
msgstr ""
#: ../../content/applications/websites/livechat.rst:-1
msgid "View of the discuss application with a message sent through live chat in Odoo"
#: ../../content/applications/websites/livechat.rst:67
msgid "New operators can be created and added to the list directly from this pop-up, as well, by clicking :guilabel:`New`, and filling out the :guilabel:`Create Operators` pop-up form. When the form is complete, click :guilabel:`SAVE & CLOSE` (or :guilabel:`SAVE & NEW` for multiple record creations)."
msgstr ""
#: ../../content/applications/websites/livechat.rst:72
msgid "Conversations are dispatched based on the current workload of the online operators."
msgid "Current operators can be edited (or removed) by clicking on their respective boxes in the :guilabel:`Operators` tab, which reveals a separate :guilabel:`Open: Operators` pop-up. In that pop-up, adjust any information as needed, and click :guilabel:`Save`, or click :guilabel:`Remove` to remove that operator from the channel."
msgstr ""
#: ../../content/applications/websites/livechat.rst:75
msgid "Leave or join a channel"
#: ../../content/applications/websites/livechat.rst:78
msgid "Options"
msgstr ""
#: ../../content/applications/websites/livechat.rst:77
msgid "Go to :menuselection:`Website --> Configuration --> Settings`, access your channel under *Live Chat*, and *Join Channel* or *Leave Channel*."
#: ../../content/applications/websites/livechat.rst:80
msgid "The :guilabel:`Options` tab on the live chat channel details form contains the visual and text settings for the live chat window."
msgstr ""
#: ../../content/applications/websites/livechat.rst:84
msgid "Livechat button"
msgstr ""
#: ../../content/applications/websites/livechat.rst:86
msgid "The *Livechat Button* is the icon that appears in the bottom corner of the website."
msgstr ""
#: ../../content/applications/websites/livechat.rst:-1
msgid "View of a channel form and the option to join a channel for Odoo Live Chat"
msgid "View of an Odoo website emphasizing the livechat button."
msgstr ""
#: ../../content/applications/websites/livechat.rst:92
msgid "Change the text in the :guilabel:`Text of the Button` field to update the greeting displayed in the text bubble when the live chat button appears on the website."
msgstr ""
#: ../../content/applications/websites/livechat.rst:95
msgid "Change the :guilabel:`Livechat Button Color` by clicking a color bubble to open the color selection window. Click the :guilabel:`🔄 (refresh)` icon to the right of the color bubbles to reset the colors to the default selection."
msgstr ""
#: ../../content/applications/websites/livechat.rst:100
msgid "Color selection, for the button or header, can be made manually using a slider or through RGB, HSL, or HEX color code entries from the pop-up color selection window that appears when either of the color bubbles are clicked. Different options will be available, depending on your operating system."
msgstr ""
#: ../../content/applications/websites/livechat.rst:106
msgid "Livechat window"
msgstr ""
#: ../../content/applications/websites/livechat.rst:108
msgid "The *Livechat Window* is the space where the live chat conversation with website visitors takes place."
msgstr ""
#: ../../content/applications/websites/livechat.rst:111
msgid "Edit the :guilabel:`Welcome Message` to change the message a visitor sees when they open a new chat session. This message will appear as though it is sent by a live chat operator, and acts as both a greeting and an invitation to continue the conversation."
msgstr ""
#: ../../content/applications/websites/livechat.rst:115
msgid "Edit the :guilabel:`Chat Input Placeholder` to alter the text that appears in the box where visitors will type their replies."
msgstr ""
#: ../../content/applications/websites/livechat.rst:118
msgid "The *Channel Header* is the colored bar at the top of the chat window. The :guilabel:`Channel Header Color` can be changed following the same steps as the *Livechat Button Color* above."
msgstr ""
#: ../../content/applications/websites/livechat.rst:124
msgid "The Livechat Window with a purple header. The chat input placeholder reads \"Ask Something...\""
msgstr ""
#: ../../content/applications/websites/livechat.rst:127
msgid "Channel rules"
msgstr ""
#: ../../content/applications/websites/livechat.rst:129
msgid "The :guilabel:`Channel Rules` tab on the live chat channel details form determines when the *Live Chat Window* opens on the website, by configuring when a :guilabel:`URL Regex` action is triggered (e.g., a page visit)."
msgstr ""
#: ../../content/applications/websites/livechat.rst:133
msgid "To create a new channel rule, click :guilabel:`Add a line`. This opens the :guilabel:`Open: Rules` pop-up."
msgstr ""
#: ../../content/applications/websites/livechat.rst:-1
msgid "View of a channel's rules form for Odoo Live Chat."
msgstr ""
#: ../../content/applications/websites/livechat.rst:141
msgid "Create new rules"
msgstr ""
#: ../../content/applications/websites/livechat.rst:143
msgid "Fill out the fields on the :guilabel:`Open: Rules` pop-up as instructed below, then click :guilabel:`Save`."
msgstr ""
#: ../../content/applications/websites/livechat.rst:148
msgid "Live Chat Button"
msgstr ""
#: ../../content/applications/websites/livechat.rst:150
msgid "The *Livechat Button* is the icon that appears in the bottom corner of the website. Select from one of the following display options:"
msgstr ""
#: ../../content/applications/websites/livechat.rst:153
msgid ":guilabel:`Show` displays the chat button on the page(s)."
msgstr ""
#: ../../content/applications/websites/livechat.rst:154
msgid ":guilabel:`Show with notification` displays the chat button, as well as a floating text bubble next to the button."
msgstr ""
#: ../../content/applications/websites/livechat.rst:156
msgid ":guilabel:`Open automatically` displays the button and automatically opens the chat window after a specified amount of time (designated in the :guilabel:`Open automatically timer` field)."
msgstr ""
#: ../../content/applications/websites/livechat.rst:159
msgid ":guilabel:`Hide` hides the chat button on the page(s)."
msgstr ""
#: ../../content/applications/websites/livechat.rst:161
msgid "Chatbot"
msgstr ""
#: ../../content/applications/websites/livechat.rst:163
msgid "If a *Chatbot* will be included on this channel, select it from the dropdown. If the chatbot will only be active when no operators are active, check the box labeled :guilabel:`Enabled only if no operator`."
msgstr ""
#: ../../content/applications/websites/livechat.rst:167
msgid "URL Regex"
msgstr ""
#: ../../content/applications/websites/livechat.rst:169
msgid "In the :guilabel:`URL Regex` field, input the relative URL of the page where the chat button should appear."
msgstr ""
#: ../../content/applications/websites/livechat.rst:172
msgid "Open automatically timer"
msgstr ""
#: ../../content/applications/websites/livechat.rst:174
msgid "This field designates the amount of time (in seconds) a page will be open before the chat window will open. If the :guilabel:`Livechat Button` for this rule is not set to :guilabel:`Open automatically`, this field will be ignored."
msgstr ""
#: ../../content/applications/websites/livechat.rst:178
msgid "Country"
msgstr ""
#: ../../content/applications/websites/livechat.rst:180
msgid "If this channel should only be available to site visitors in specific countries, add them to the :guilabel:`Country` field. If this field is left blank, the channel will be available to all site visitors, regardless of location."
msgstr ""
#: ../../content/applications/websites/livechat.rst:185
msgid "In order to track the geographical location of visitors, :guilabel:`GeoIP` must be installed on the database. While this feature is installed by default on *Odoo Online*, *On-Premise* databases will require additional :doc:`setup steps </applications/websites/website/configuration/on-premise_geo-ip-installation>`."
msgstr ""
#: ../../content/applications/websites/livechat.rst:191
msgid "Widget"
msgstr ""
#: ../../content/applications/websites/livechat.rst:193
msgid "The :guilabel:`Widget` tab on the live chat channel details form provides the shortcode for an embeddable website widget. This code can be added to a website to provide access to a live chat window."
msgstr ""
#: ../../content/applications/websites/livechat.rst:197
msgid "The live chat widget can be added to websites created through Odoo by navigating to the :menuselection:`Website --> Configuration --> Settings`. Then scroll to the :guilabel:`Livechat` section, and select the channel to add to the site. Click :guilabel:`Save` to apply."
msgstr ""
#: ../../content/applications/websites/livechat.rst:201
msgid "To add the widget to a website created on a third-party platform, click the first :guilabel:`COPY` button on the :guilabel:`Widget` tab and paste the code into the `<head>` tag on the site."
msgstr ""
#: ../../content/applications/websites/livechat.rst:204
msgid "Likewise, to send a live chat session to a customer, click the second :guilabel:`COPY` button on the :guilabel:`Widget` tab. This link can be sent directly to a customer, and once they click the link, it will open a new chat."
msgstr ""
#: ../../content/applications/websites/livechat.rst:-1
msgid "View of the widget tab for Odoo Live Chat."
msgstr ""
#: ../../content/applications/websites/livechat.rst:213
msgid "Participate in a conversation"
msgstr ""
#: ../../content/applications/websites/livechat.rst:215
msgid "As explained above, *operators* are the users who will respond to live chat requests from customers. The information below outlines the necessary steps for operators participating in live chat conversations on an Odoo database."
msgstr ""
#: ../../content/applications/websites/livechat.rst:220
msgid "Set an online chat name"
msgstr ""
#: ../../content/applications/websites/livechat.rst:222
msgid "Before participating in a live chat, operators should update their *Online Chat Name*. This is the name that will be displayed to site visitors in the live chat conversation."
msgstr ""
#: ../../content/applications/websites/livechat.rst:225
msgid "To update the :guilabel:`Online Chat Name`, click on the user name in the upper-right corner of any page in the database. Select :guilabel:`My Profile` to open the Profile page. On the right side of the :guilabel:`Preferences` tab, locate the :guilabel:`Online Chat Name` field and enter the preferred name."
msgstr ""
#: ../../content/applications/websites/livechat.rst:-1
msgid "View of the My Profile option in Odoo."
msgstr ""
#: ../../content/applications/websites/livechat.rst:234
msgid "If a users :guilabel:`Online Chat Name` is not set, the name displayed will default to the :guilabel:`User Name`."
msgstr ""
#: ../../content/applications/websites/livechat.rst:238
msgid "A user has their full name as their :guilabel:`User Name`, but they do not want to include their last name in a live chat conversation. They would then set their :guilabel:`Online Chat Name` to include only their first name."
msgstr ""
#: ../../content/applications/websites/livechat.rst:0
msgid "View of user profile in Odoo, emphasizing the Online Chat name field."
msgstr ""
#: ../../content/applications/websites/livechat.rst:247
msgid "Join or leave a channel"
msgstr ""
#: ../../content/applications/websites/livechat.rst:249
msgid "To join a live chat channel, go to the :menuselection:`Live Chat` app and click the :guilabel:`JOIN` button on the kanban card for the appropriate channel."
msgstr ""
#: ../../content/applications/websites/livechat.rst:252
msgid "Any channel where the user is currently active will show a :guilabel:`LEAVE` button. Click this button to disconnect from the channel."
msgstr ""
#: ../../content/applications/websites/livechat.rst:-1
msgid "View of a channel form and the option to join a channel for Odoo Live Chat."
msgstr ""
#: ../../content/applications/websites/livechat.rst:260
msgid "*Operators* that do not show any activity in Odoo for more than thirty minutes will be considered disconnected, and subsequently removed from the channel."
msgstr ""
#: ../../content/applications/websites/livechat.rst:264
msgid "Manage live chat requests"
msgstr ""
#: ../../content/applications/websites/livechat.rst:266
msgid "When an operator is active in a channel, chat windows will open in the bottom right corner of the screen, no matter where they are in the database. They can participate in conversations without leaving their current location."
msgstr ""
#: ../../content/applications/websites/livechat.rst:271
msgid "Conversations can also be accessed by clicking the :guilabel:`Conversations` icon in the menu bar."
msgstr ""
#: ../../content/applications/websites/livechat.rst:0
msgid "View of the menu bar in Odoo emphasizing the conversations icon."
msgstr ""
#: ../../content/applications/websites/livechat.rst:278
msgid "Live chat conversations can also be viewed by navigating to :menuselection:`Dashboard --> Discuss`. New conversations will appear in bold under the :guilabel:`LIVECHAT` heading along the left panel."
msgstr ""
#: ../../content/applications/websites/livechat.rst:-1
msgid "View of the discuss application with a message sent through live chat in Odoo."
msgstr ""
#: ../../content/applications/websites/livechat.rst:285
msgid "Click on a conversation in the left panel to select it. This will open the conversation. From this view, an operator can participate in the chat the same as they would in the normal chat window."
msgstr ""
#: ../../content/applications/websites/livechat.rst:289
msgid ":doc:`Get Started with Discuss </applications/productivity/discuss/overview/get_started>`"
msgstr ""
#: ../../content/applications/websites/livechat.rst:290
msgid ":doc:`/applications/websites/livechat/responses`"
msgstr ""
#: ../../content/applications/websites/livechat/ratings.rst:3
@ -1936,83 +2165,239 @@ msgid ":doc:`responses`"
msgstr ""
#: ../../content/applications/websites/livechat/responses.rst:3
msgid "Commands and Canned Responses"
msgid "Commands and canned responses"
msgstr ""
#: ../../content/applications/websites/livechat/responses.rst:5
msgid "Using canned responses can help you save time and have a previous, well-thought response, to some of your most common questions and comments."
msgstr ""
#: ../../content/applications/websites/livechat/responses.rst:9
msgid "Use commands"
msgid "In the Odoo *Live Chat* application, *commands* allow the user to perform specific actions both inside the chat window, and through other Odoo applications. The *Live Chat* app also includes *canned responses*. These are customized, pre-configured substitutions that allow users to replace shortcut entries in place of longer, well-thought out responses to some of the most common questions and comments."
msgstr ""
#: ../../content/applications/websites/livechat/responses.rst:11
msgid "Commands are shortcuts that do specific actions within the chat window:"
msgstr ""
#: ../../content/applications/websites/livechat/responses.rst:13
msgid "**/help**: shows a help message."
msgstr ""
#: ../../content/applications/websites/livechat/responses.rst:14
msgid "**/helpdesk**: creates a helpdesk ticket."
msgid "Both commands and canned responses save time, and allow users to maintain a level of consistency throughout their conversations."
msgstr ""
#: ../../content/applications/websites/livechat/responses.rst:15
msgid "**/helpdesk_search**: searches for a helpdesk ticket."
msgstr ""
#: ../../content/applications/websites/livechat/responses.rst:16
msgid "**/history**: shows the last 15 visited pages."
msgid "Execute a command"
msgstr ""
#: ../../content/applications/websites/livechat/responses.rst:17
msgid "**/lead**: creates a new lead."
msgid "Live chat *commands* are keywords that trigger pre-configured actions. When a live chat *operator* is participating in a conversation with a customer or website visitor, they can execute a command by typing `/`, followed by the command."
msgstr ""
#: ../../content/applications/websites/livechat/responses.rst:18
msgid "**/leave**: leaves the channel."
msgstr ""
#: ../../content/applications/websites/livechat/responses.rst:0
msgid "- For *helpdesk tickets*: make sure the application is installed on your database and the option *Live Chat* under :menuselection:`Helpdesk --> Configuration --> Helpdesk Teams` is enabled."
msgstr ""
#: ../../content/applications/websites/livechat/responses.rst:0
msgid "- For *leads*: the *CRM* application must be installed on your database."
msgstr ""
#: ../../content/applications/websites/livechat/responses.rst:26
msgid "To access the ticket or lead created from the chat, click on the shortcut link."
#: ../../content/applications/websites/livechat/responses.rst:21
msgid "Commands, and the resulting actions, are only visible in the conversation window for the live chat operator. A customer will not see any commands that an operator uses in a conversation from their view of the chat."
msgstr ""
#: ../../content/applications/websites/livechat/responses.rst:-1
msgid "View of the chat window with a helpdesk ticket created in Odoo Live Chat"
msgid "View of the chat window with a helpdesk ticket created in Odoo Live Chat."
msgstr ""
#: ../../content/applications/websites/livechat/responses.rst:33
msgid "Helpdesk tickets created from the chat automatically add the conversation as a description of the ticket. The same goes for the creation of a lead."
#: ../../content/applications/websites/livechat/responses.rst:29
msgid "More information about each available command can be found below."
msgstr ""
#: ../../content/applications/websites/livechat/responses.rst:32
msgid "Help"
msgstr ""
#: ../../content/applications/websites/livechat/responses.rst:34
msgid "If an operator types `/help` in the chat window, an informative message that includes the potential entry types an operator can make is displayed."
msgstr ""
#: ../../content/applications/websites/livechat/responses.rst:37
msgid "Send canned responses"
msgid "Type `@username` to mention a user in the conversation. A notification will be sent to that user's inbox or email, depending on their notification settings."
msgstr ""
#: ../../content/applications/websites/livechat/responses.rst:39
msgid "Type `#channel` to mention a *Discuss* channel."
msgstr ""
#: ../../content/applications/websites/livechat/responses.rst:40
msgid "Canned responses allow you to have a full piece of text being placed when you type a shortcut word. To create them, go to :menuselection:`Live Chat --> Configuration --> Canned Responses`."
msgid "Type `/command` to execute a command."
msgstr ""
#: ../../content/applications/websites/livechat/responses.rst:41
msgid "To use them during a conversation, simply type **:** followed by the shortcut word you created."
msgid "Type `:shortcut` to insert a :ref:`canned response <live-chat/canned-responses>`."
msgstr ""
#: ../../content/applications/websites/livechat/responses.rst:-1
msgid "View of a chat window and the use of a canned response in Odoo Live Chat"
msgid "View of the message generated from using the /help command in Odoo Live Chat."
msgstr ""
#: ../../content/applications/websites/livechat/responses.rst:48
msgid ":doc:`ratings`"
msgid ":doc:`/applications/productivity/discuss/overview/get_started`"
msgstr ""
#: ../../content/applications/websites/livechat/responses.rst:49
msgid ":doc:`/applications/productivity/discuss/overview/team_communication`"
msgstr ""
#: ../../content/applications/websites/livechat/responses.rst:52
msgid "Helpdesk & Helpdesk search"
msgstr ""
#: ../../content/applications/websites/livechat/responses.rst:54
msgid "The `/helpdesk` and `/helpdesk_search` commands allow operators to both create helpdesk tickets directly from a conversation, and search through existing tickets by keyword or ticket number."
msgstr ""
#: ../../content/applications/websites/livechat/responses.rst:58
msgid "The `/helpdesk` and `/helpdesk_search` commands can only be used if the *Helpdesk* app has been installed, and *Live Chat* has been activated on a *Helpdesk* team. To activate :guilabel:`Live Chat`, go to :menuselection:`Helpdesk application --> Configuration --> Teams`, and select a team. Scroll to the :guilabel:`Channels` section and check the box labeled :guilabel:`Live Chat`."
msgstr ""
#: ../../content/applications/websites/livechat/responses.rst:64
msgid "Create a ticket from a live chat"
msgstr ""
#: ../../content/applications/websites/livechat/responses.rst:66
msgid "If an operator types `/helpdesk` in the chat window, the conversation is used to create a *Helpdesk* ticket."
msgstr ""
#: ../../content/applications/websites/livechat/responses.rst:69
msgid "After entering the `/helpdesk` command, type a title for the ticket into the chat window, then press `Enter`."
msgstr ""
#: ../../content/applications/websites/livechat/responses.rst:-1
msgid "View of the results from a helpdesk search in a Live Chat conversation."
msgstr ""
#: ../../content/applications/websites/livechat/responses.rst:76
msgid "The newly created ticket will be added to the *Helpdesk* team that has live chat enabled. If more than one team has live chat enabled, the ticket will automatically be assigned based on the team's priority."
msgstr ""
#: ../../content/applications/websites/livechat/responses.rst:80
msgid "The transcript from the conversation will be added to the new ticket, under the :guilabel:`Description` tab."
msgstr ""
#: ../../content/applications/websites/livechat/responses.rst:83
msgid "To access the new ticket, click on the link in the chat window, or go to the :menuselection:`Helpdesk app` and click the :guilabel:`Tickets` button on the kanban card for the appropriate team."
msgstr ""
#: ../../content/applications/websites/livechat/responses.rst:88
msgid "Search for a ticket from a live chat"
msgstr ""
#: ../../content/applications/websites/livechat/responses.rst:90
msgid "If an operator types `/helpdesk_search` in the chat window, they can search through *Helpdesk* tickets by ticket number or keyword."
msgstr ""
#: ../../content/applications/websites/livechat/responses.rst:93
msgid "After entering the `/helpdesk_search` command, type a keyword or ticket number, then press `Enter`. If one or more related tickets are found, a list of links will be generated in the conversation window."
msgstr ""
#: ../../content/applications/websites/livechat/responses.rst:102
msgid "Results from the search command will only be seen by the operator, not the customer."
msgstr ""
#: ../../content/applications/websites/livechat/responses.rst:105
msgid "History"
msgstr ""
#: ../../content/applications/websites/livechat/responses.rst:107
msgid "If an operator types `/history` in the chat window, it will generate a list of the most recent pages the visitor has viewed on the website (up to 15)."
msgstr ""
#: ../../content/applications/websites/livechat/responses.rst:-1
msgid "View of the results from a /history command in a Live Chat conversation."
msgstr ""
#: ../../content/applications/websites/livechat/responses.rst:115
msgid "Lead"
msgstr ""
#: ../../content/applications/websites/livechat/responses.rst:117
msgid "By typing `/lead` in the chat window, an operator can create a *lead* in the *CRM* application."
msgstr ""
#: ../../content/applications/websites/livechat/responses.rst:-1
msgid "View of the results from a /lead command in a Live Chat conversation."
msgstr ""
#: ../../content/applications/websites/livechat/responses.rst:124
msgid "The `/lead` command can only be used if the *CRM* app has been installed."
msgstr ""
#: ../../content/applications/websites/livechat/responses.rst:126
msgid "After typing `/lead`, create a title for this new lead, then press `Enter`. A link with the lead title appears. Click the link, or navigate to the :menuselection:`CRM` app to view the :guilabel:`Pipeline`."
msgstr ""
#: ../../content/applications/websites/livechat/responses.rst:131
msgid "The link to the new lead can only be seen and accessed by the operator, not the customer."
msgstr ""
#: ../../content/applications/websites/livechat/responses.rst:133
msgid "The transcript of that specific live chat conversation (where the lead was created) is added to the :guilabel:`Internal Notes` tab of the lead form."
msgstr ""
#: ../../content/applications/websites/livechat/responses.rst:136
msgid "On the :guilabel:`Extra Information` tab of the lead form, the :guilabel:`Source` will be listed as :guilabel:`Livechat`."
msgstr ""
#: ../../content/applications/websites/livechat/responses.rst:140
msgid "Leave"
msgstr ""
#: ../../content/applications/websites/livechat/responses.rst:142
msgid "If an operator types `/leave` in the chat window, they can automatically exit the conversation. This command does not cause the customer to be removed from the conversation, nor does it automatically end the conversation."
msgstr ""
#: ../../content/applications/websites/livechat/responses.rst:147
msgid ":doc:`/applications/sales/crm/acquire_leads`"
msgstr ""
#: ../../content/applications/websites/livechat/responses.rst:148
msgid ":doc:`/applications/services/helpdesk/overview/getting_started`"
msgstr ""
#: ../../content/applications/websites/livechat/responses.rst:153
msgid "Canned responses"
msgstr ""
#: ../../content/applications/websites/livechat/responses.rst:155
msgid "*Canned responses* are customizable inputs where a *shortcut* stands in for a longer response. An operator will enter the shortcut, and it will automatically be replaced by the expanded *substitution* response in the conversation."
msgstr ""
#: ../../content/applications/websites/livechat/responses.rst:160
msgid "Create canned responses"
msgstr ""
#: ../../content/applications/websites/livechat/responses.rst:162
msgid "To create a new canned response, go to :menuselection:`Live Chat app --> Configuration --> Canned Responses --> New`."
msgstr ""
#: ../../content/applications/websites/livechat/responses.rst:165
msgid "From here, type the shortcut command into the :guilabel:`Shortcut` field."
msgstr ""
#: ../../content/applications/websites/livechat/responses.rst:167
msgid "Then, click into the :guilabel:`Substitution` field, and enter the custom message that will be sent to visitors in place of the shortcut. Click :guilabel:`Save`."
msgstr ""
#: ../../content/applications/websites/livechat/responses.rst:171
msgid "Try to connect the shortcut to the topic of the substitution. The easier it is for the operators to remember, the easier it will be to use the canned responses in conversations."
msgstr ""
#: ../../content/applications/websites/livechat/responses.rst:175
msgid "Use canned responses in a live chat conversation"
msgstr ""
#: ../../content/applications/websites/livechat/responses.rst:177
msgid "To use a canned response during a live chat conversation, type a colon (`:`) into the chat window, followed by the shortcut."
msgstr ""
#: ../../content/applications/websites/livechat/responses.rst:181
msgid "An operator is chatting with a visitor. As soon as they type `:` they would see a list of available responses. They can manually select one from the list, or continue to type. If they want to use the canned response `'I am sorry to hear that.'`, they would type `:sorry`."
msgstr ""
#: ../../content/applications/websites/livechat/responses.rst:-1
msgid "View of a chat window and the use of a canned response in Odoo Live Chat."
msgstr ""
#: ../../content/applications/websites/livechat/responses.rst:190
msgid "Typing `:` into a chat window on its own will generate a list of available canned responses. Responses can be manually selected from the list, in addition to the use of shortcuts."
msgstr ""
#: ../../content/applications/websites/livechat/responses.rst:0
msgid "View of a chat window and the list of available canned responses."
msgstr ""
#: ../../content/applications/websites/website.rst:8
@ -2401,6 +2786,123 @@ msgstr ""
msgid "The GeoIP database was unable to resolve the given IP address"
msgstr ""
#: ../../content/applications/websites/website/configuration/recaptcha.rst:3
msgid "reCAPTCHA v3 on forms"
msgstr ""
#: ../../content/applications/websites/website/configuration/recaptcha.rst:5
msgid "Google's reCAPTCHA protects website forms against spam and abuse. It attempts to distinguish between human and bot submissions."
msgstr ""
#: ../../content/applications/websites/website/configuration/recaptcha.rst:9
msgid "reCAPTCHA v3 works in the background and does not interrupt visitors. However, if the check fails, visitors cannot submit the form."
msgstr ""
#: ../../content/applications/websites/website/configuration/recaptcha.rst:13
msgid "`Google's reCAPTCHA v3 guide <https://developers.google.com/recaptcha/docs/v3>`_"
msgstr ""
#: ../../content/applications/websites/website/configuration/recaptcha.rst:19
msgid "On Google"
msgstr ""
#: ../../content/applications/websites/website/configuration/recaptcha.rst:21
msgid "Open `the reCAPTCHA website registration page <https://www.google.com/recaptcha/admin/create>`_. Log in or create a Google account if necessary."
msgstr ""
#: ../../content/applications/websites/website/configuration/recaptcha.rst:24
msgid "On the website registration page:"
msgstr ""
#: ../../content/applications/websites/website/configuration/recaptcha.rst:26
msgid "Give the website a :guilabel:`Label`."
msgstr ""
#: ../../content/applications/websites/website/configuration/recaptcha.rst:27
msgid "Leave the :guilabel:`reCAPTCHA type` on :guilabel:`Score based (v3)`."
msgstr ""
#: ../../content/applications/websites/website/configuration/recaptcha.rst:28
msgid "Enter one or more :guilabel:`Domains` (e.g., *example.com* or *subdomain.example.com*)."
msgstr ""
#: ../../content/applications/websites/website/configuration/recaptcha.rst:29
msgid "Under :guilabel:`Google Cloud Platform`, a project is automatically selected if one was already created with the logged-in Google account. If not, one is automatically created. Click :guilabel:`Google Cloud Platform` to select a project yourself or rename the automatically created project."
msgstr ""
#: ../../content/applications/websites/website/configuration/recaptcha.rst:33
msgid "Agree to the terms of service."
msgstr ""
#: ../../content/applications/websites/website/configuration/recaptcha.rst:34
msgid "Click :guilabel:`Submit`."
msgstr ""
#: ../../content/applications/websites/website/configuration/recaptcha.rst:-1
msgid "reCAPTCHA website registration example"
msgstr ""
#: ../../content/applications/websites/website/configuration/recaptcha.rst:39
msgid "A new page with the generated keys is then displayed. Leave it open for convenience, as copying the keys to Odoo is required next."
msgstr ""
#: ../../content/applications/websites/website/configuration/recaptcha.rst:43
msgid "On Odoo"
msgstr ""
#: ../../content/applications/websites/website/configuration/recaptcha.rst:45
msgid "From the database dashboard, click :guilabel:`Settings`. Under :guilabel:`Integrations`, enable :guilabel:`reCAPTCHA` if needed."
msgstr ""
#: ../../content/applications/websites/website/configuration/recaptcha.rst:49
msgid "Do not disable the :guilabel:`reCAPTCHA` feature or uninstall the :guilabel:`Google reCAPTCHA integration` module, as many other modules would also be removed."
msgstr ""
#: ../../content/applications/websites/website/configuration/recaptcha.rst:52
msgid "Open the Google reCAPTCHA page, copy the :guilabel:`Site key`, and paste it into the :guilabel:`Site Key` field in Odoo."
msgstr ""
#: ../../content/applications/websites/website/configuration/recaptcha.rst:54
msgid "Open the Google reCAPTCHA page, copy the :guilabel:`Secret key`, and paste it into the :guilabel:`Secret Key` field in Odoo."
msgstr ""
#: ../../content/applications/websites/website/configuration/recaptcha.rst:56
msgid "Change the default :guilabel:`Minimum score` (`0.5`) if necessary, using a value between `1.0` and `0.0`. The higher the threshold is, the more difficult it is to pass the reCAPTCHA, and vice versa."
msgstr ""
#: ../../content/applications/websites/website/configuration/recaptcha.rst:59
#: ../../content/applications/websites/website/configuration/translate.rst:95
msgid "Click :guilabel:`Save`."
msgstr ""
#: ../../content/applications/websites/website/configuration/recaptcha.rst:61
msgid "All pages using the :guilabel:`Form`, :guilabel:`Newsletter Block`, :guilabel:`Newsletter Popup` snippets, and the eCommerce :guilabel:`Extra Step During Checkout` form are now protected by reCAPTCHA."
msgstr ""
#: ../../content/applications/websites/website/configuration/recaptcha.rst:66
msgid "If the reCAPTCHA check fails, the following error message is displayed:"
msgstr ""
#: ../../content/applications/websites/website/configuration/recaptcha.rst:0
msgid "Google reCAPTCHA verification error message"
msgstr ""
#: ../../content/applications/websites/website/configuration/recaptcha.rst:71
msgid "reCAPTCHA v3 is free for up to `1 million assessments per month <https://developers.google.com/recaptcha/docs/faq#are-there-any-qps-or-daily-limits-on-my-use-of-recaptcha>`_."
msgstr ""
#: ../../content/applications/websites/website/configuration/recaptcha.rst:74
msgid "Analytics and additional settings are available on `Google's reCAPTCHA administration page <https://www.google.com/recaptcha/admin/>`_. For example, you can receive email alerts if Google detects suspicious traffic on your website or view the percentage of suspicious requests, which could help you determine the right minimum score."
msgstr ""
#: ../../content/applications/websites/website/configuration/recaptcha.rst:79
msgid "You can notify visitors that reCAPTCHA protects a form. To do so, open the website editor and navigate to the form. Then, click somewhere on the form, and on the right sidebar's :guilabel:`Customize` tab, toggle :guilabel:`Show reCAPTCHA Policy` found under the :guilabel:`Form` section."
msgstr ""
#: ../../content/applications/websites/website/configuration/recaptcha.rst:0
msgid "reCAPTCHA policy message displayed on a form"
msgstr ""
#: ../../content/applications/websites/website/configuration/translate.rst:3
msgid "Translations"
msgstr ""
@ -2537,10 +3039,6 @@ msgstr ""
msgid "Add a language selector menu."
msgstr ""
#: ../../content/applications/websites/website/configuration/translate.rst:95
msgid "Click :guilabel:`Save`."
msgstr ""
#: ../../content/applications/websites/website/configuration/unsplash.rst:3
msgid "Unsplash (free images)"
msgstr ""