[I18N] *: export 13.0 source terms

This commit is contained in:
Martin Trigaux 2020-09-24 12:03:20 +02:00
parent 7c24b8e156
commit a40685b5d3
23 changed files with 10523 additions and 7548 deletions

File diff suppressed because it is too large Load Diff

View File

@ -8,7 +8,7 @@ msgid ""
msgstr ""
"Project-Id-Version: Odoo 13.0\n"
"Report-Msgid-Bugs-To: \n"
"POT-Creation-Date: 2020-03-19 13:03+0100\n"
"POT-Creation-Date: 2020-09-24 12:02+0200\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"
@ -39,6 +39,7 @@ msgstr ""
#: ../../crm/acquire_leads/convert.rst:14
#: ../../crm/acquire_leads/generate_from_website.rst:41
#: ../../crm/acquire_leads/lead_mining.rst:8
#: ../../crm/optimize/gamification.rst:11
#: ../../crm/optimize/onsip.rst:13
#: ../../crm/optimize/partner_autocomplete.rst:9
#: ../../crm/track_leads/lead_scoring.rst:12
@ -196,7 +197,7 @@ msgid "When choosing to target Companied and their contacts you can choose the c
msgstr ""
#: ../../crm/acquire_leads/lead_mining.rst:39
msgid "You can decide to filter the leads you are getting depending on the size (number of employees) of the companies. You can pick the countries your leads are coming from. It is possible to pick multiple countries. You can pick the industries your leads are coming from. It is possible to pick multiple countries."
msgid "You can decide to filter the leads you are getting depending on the size (number of employees) of the companies. You can pick the countries your leads are coming from. It is possible to pick multiple countries. You can pick the industries your leads are coming from. It is possible to pick multiple industries."
msgstr ""
#: ../../crm/acquire_leads/lead_mining.rst:43
@ -213,7 +214,7 @@ msgid "Pricing"
msgstr ""
#: ../../crm/acquire_leads/lead_mining.rst:51
msgid "This is an In-App Purchase feature, each generated lead will cost you one credit. If you choose to get contact information each contact will also cost us one additional credit. Here is the pricing for this `feature <https://iap.odoo.com/iap/in-app-services/167?>`__, To buy credits you can either go to :menuselection:`CRM --> Configuration --> Settings --> Buy Credits`; or go to `Settings --> In-App Purchases --> View my Services`."
msgid "This is an In-App Purchase feature, each generated lead will cost you one credit. If you choose to get contact information each contact will also cost us one additional credit. Here is the pricing for this `feature <https://iap.odoo.com/iap/in-app-services/167?>`__, To buy credits you can either go to :menuselection:`CRM --> Configuration --> Settings --> Buy Credits`; or go to :menuselection:`Settings --> In-App Purchases --> View my Services`."
msgstr ""
#: ../../crm/acquire_leads/lead_mining.rst:65
@ -264,6 +265,90 @@ msgstr ""
msgid "Optimize your Day-to-Day work"
msgstr ""
#: ../../crm/optimize/gamification.rst:3
msgid "How to motivate and reward my salespeople?"
msgstr ""
#: ../../crm/optimize/gamification.rst:5
msgid "Challenging your employees to reach specific targets with goals and rewards is an excellent way to reinforce good habits and improve your salespeople productivity. The Gamification module gives you simple and creative ways to motivate and evaluate your employees with real-time recognition and badges inspired by game mechanics."
msgstr ""
#: ../../crm/optimize/gamification.rst:13
msgid "Install the *Gamification* module, or the *CRM gamification* one, which adds some useful data (goals and challenges) that can be used on *CRM/Sale*."
msgstr ""
#: ../../crm/optimize/gamification.rst:21
msgid "Create a challenge"
msgstr ""
#: ../../crm/optimize/gamification.rst:23
msgid "Now, create your first challenge by going to :menuselection:`Settings --> Gamification Tools --> Challenges`."
msgstr ""
#: ../../crm/optimize/gamification.rst:27
msgid "As the gamification tool is a one-time technical setup, you need to activate the technical features in order to access the configuration. To do so, go to *Settings* and *Activate the developer mode*."
msgstr ""
#: ../../crm/optimize/gamification.rst:35
msgid "A challenge is a mission that you send to your sales team. It can include one or several goals, set for a specific period of time. Configure your challenge as follows:"
msgstr ""
#: ../../crm/optimize/gamification.rst:38
msgid "Assign the salespeople to be challenged;"
msgstr ""
#: ../../crm/optimize/gamification.rst:39
msgid "Assign a responsible;"
msgstr ""
#: ../../crm/optimize/gamification.rst:40
msgid "Set up the periodicity along with the start and the end date;"
msgstr ""
#: ../../crm/optimize/gamification.rst:41
msgid "Select your goals;"
msgstr ""
#: ../../crm/optimize/gamification.rst:42
msgid "Set up your rewards (badges)."
msgstr ""
#: ../../crm/optimize/gamification.rst:45
msgid "Badges are granted when a challenge is finished. This is either at the end of a running period (eg: end of the month for a monthly challenge), at the end date of a challenge (if no periodicity is set), or when the challenge is manually closed."
msgstr ""
#: ../../crm/optimize/gamification.rst:49
msgid "In the example below, 2 employees are being challenged with a *Monthly Sales Target*. The challenge is based on 2 goals: the total amount invoiced and number of new leads generated. At the end of the month, the winner will be granted with a badge."
msgstr ""
#: ../../crm/optimize/gamification.rst:58
msgid "Set up goals"
msgstr ""
#: ../../crm/optimize/gamification.rst:60
msgid "The users can be evaluated using goals and numerical objectives to reach."
msgstr ""
#: ../../crm/optimize/gamification.rst:62
msgid "**Goals** are assigned through *challenges* that evaluate (see image above) and compare members of a team throughout time."
msgstr ""
#: ../../crm/optimize/gamification.rst:66
msgid "You can create a new goal on the fly from a *Challenge* by clicking on *Add new item*, under *Goals*. Select the business object according to your company's needs. Examples: number of new leads, time to qualify a lead, total amount invoiced in a specific week, month or any other time frame based on your management preferences, etc."
msgstr ""
#: ../../crm/optimize/gamification.rst:73
msgid "Goals may include your database setup as well (e.g. set your company data and a timezone, create new users, etc.)."
msgstr ""
#: ../../crm/optimize/gamification.rst:77
msgid "Set up rewards"
msgstr ""
#: ../../crm/optimize/gamification.rst:79
msgid "For non-numerical achievements, **Badges** can be granted to users. From a simple thank you to an exceptional achievement, a badge is an easy way to express gratitude to a user for their good work. To create and grant badges to your employees based on their performance, go to :menuselection:`Settings --> Gamification Tools --> Badges`."
msgstr ""
#: ../../crm/optimize/google_calendar_credentials.rst:3
msgid "Synchronize Google Calendar with Odoo"
msgstr ""

View File

@ -8,7 +8,7 @@ msgid ""
msgstr ""
"Project-Id-Version: Odoo 13.0\n"
"Report-Msgid-Bugs-To: \n"
"POT-Creation-Date: 2020-01-16 09:46+0100\n"
"POT-Creation-Date: 2020-09-24 12:02+0200\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"
@ -149,7 +149,7 @@ msgid "A test upgrade will create a copy of your database, upgrade it and make i
msgstr ""
#: ../../db_management/db_online.rst:116
msgid "**Testing your database is the most important step of the upgrade process!** Even though we test all upgrades manually, we do not know your work processes. A change in standard worfklows of Odoo in new versions might require you to change internal processes, or some of the customizations you made through Odoo Studio might now work properly. *It is up to you to make sure that everything works as it should!* You can report issues with your test database through our `Support page <https://www.odoo.com/help>`__."
msgid "**Testing your database is the most important step of the upgrade process!** Even though we test all upgrades manually, we do not know your work processes. A change in standard worfklows of Odoo in new versions might require you to change internal processes, or some of the customizations you made through Odoo Studio might not work properly. *It is up to you to make sure that everything works as it should!* You can report issues with your test database through our `Support page <https://www.odoo.com/help>`__."
msgstr ""
#: ../../db_management/db_online.rst:124

View File

@ -8,7 +8,7 @@ msgid ""
msgstr ""
"Project-Id-Version: Odoo 13.0\n"
"Report-Msgid-Bugs-To: \n"
"POT-Creation-Date: 2020-03-19 13:03+0100\n"
"POT-Creation-Date: 2020-09-24 12:02+0200\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"
@ -20,443 +20,517 @@ msgstr ""
msgid "Discuss"
msgstr ""
#: ../../discuss/email_servers.rst:3
msgid "How to use my mail server to send and receive emails in Odoo"
#: ../../discuss/advanced.rst:3
msgid "Advanced"
msgstr ""
#: ../../discuss/email_servers.rst:6
#: ../../discuss/advanced/email_servers.rst:3
msgid "How to Use my Mail Server to Send and Receive Emails in Odoo"
msgstr ""
#: ../../discuss/advanced/email_servers.rst:6
msgid "If you are a user of Odoo Online or Odoo.sh..."
msgstr ""
#: ../../discuss/email_servers.rst:8
#: ../../discuss/advanced/email_servers.rst:8
msgid "You have nothing to do! **Odoo sets up its own mail servers for your database.** Outgoing and incoming emails work out-of-the-box!"
msgstr ""
#: ../../discuss/email_servers.rst:11
#: ../../discuss/advanced/email_servers.rst:11
msgid "Unless you plan to send large batches of mass mailing that could require the use of an external mail server, simply enjoy your new Odoo database."
msgstr ""
#: ../../discuss/email_servers.rst:16
#: ../../discuss/advanced/email_servers.rst:16
msgid "Scope of this documentation"
msgstr ""
#: ../../discuss/email_servers.rst:18
#: ../../discuss/advanced/email_servers.rst:18
msgid "This document is **mainly dedicated to Odoo on-premise users** who don't benefit from an out-of-the-box solution to send and receive emails in Odoo, unlike `Odoo Online <https://www.odoo.com/trial>`__ & `Odoo.sh <https://www.odoo.sh>`__."
msgstr ""
#: ../../discuss/email_servers.rst:25
#: ../../discuss/advanced/email_servers.rst:25
msgid "If no one in your company is used to manage email servers, we strongly recommend that you opt for those Odoo hosting solutions. Their email system works instantly and is monitored by professionals. Nevertheless you can still use your own email servers if you want to manage your email server's reputation yourself."
msgstr ""
#: ../../discuss/email_servers.rst:31
#: ../../discuss/advanced/email_servers.rst:31
msgid "You will find here below some useful information on how to integrate your own email solution with Odoo."
msgstr ""
#: ../../discuss/email_servers.rst:34
#: ../../discuss/advanced/email_servers.rst:34
msgid "Office 365 email servers don't allow easily to send external emails from hosts like Odoo. Refer to the `Microsoft's documentation <https://support.office.com/en-us/article/How-to-set-up-a-multifunction-device-or-application-to-send-email-using-Office-365-69f58e99-c550-4274-ad18-c805d654b4c4>`__ to make it work."
msgstr ""
#: ../../discuss/email_servers.rst:40
#: ../../discuss/advanced/email_servers.rst:40
msgid "How to manage outbound messages"
msgstr ""
#: ../../discuss/email_servers.rst:41
#: ../../discuss/advanced/email_servers.rst:41
msgid "As a system admin, go to :menuselection:`Settings --> General Settings` and check *External Email Servers*. Then, click *Outgoing Mail Servers* to create one and reference the SMTP data of your email server. Once all the information has been filled out, click on *Test Connection*."
msgstr ""
#: ../../discuss/email_servers.rst:46
#: ../../discuss/advanced/email_servers.rst:46
msgid "Here is a typical configuration for a G Suite server."
msgstr ""
#: ../../discuss/email_servers.rst:51
#: ../../discuss/advanced/email_servers.rst:51
msgid "Then set your email domain name in the General Settings."
msgstr ""
#: ../../discuss/email_servers.rst:54
#: ../../discuss/advanced/email_servers.rst:54
msgid "If you get a ``[AUTHENTICATIONFAILED] Invalid credentials (Failure)`` warning when you *Test Connection* on a Gmail address, activate the *Less secure app access* option. A direct link can be `accessed here <https://myaccount.google.com/lesssecureapps?pli=1>`_."
msgstr ""
#: ../../discuss/email_servers.rst:58
#: ../../discuss/advanced/email_servers.rst:58
msgid "In addition to that, enable the IMAP setting on your Gmail account."
msgstr ""
#: ../../discuss/email_servers.rst:62
#: ../../discuss/advanced/email_servers.rst:62
msgid "Can I use an Office 365 server"
msgstr ""
#: ../../discuss/email_servers.rst:63
#: ../../discuss/advanced/email_servers.rst:63
msgid "You can use an Office 365 server if you run Odoo on-premise. Office 365 SMTP relays are not compatible with Odoo Online."
msgstr ""
#: ../../discuss/email_servers.rst:66
#: ../../discuss/advanced/email_servers.rst:66
msgid "Please refer to `Microsoft's documentation <https://support.office.com/en-us/article/How-to-set-up-a-multifunction-device-or-application-to-send-email-using-Office-365-69f58e99-c550-4274-ad18-c805d654b4c4>`__ to configure a SMTP relay for your Odoo's IP address."
msgstr ""
#: ../../discuss/email_servers.rst:70
#: ../../discuss/advanced/email_servers.rst:70
msgid "How to use a G Suite server"
msgstr ""
#: ../../discuss/email_servers.rst:71
#: ../../discuss/advanced/email_servers.rst:71
msgid "You can use an G Suite server for any Odoo hosting type. To do so you need to setup the SMTP relay service. The configuration steps are explained in `Google documentation <https://support.google.com/a/answer/2956491?hl=en>`__."
msgstr ""
#: ../../discuss/email_servers.rst:78
#: ../../discuss/advanced/email_servers.rst:78
msgid "Be SPF-compliant"
msgstr ""
#: ../../discuss/email_servers.rst:79
#: ../../discuss/advanced/email_servers.rst:79
msgid "In case you use SPF (Sender Policy Framework) to increase the deliverability of your outgoing emails, don't forget to authorize Odoo as a sending host in your domain name settings. Here is the configuration for Odoo Online:"
msgstr ""
#: ../../discuss/email_servers.rst:83
#: ../../discuss/advanced/email_servers.rst:83
msgid "If no TXT record is set for SPF, create one with following definition: v=spf1 include:_spf.odoo.com ~all"
msgstr ""
#: ../../discuss/email_servers.rst:85
#: ../../discuss/advanced/email_servers.rst:85
msgid "In case a SPF TXT record is already set, add \"include:_spf.odoo.com\". e.g. for a domain name that sends emails via Odoo Online and via G Suite it could be: v=spf1 include:_spf.odoo.com include:_spf.google.com ~all"
msgstr ""
#: ../../discuss/email_servers.rst:89
#: ../../discuss/advanced/email_servers.rst:89
msgid "Find `here <https://www.mail-tester.com/spf/>`__ the exact procedure to create or modify TXT records in your own domain registrar."
msgstr ""
#: ../../discuss/email_servers.rst:92
#: ../../discuss/advanced/email_servers.rst:92
msgid "Your new SPF record can take up to 48 hours to go into effect, but this usually happens more quickly."
msgstr ""
#: ../../discuss/email_servers.rst:95
#: ../../discuss/advanced/email_servers.rst:95
msgid "Adding more than one SPF record for a domain can cause problems with mail delivery and spam classification. Instead, we recommend using only one SPF record by modifying it to authorize Odoo."
msgstr ""
#: ../../discuss/email_servers.rst:100
#: ../../discuss/advanced/email_servers.rst:100
msgid "Allow DKIM"
msgstr ""
#: ../../discuss/email_servers.rst:101
#: ../../discuss/advanced/email_servers.rst:101
msgid "You should do the same thing if DKIM (Domain Keys Identified Mail) is enabled on your email server. In the case of Odoo Online & Odoo.sh, you should add a DNS \"odoo._domainkey\" CNAME record to \"odoo._domainkey.odoo.com\". For example, for \"foo.com\" they should have a record \"odoo._domainkey.foo.com\" that is a CNAME with the value \"odoo._domainkey.odoo.com\"."
msgstr ""
#: ../../discuss/email_servers.rst:109
#: ../../discuss/advanced/email_servers.rst:109
msgid "Restriction"
msgstr ""
#: ../../discuss/advanced/email_servers.rst:110
msgid "Please note that the port 25 is blocked for security reasons. Try using 587, 465 or 2525."
msgstr ""
#: ../../discuss/advanced/email_servers.rst:113
msgid "How to manage inbound messages"
msgstr ""
#: ../../discuss/email_servers.rst:111
#: ../../discuss/advanced/email_servers.rst:115
msgid "Odoo relies on generic email aliases to fetch incoming messages."
msgstr ""
#: ../../discuss/email_servers.rst:113
#: ../../discuss/advanced/email_servers.rst:117
msgid "**Reply messages** of messages sent from Odoo are routed to their original discussion thread (and to the inbox of all its followers) by the catchall alias (**catchall@**)."
msgstr ""
#: ../../discuss/email_servers.rst:117
#: ../../discuss/advanced/email_servers.rst:121
msgid "**Bounced messages** are routed to **bounce@** in order to track them in Odoo. This is especially used in `Odoo Email Marketing <https://www.odoo.com/page/email-marketing>`__ to opt-out invalid recipients."
msgstr ""
#: ../../discuss/email_servers.rst:121
#: ../../discuss/advanced/email_servers.rst:125
msgid "**Original messages**: Several business objects have their own alias to create new records in Odoo from incoming emails:"
msgstr ""
#: ../../discuss/email_servers.rst:124
#: ../../discuss/advanced/email_servers.rst:128
msgid "Sales Channel (to create Leads or Opportunities in `Odoo CRM <https://www.odoo.com/page/crm>`__),"
msgstr ""
#: ../../discuss/email_servers.rst:126
#: ../../discuss/advanced/email_servers.rst:130
msgid "Support Channel (to create Tickets in `Odoo Helpdesk <https://www.odoo.com/page/helpdesk>`__),"
msgstr ""
#: ../../discuss/email_servers.rst:128
#: ../../discuss/advanced/email_servers.rst:132
msgid "Projects (to create new Tasks in `Odoo Project <https://www.odoo.com/page/project-management>`__),"
msgstr ""
#: ../../discuss/email_servers.rst:130
#: ../../discuss/advanced/email_servers.rst:134
msgid "Job Positions (to create Applicants in `Odoo Recruitment <https://www.odoo.com/page/recruitment>`__),"
msgstr ""
#: ../../discuss/email_servers.rst:132
#: ../../discuss/advanced/email_servers.rst:136
msgid "etc."
msgstr ""
#: ../../discuss/email_servers.rst:134
#: ../../discuss/advanced/email_servers.rst:138
msgid "Depending on your mail server, there might be several methods to fetch emails. The easiest and most recommended method is to manage one email address per Odoo alias in your mail server."
msgstr ""
#: ../../discuss/email_servers.rst:138
#: ../../discuss/advanced/email_servers.rst:142
msgid "Create the corresponding email addresses in your mail server (catchall@, bounce@, sales@, etc.)."
msgstr ""
#: ../../discuss/email_servers.rst:140
#: ../../discuss/advanced/email_servers.rst:144
msgid "Set your domain name in the General Settings."
msgstr ""
#: ../../discuss/email_servers.rst:145
#: ../../discuss/advanced/email_servers.rst:149
msgid "If you use Odoo on-premise, create an *Incoming Mail Server* in Odoo for each alias. You can do it from the General Settings as well. Fill out the form according to your email providers settings. Leave the *Actions to Perform on Incoming Mails* blank. Once all the information has been filled out, click on *TEST & CONFIRM*."
msgstr ""
#: ../../discuss/email_servers.rst:154
#: ../../discuss/advanced/email_servers.rst:158
msgid "If you use Odoo Online or Odoo.sh, We do recommend to redirect incoming messages to Odoo's domain name rather than exclusively use your own email server. That way you will receive incoming messages without delay. Indeed, Odoo Online is fetching incoming messages of external servers once per hour only. You should set redirections for all the email addresses to Odoo's domain name in your email server (e.g. *catchall@mydomain.ext* to *catchall@mycompany.odoo.com*)."
msgstr ""
#: ../../discuss/email_servers.rst:164
#: ../../discuss/advanced/email_servers.rst:168
msgid "All the aliases are customizable in Odoo."
msgstr ""
#: ../../discuss/email_servers.rst:162
#: ../../discuss/advanced/email_servers.rst:166
msgid "Object aliases can be edited from their respective configuration view. To edit catchall and bounce aliases, you first need to activate the :doc:`Developer mode <../../general/developer_mode/activate>`."
msgstr ""
#: ../../discuss/email_servers.rst:166
#: ../../discuss/advanced/email_servers.rst:170
msgid "Then go to :menuselection:`Settings --> Technical --> Parameters --> System Parameters` to customize the aliases (*mail.catchall.alias* & * mail.bounce.alias*)."
msgstr ""
#: ../../discuss/email_servers.rst:172
#: ../../discuss/advanced/email_servers.rst:176
msgid "By default inbound messages are fetched every 5 minutes in Odoo on-premise. You can change this value in :doc:`Developer mode <../../general/developer_mode/activate>`. Go to :menuselection:`Settings --> Technical --> Automation --> Scheduled Actions` and look for *Mail: Fetchmail Service*."
msgstr ""
#: ../../discuss/mail_twitter.rst:3
msgid "How to follow Twitter feed from Odoo"
#: ../../discuss/advanced/email_template.rst:3
msgid "Email Templates"
msgstr ""
#: ../../discuss/mail_twitter.rst:8
msgid "You can follow specific hashtags on Twitter and see the tweets within the Odoo Discuss channels of your choice. The tweets are retrieved periodically from Twitter. An authenticated user can retweet the messages."
#: ../../discuss/advanced/email_template.rst:5
msgid "We all know writing good emails is vital to get a high response rate, but you do not want to rewrite the same structure every time, do you? That is where email templates come in. Without the need to rewrite the entire email structure every time, you save time to focus on the content. Multiple templates also let you deliver the right message to the right audience, improving their overall experience with the company."
msgstr ""
#: ../../discuss/mail_twitter.rst:13
msgid "Setting up the App on Twitter's side"
#: ../../discuss/advanced/email_template.rst:12
msgid "Enable it and understand a few concepts"
msgstr ""
#: ../../discuss/mail_twitter.rst:15
msgid "Twitter uses an \"App\" on its side which is opens a gate to which Odoo asks for tweets, and through which a user can retweet. To set up this app, go to http://apps.twitter.com/app/new and put in the values:"
#: ../../discuss/advanced/email_template.rst:14
msgid "The :doc:`Developer mode <../../general/developer_mode/activate>` must be activated. Then, go to :menuselection:`Settings --> Technical --> Templates`. A view of the existing templates is shown."
msgstr ""
#: ../../discuss/mail_twitter.rst:19
msgid "Name: this is the name of the application on Twitter"
#: ../../discuss/advanced/email_template.rst:18
msgid "**It is highly recommended not to change the content in existing templates unless the user has prior knowledge about placeholders.**"
msgstr ""
#: ../../discuss/mail_twitter.rst:21
msgid "Website: this is the external url of your Odoo database, with \"/web\" added. For example, if your Odoo instance is hosted at \"http://www.example.com\", you should put \"http://www.example.com/web\" in this field."
#: ../../discuss/advanced/email_template.rst:21
msgid "To add a new one, click on *Create* and choose the type of document this template is used with. In the example below, the template would be sent to job applicants."
msgstr ""
#: ../../discuss/mail_twitter.rst:25
msgid "Callback URL: this is the address on which Twitter will respond. Following the previous example you should write \"http://www.example.com/web/twitter/callback\"."
#: ../../discuss/advanced/email_template.rst:30
msgid "Under *Email Configuration*, fields such as *From*, *To (Emails)*, *To (Partners)*, require placeholders. If the *From* field is not set, the default value is the authors email alias, if configured, or email address."
msgstr ""
#: ../../discuss/mail_twitter.rst:28
msgid "Do not forget to accept the terms **Developer agreement** of use and click on **Create your Twitter application** at the bottom of the page."
#: ../../discuss/advanced/email_template.rst:32
msgid "Under *Advanced Settings*, if an *Outgoing Mail Server* is not set, the one with the highest priority is used."
msgstr ""
#: ../../discuss/mail_twitter.rst:33
msgid "Getting the API key and secret"
#: ../../discuss/advanced/email_template.rst:34
msgid "The option *Auto Delete* permanently deletes the emails after they are sent, saving space in your database."
msgstr ""
#: ../../discuss/mail_twitter.rst:35
msgid "When on the App dashboard, switch to the **Keys and Access Tokens** tab."
#: ../../discuss/advanced/email_template.rst:37
msgid "Writing content including placeholder expressions"
msgstr ""
#: ../../discuss/mail_twitter.rst:40
msgid "And copy those values in Odoo in :menuselection:`Settings--> General Settings--> Twitter discuss integration` and click on **Save** to save the settings."
#: ../../discuss/advanced/email_template.rst:39
msgid "Under the tab *Dynamic Placeholder Generator*, look for the *Field* you would like to use."
msgstr ""
#: ../../discuss/mentions.rst:3
msgid "How to grab attention of other users in my messages"
#: ../../discuss/advanced/email_template.rst:45
msgid "Next, copy the *Placeholder Expression* and paste it in the *Body* of the email, under the *Content* tab, using - essentially - the *Code View*."
msgstr ""
#: ../../discuss/mentions.rst:5
msgid "You can **mention** a user in a channel or chatter by typing **@user-name**. Mentioning a user in the chatter will set them as a follower of the item (if they are not already) and send a message to their inbox. The item containing the mention will also be bolded in the list view. Mentioning a user in a channel will send a message to their inbox. You cannot mention a user in a channel who is not subscribed to the channel. Typing **#channel-name** will provide a link to the mentioned channel in either a chatter or another channel."
msgstr ""
#: ../../discuss/mentions.rst:15
msgid "Direct messaging a user"
msgstr ""
#: ../../discuss/mentions.rst:17
msgid "**Direct messages** are private messages viewable only by the sender and recipient. You can send direct messages to other users from within the Discuss module by creating a new conversation or selecting an existing one from the sidebar. Direct messages can be sent from anywhere in Odoo using the speech bubble icon in the top bar. The online status of other users is displayed to the left of their name. A **green dot** indicates that a user is Online, an **orange dot** that they are Idle, and a **grey dot** that they are offline."
msgstr ""
#: ../../discuss/mentions.rst:28
msgid "Desktop notifications from Discuss"
msgstr ""
#: ../../discuss/mentions.rst:30
msgid "You can choose to see **desktop notifications** when you receive a new direct message. The notification shows you the sender and a brief preview of the message contents. These can be configured or disabled by clicking on the gear icon in the corner of the notification.."
msgstr ""
#: ../../discuss/monitoring.rst:3
msgid "How to be responsive at work thanks to my Odoo inbox"
msgstr ""
#: ../../discuss/monitoring.rst:5
msgid "Use the **Inbox** in Discuss app to monitor updates and progress on everything you do in Odoo. Notifications and messages from everything you follow or in which you are mentioned appear in your inbox."
msgstr ""
#: ../../discuss/monitoring.rst:13
msgid "You can keep an eye on your **Inbox** from any screen."
msgstr ""
#: ../../discuss/monitoring.rst:18
msgid "Marking an item with a check marks the message as **read** and removes it from your inbox. If you would like to save an item for future reference or action, mark it with a star to add it to the **Starred** box. You can star any message or notification in Discuss or any of the item-specific chatters throughout Odoo to keep tabs on it here."
#: ../../discuss/advanced/email_template.rst:52
msgid "Deactivate the *Code View* option by simply clicking on it again, and easily design the message. Click on *Preview* to check how the email looks before sending it."
msgstr ""
#: ../../discuss/overview.rst:3
msgid "Why use Odoo Discuss"
msgid "Overview"
msgstr ""
#: ../../discuss/overview.rst:5
msgid "Odoo Discuss is an easy to use messaging app for teams that brings all your organization's communication into one place and seamlessly integrates with the Odoo platform. Discuss lets you send and receive messages from wherever you are in Odoo as well as manage your messages and notifications easily from within the app. Discuss allows you to create **channels** for team chats, conversations about projects, meeting coordination, and more in one simple and searchable interface."
#: ../../discuss/overview/get_started.rst:3
msgid "Get Started with Discuss"
msgstr ""
#: ../../discuss/plan_activities.rst:3
msgid "Get organized by planning activities"
#: ../../discuss/overview/get_started.rst:5
msgid "Discuss allows you to bring all of your companys communication together through messages, notes, and chat. Share information, projects, files, prioritize tasks, and stay connected with colleagues and partners throughout applications. Forge better relationships, increase productivity and transparency by promoting a convenient way of communicating."
msgstr ""
#: ../../discuss/plan_activities.rst:5
msgid "Planning activities is the perfect way to keep on track with your work. Get reminded of what needs to be done and schedule the next activities to undertake."
#: ../../discuss/overview/get_started.rst:11
msgid "Choose your notifications preference"
msgstr ""
#: ../../discuss/plan_activities.rst:9
msgid "Your activities are available wherever you are in Odoo. It is easy to manage your priorities."
#: ../../discuss/overview/get_started.rst:13
msgid "Access your *Preferences* and choose how you would like your :doc:`Chatter <../../project/tasks/collaborate>` notifications to be handled."
msgstr ""
#: ../../discuss/plan_activities.rst:15
msgid "Activities can be planned and managed from the chatters or in the kanban views. Here is an example for opportunities :"
#: ../../discuss/overview/get_started.rst:22
msgid "By default, the field is set as *Handle by Emails* making messages, notes, and notifications where you were mentioned or that you follow, to be sent through email. By choosing *Handle in Odoo*, they are shown in the *Inbox*."
msgstr ""
#: ../../discuss/plan_activities.rst:22
#: ../../discuss/overview/get_started.rst:23
msgid "Messages can then be *Marked as Todo*, *Replied*, or *Marked as Read*."
msgstr ""
#: ../../discuss/overview/get_started.rst:29
msgid "The messages tagged as *Mark as Todo* are also shown in *Starred*, while the ones *Marked as Read* are moved to *History*."
msgstr ""
#: ../../discuss/overview/get_started.rst:37
msgid "Start Chatting"
msgstr ""
#: ../../discuss/overview/get_started.rst:39
msgid "The first time you log in to your account, OdooBot sends you a message asking for permission to receive desktop notifications to chats. If accepted, you receive push notifications to the messages sent to you despite of where you are in Odoo."
msgstr ""
#: ../../discuss/overview/get_started.rst:49
msgid "To stop receiving desktop notifications, reset the notifications settings of your browser."
msgstr ""
#: ../../discuss/overview/get_started.rst:51
msgid "To start a chat, click on *New Message* on the *Messaging Menu*, or go to *Discuss* and send a *Direct Message*."
msgstr ""
#: ../../discuss/overview/get_started.rst:59
msgid "You can also create :doc:`public and private channels <team_communication>`."
msgstr ""
#: ../../discuss/overview/get_started.rst:62
msgid "Mentions in the chat and on the Chatter"
msgstr ""
#: ../../discuss/overview/get_started.rst:65
msgid "To mention a user within a chat or the :doc:`chatter <../../project/tasks/collaborate>` type *@user-name*; to refer to a channel, type *#channel-name*."
msgstr ""
#: ../../discuss/overview/get_started.rst:67
msgid "A notification is sent to the user mentioned either to his *Inbox* or through email, depending on his settings."
msgstr ""
#: ../../discuss/overview/get_started.rst:74
msgid "When a user is mentioned, the search list (list of names) suggests values first based on the tasks :doc:`followers <../../project/tasks/collaborate>`, and secondly on *Employees*. If the record being searched does not match with either a follower or employee, the scope of the search becomes all partners."
msgstr ""
#: ../../discuss/overview/get_started.rst:80
msgid "Chat status"
msgstr ""
#: ../../discuss/overview/get_started.rst:82
msgid "It is helpful to see what colleagues are up to and how quickly they can respond to messages by checking their *Status*. The status is shown on the left side of a contacts names on Discuss sidebar and on the *Messaging menu*."
msgstr ""
#: ../../discuss/overview/get_started.rst:86
msgid "Green = online"
msgstr ""
#: ../../discuss/overview/get_started.rst:87
msgid "Orange = away"
msgstr ""
#: ../../discuss/overview/get_started.rst:88
msgid "White = offline"
msgstr ""
#: ../../discuss/overview/get_started.rst:89
msgid "Airplane = out of the office"
msgstr ""
#: ../../discuss/overview/get_started.rst:97
msgid ":doc:`../../project/tasks/collaborate`"
msgstr ""
#: ../../discuss/overview/get_started.rst:98
#: ../../discuss/overview/plan_activities.rst:65
msgid ":doc:`team_communication`"
msgstr ""
#: ../../discuss/overview/get_started.rst:99
msgid ":doc:`../advanced/email_servers`"
msgstr ""
#: ../../discuss/overview/plan_activities.rst:3
msgid "Get Organized by Planning Activities"
msgstr ""
#: ../../discuss/overview/plan_activities.rst:5
msgid "When you plan activities you minimize the risk of uncertainties, as you provide clear directions for the course of your next action. In addition to that, you do not leave space for wasteful activities and reduce the chance of having overlapping actions between team members."
msgstr ""
#: ../../discuss/overview/plan_activities.rst:10
msgid "Where do I see my schedule activities?"
msgstr ""
#: ../../discuss/overview/plan_activities.rst:12
msgid "Access and manage your activities wherever you are in Odoo by the *Activities* menu."
msgstr ""
#: ../../discuss/overview/plan_activities.rst:20
msgid "Plan activities"
msgstr ""
#: ../../discuss/overview/plan_activities.rst:22
msgid "Activities can be planned and managed from the :doc:`Chatter <../../project/tasks/collaborate>` by clicking on *Schedule activity*, or through Kanban views."
msgstr ""
#: ../../discuss/overview/plan_activities.rst:31
msgid "Set your activity types"
msgstr ""
#: ../../discuss/plan_activities.rst:24
msgid "A number of generic activities types are available by default in Odoo (e.g. call, email, meeting, etc.). If you would like to set new ones, go to :menuselection:`Settings --> General settings --> Activity types`."
#: ../../discuss/overview/plan_activities.rst:33
msgid "A number of activities types are available by default in Odoo (call, email, meeting, etc.). However, you can set new ones going to :menuselection:`Settings --> Activity types`."
msgstr ""
#: ../../discuss/plan_activities.rst:29
msgid "Schedule meetings"
#: ../../discuss/overview/plan_activities.rst:42
msgid "If you need to create an activity type with an available calendar, make sure to create it with an *Action to Perform* set as *Meeting*."
msgstr ""
#: ../../discuss/plan_activities.rst:31
msgid "Activities are planned for specific days. If you need to set hours, go with the *Meeting* activity type. When scheduling one, the calendar will simply open to let you select a time slot."
#: ../../discuss/overview/plan_activities.rst:46
msgid "Recommend next activities"
msgstr ""
#: ../../discuss/plan_activities.rst:36
msgid "If you need to use other activity types with a calendar planning, make sure their *Category* is set as *Meeting*."
#: ../../discuss/overview/plan_activities.rst:48
msgid "Odoo helps you to plan a flow of activities by allowing you to set *Recommended Next Activities*."
msgstr ""
#: ../../discuss/plan_activities.rst:40
msgid "Schedule a chain of activities to follow"
#: ../../discuss/overview/plan_activities.rst:55
msgid "Once the respective activity is completed, select *Done & Schedule Next* and next steps are suggested to you."
msgstr ""
#: ../../discuss/plan_activities.rst:42
msgid "Odoo helps you easily plan your usual flow of activities. Go to :menuselection:`Configuration --> Activity Types` and set the common following steps as *Recommended next activities*."
#: ../../discuss/overview/plan_activities.rst:64
#: ../../discuss/overview/team_communication.rst:115
msgid ":doc:`get_started`"
msgstr ""
#: ../../discuss/plan_activities.rst:49
msgid "Now, when an activity is completed, you can select *Done & schedule next*. The next steps will automatically be suggested to you."
#: ../../discuss/overview/team_communication.rst:3
msgid "Efficiently Communicate Using Channels"
msgstr ""
#: ../../discuss/plan_activities.rst:55
msgid "Have fun getting better organized by planning activities !"
#: ../../discuss/overview/team_communication.rst:5
msgid "You can use channels to organize discussions between individual teams, departments, projects, or any other group that requires regular communication. This way, you keep everyone in the loop updated with the latest developments."
msgstr ""
#: ../../discuss/team_communication.rst:3
msgid "How to efficiently communicate in team using channels"
#: ../../discuss/overview/team_communication.rst:10
msgid "Public and Private channels"
msgstr ""
#: ../../discuss/team_communication.rst:5
msgid "You can use **channels** to organize discussions between individual teams, departments, projects, or any other group that requires regular communication. By having conversations that everyone in the channel can see, it's easy to keep the whole team in the loop with the latest developments."
#: ../../discuss/overview/team_communication.rst:12
msgid "A *Public* channel can be seen by everyone, while a *Private* one is only visible to users invited to it."
msgstr ""
#: ../../discuss/team_communication.rst:12
msgid "Creating a channel"
#: ../../discuss/overview/team_communication.rst:21
msgid "A public channel is best used when many employees need to access information (such as company announcements), whereas a private channel could be used whenever information should be limited to specific groups (such as a specific department)."
msgstr ""
#: ../../discuss/team_communication.rst:14
msgid "In Discuss there are two types of channels - **public** and **private**."
#: ../../discuss/overview/team_communication.rst:26
msgid "Configuration options"
msgstr ""
#: ../../discuss/team_communication.rst:17
msgid "A **public channel** can only be created by an administrator with write privileges and can be seen by everyone in the organization. By contrast, a **private channel** can be created by any user and by default is only visible to users who have been invited to this channel."
#: ../../discuss/overview/team_communication.rst:28
msgid "You can configure a channels name, description, email alias, and privacy by clicking on the *Channel Settings* icon on the sidebar."
msgstr ""
#: ../../discuss/team_communication.rst:24
msgid "A public channel is best used when many employees need to access information (such as interdepartmental communication or company announcements), whereas a private channel should be used whenever information should be limited to specific users/employees (such as department specific or sensitive information)."
#: ../../discuss/overview/team_communication.rst:36
msgid "Privacy and Members"
msgstr ""
#: ../../discuss/team_communication.rst:31
msgid "Configuring a channel"
#: ../../discuss/overview/team_communication.rst:40
msgid "Changing *Who can follow the groups activities?* allows you to control which groups can have access to the channel. Note that allowing *Everyone* to follow a private channel lets other users view and join it, as they would a public one."
msgstr ""
#: ../../discuss/team_communication.rst:33
msgid "You can configure a channel's name, description, access rights, automatic subscription, and emailing from :menuselection:`#channel-name --> Settings`. Changing channel access rights allows you to control which groups can view each channel. You can make a channel visible by all users, invited users, or users within a selected user group. Note that allowing \"Everyone\" to follow a private channel will let other users view and join it as they would a public channel."
#: ../../discuss/overview/team_communication.rst:42
msgid "If you choose *Invited people only*, go to the *Members* tab to add your members, or, go to Discuss main page, select the channel and click on *Invite*."
msgstr ""
#: ../../discuss/team_communication.rst:47
msgid "How to set up a mailing list"
#: ../../discuss/overview/team_communication.rst:49
msgid "For *Selected group of users*, the option *Auto Subscribe Groups* automatically add its members as followers. In other words, while *Authorized Groups* limits which users can access the channel, *Auto Subscribe Groups* automatically adds the user as a member as long as they are part of the group."
msgstr ""
#: ../../discuss/team_communication.rst:49
msgid "A channel can be configured to behave as a mailing list. From within :menuselection:`#channel-name --> Settings`, define the email you would like to use. Users can then post to the channel and choose to receive notifications using the defined email address. An envelope icon will appear next to the channel name in the list to indicate that a channel will send messages by email."
#: ../../discuss/overview/team_communication.rst:55
msgid "Use a channel as a mailing list"
msgstr ""
#: ../../discuss/team_communication.rst:57
msgid "Locating a channel"
#: ../../discuss/overview/team_communication.rst:57
msgid "Choosing to *Send messages by email* configures the channel to behave as a mailing list."
msgstr ""
#: ../../discuss/team_communication.rst:59
msgid "If you do not see a channel on your dashboard, you can search the list of **public channels** to locate the correct channel or create a new channel by clicking the plus icon."
#: ../../discuss/overview/team_communication.rst:59
msgid "Enabling this option allows you to *Moderate this channel*, meaning that messages will need to be approved before being sent."
msgstr ""
#: ../../discuss/team_communication.rst:66
msgid "You can also click the **CHANNELS** heading to browse a list of all public channels. This allows the user to manually **join** and **leave** public channels from a single screen."
#: ../../discuss/overview/team_communication.rst:66
msgid "Under the *Moderation* tab choose as many moderators as you need, and if you would like them to receive an *Automatic notification*."
msgstr ""
#: ../../discuss/team_communication.rst:71
msgid "It is always wise to search for a channel before creating a new one to ensure that duplicate entries are not created for the same topic."
#: ../../discuss/overview/team_communication.rst:67
msgid "Mark *Send guidelines to new subscribers* to automatically send instructions to newcomers."
msgstr ""
#: ../../discuss/team_communication.rst:76
msgid "Using filters to navigate within Discuss"
#: ../../discuss/overview/team_communication.rst:73
msgid "Moderators can: *Accept*, *Reject*, *Discard*, *Always Allow* or *Ban* messages."
msgstr ""
#: ../../discuss/team_communication.rst:78
msgid "The topbar search provides access to the same comprehensive search function present in the rest of Odoo. You can apply multiple **filter criteria** and **save filters** for later use. The search function accepts wildcards by using the underscore character \"\\ **\\_**\\ \" to represent a **single character wildcard.**"
#: ../../discuss/overview/team_communication.rst:80
msgid "Members of a mailing channel receive messages through email regardless of their :doc:`notification preference <get_started>`."
msgstr ""
#: ../../discuss/tracking.rst:3
msgid "How to follow a discussion thread and define what I want to hear about"
#: ../../discuss/overview/team_communication.rst:83
msgid "Once a channel is moderated, the menu *Ban List* allows you to add email addresses per moderated channel to auto-ban them from sending messages."
msgstr ""
#: ../../discuss/tracking.rst:6
msgid "How to follow a discussion thread"
#: ../../discuss/overview/team_communication.rst:91
msgid "Quick search bar"
msgstr ""
#: ../../discuss/tracking.rst:7
msgid "You can keep track of virtually any business object in Odoo (an opportunity, a quotation, a task, etc.), by **following** it."
#: ../../discuss/overview/team_communication.rst:93
msgid "Once at least 20 channels, direct message and live chat conversations (if the module is installed on your database) are pinned in the sidebar, a *Quick search…* bar is displayed. It is a clever way to filter conversations and quickly find the one you need."
msgstr ""
#: ../../discuss/tracking.rst:14
msgid "How to choose the events to follow"
#: ../../discuss/overview/team_communication.rst:103
msgid "Finding channels"
msgstr ""
#: ../../discuss/tracking.rst:15
msgid "You can choose which types of events you want to be notified about. The example below shows the options available when following a **task** in the **Project** app."
#: ../../discuss/overview/team_communication.rst:106
msgid "Click on *Channels* (on the sidebar), browse through the list of public channels, and join or leave them from a single screen."
msgstr ""
#: ../../discuss/tracking.rst:23
msgid "How to add other followers"
#: ../../discuss/overview/team_communication.rst:108
msgid "Apply filters criteria and save it for later use. The search function accepts wildcards by using the underscore character *(_)* to represent a single character."
msgstr ""
#: ../../discuss/tracking.rst:24
msgid "You can invite other users and add channels as followers. Adding a channel as a follower will send messages posted in the chatter to the channel with a link back to the original document."
msgstr ""
#: ../../discuss/tracking.rst:34
msgid "How to be a default follower"
msgstr ""
#: ../../discuss/tracking.rst:35
msgid "You are automatically set as a default follower of any item you create. In some applications like CRM and Project, you can be a default follower of any new record created to get notified of specific events (e.g. a new task created, an opportunity won)."
msgstr ""
#: ../../discuss/tracking.rst:40
msgid "To do so, start following the parent business object (e.g. the sales channel in CRM, the project in Project). Then, choose the events you want to hear about."
#: ../../discuss/overview/team_communication.rst:116
msgid ":doc:`plan_activities`"
msgstr ""

View File

@ -8,7 +8,7 @@ msgid ""
msgstr ""
"Project-Id-Version: Odoo 13.0\n"
"Report-Msgid-Bugs-To: \n"
"POT-Creation-Date: 2020-03-19 13:03+0100\n"
"POT-Creation-Date: 2020-09-24 12:02+0200\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"
@ -537,242 +537,6 @@ msgstr ""
msgid "Get paid"
msgstr ""
#: ../../ecommerce/shopper_experience/authorize.rst:3
msgid "How to get paid with Authorize.Net"
msgstr ""
#: ../../ecommerce/shopper_experience/authorize.rst:5
msgid "Authorize.Net is one of the most popular eCommerce payment platforms in North America. Unlike most of the other payment acquirers compatible with Odoo, Authorize.Net can be used as `payment gateway <https://www.authorize.net/solutions/merchantsolutions/pricing/?p=gwo>`__ only. That way you can use the `payment processor or merchant <https://www.authorize.net/partners/resellerprogram/processorlist/>`__ that you like."
msgstr ""
#: ../../ecommerce/shopper_experience/authorize.rst:12
msgid "Create an Authorize.Net account"
msgstr ""
#: ../../ecommerce/shopper_experience/authorize.rst:14
msgid "Create an `Authorize.Net account <https://www.authorize.net>`__ by clicking 'Get Started'."
msgstr ""
#: ../../ecommerce/shopper_experience/authorize.rst:16
msgid "In the pricing page, press *Sign up now* if you want to use Authorize.net as both payment gateway and merchant. If you want to use your own merchant, press the related option."
msgstr ""
#: ../../ecommerce/shopper_experience/authorize.rst:23
msgid "Go through the registration steps."
msgstr ""
#: ../../ecommerce/shopper_experience/authorize.rst:24
msgid "The account is set as a test account by default. You can use this test account to process a test transaction from Odoo."
msgstr ""
#: ../../ecommerce/shopper_experience/authorize.rst:26
msgid "Once ready, switch to **Production** mode."
msgstr ""
#: ../../ecommerce/shopper_experience/authorize.rst:30
msgid "Set up Odoo"
msgstr ""
#: ../../ecommerce/shopper_experience/authorize.rst:31
msgid "Activate Authorize.Net in Odoo from :menuselection:`Website or Sales or Accounting --> Settings --> Payment Acquirers`."
msgstr ""
#: ../../ecommerce/shopper_experience/authorize.rst:33
msgid "Enter both your **Login ID** your **API Transaction Key** and your **API Signature Key**."
msgstr ""
#: ../../ecommerce/shopper_experience/authorize.rst:39
msgid "To get those credentials from Authorize.Net, you can follow the direction in the Authorize.net Help `API Credentials and Keys <https://account.authorize.net/help/Account/Settings/Security_Settings/General_Settings/API_Login_ID_and_Transaction_Key.htm>`__ entry and access the menu :menuselection:`Account --> Settings --> API Credentials & Keys` in the Authorize.net dashboard. Note that you need *both* a Transaction key and and Signature key."
msgstr ""
#: ../../ecommerce/shopper_experience/authorize.rst:45
msgid "Once both keys are set up, you can then generate a Client Key by clicking the \"Generate Client Key\" button. Note that these 3 keys are necessary for the setup to work correctly."
msgstr ""
#: ../../ecommerce/shopper_experience/authorize.rst:51
msgid "Go live"
msgstr ""
#: ../../ecommerce/shopper_experience/authorize.rst:52
msgid "Your configuration is now ready! You can make Authorize.Net visible on your merchant interface and activate the **Enabled** state."
msgstr ""
#: ../../ecommerce/shopper_experience/authorize.rst:59
msgid "Credentials provided by Authorize.net are different for both test and production mode. Don't forget to update them in Odoo when you switch from testing to production or vice-versa."
msgstr ""
#: ../../ecommerce/shopper_experience/authorize.rst:65
msgid "Assess Authorize.Net as payment solution"
msgstr ""
#: ../../ecommerce/shopper_experience/authorize.rst:66
msgid "You can test and assess Authorize.Net for free by creating a `developer account <https://developer.authorize.net>`__."
msgstr ""
#: ../../ecommerce/shopper_experience/authorize.rst:68
msgid "Once the account created you receive sandbox credentials. Enter them in Odoo as explained here above and make sure you are still in *Test* mode."
msgstr ""
#: ../../ecommerce/shopper_experience/authorize.rst:72
msgid "You can also log in to `Authorize.Net sandbox platform <https://sandbox.authorize.net/>`__ to configure your sandbox account."
msgstr ""
#: ../../ecommerce/shopper_experience/authorize.rst:75
msgid "To perform ficticious transactions you can use fake card numbers provided in the `Authorize.Net Testing Guide <https://developer.authorize.net/hello_world/testing_guide/>`__."
msgstr ""
#: ../../ecommerce/shopper_experience/authorize.rst:80
#: ../../ecommerce/shopper_experience/paypal.rst:206
msgid ":doc:`payment`"
msgstr ""
#: ../../ecommerce/shopper_experience/authorize.rst:81
#: ../../ecommerce/shopper_experience/payment.rst:111
#: ../../ecommerce/shopper_experience/paypal.rst:207
msgid ":doc:`payment_acquirer`"
msgstr ""
#: ../../ecommerce/shopper_experience/payment.rst:3
msgid "How to get paid with payment acquirers"
msgstr ""
#: ../../ecommerce/shopper_experience/payment.rst:5
msgid "Odoo embeds several payment methods to get paid on eCommerce, Sales and Invoicing apps."
msgstr ""
#: ../../ecommerce/shopper_experience/payment.rst:10
msgid "What are the payment methods available"
msgstr ""
#: ../../ecommerce/shopper_experience/payment.rst:13
msgid "Wire transfer"
msgstr ""
#: ../../ecommerce/shopper_experience/payment.rst:15
msgid "Wire Transfer is the default payment method available. The aim is providing your customers with your bank details so they can pay on their own via their bank. This is very easy to start with but slow and inefficient process-wise. Opt for online acquirers as soon as you can!"
msgstr ""
#: ../../ecommerce/shopper_experience/payment.rst:21
msgid "Payment acquirers"
msgstr ""
#: ../../ecommerce/shopper_experience/payment.rst:23
msgid "Redirect your customers to payment platforms to collect money effortless and track the payment status (call-back). Odoo supports more and more platforms over time:"
msgstr ""
#: ../../ecommerce/shopper_experience/payment.rst:27
msgid "`Paypal <paypal.html>`__"
msgstr ""
#: ../../ecommerce/shopper_experience/payment.rst:28
msgid "Ingenico"
msgstr ""
#: ../../ecommerce/shopper_experience/payment.rst:29
msgid "Authorize.net"
msgstr ""
#: ../../ecommerce/shopper_experience/payment.rst:30
msgid "Adyen"
msgstr ""
#: ../../ecommerce/shopper_experience/payment.rst:31
msgid "Buckaroo"
msgstr ""
#: ../../ecommerce/shopper_experience/payment.rst:32
msgid "PayUmoney"
msgstr ""
#: ../../ecommerce/shopper_experience/payment.rst:33
msgid "Sips"
msgstr ""
#: ../../ecommerce/shopper_experience/payment.rst:34
msgid "Stripe"
msgstr ""
#: ../../ecommerce/shopper_experience/payment.rst:38
msgid "How to go live"
msgstr ""
#: ../../ecommerce/shopper_experience/payment.rst:40
msgid "Once the payment method is ready, make it visible in the payment interface by switching the state to **Enabled**."
msgstr ""
#: ../../ecommerce/shopper_experience/payment.rst:48
msgid "How to let customers save and reuse credit cards"
msgstr ""
#: ../../ecommerce/shopper_experience/payment.rst:49
msgid "To ease the payment of returning customers, you can let them save and reuse a credit card if they want to. If so, a payment token will be saved in Odoo. This option is available with Ingenico and Authorize.net."
msgstr ""
#: ../../ecommerce/shopper_experience/payment.rst:54
#: ../../ecommerce/shopper_experience/payment.rst:68
msgid "You can turn this on from the acquirer configuration form."
msgstr ""
#: ../../ecommerce/shopper_experience/payment.rst:61
msgid "How to debit credit cards to pay subscriptions"
msgstr ""
#: ../../ecommerce/shopper_experience/payment.rst:62
msgid "`Odoo Subscription <https://www.odoo.com/page/subscriptions>`__ allows to bill services automatically on a recurring basis. Along with it, you can have an automatic debit of the customer's credit card."
msgstr ""
#: ../../ecommerce/shopper_experience/payment.rst:66
msgid "This option is available with Ingenico and Authorize.net."
msgstr ""
#: ../../ecommerce/shopper_experience/payment.rst:73
msgid "That way a payment token will be recorded when the customer goes for the subscription and an automatic debit will occur whenever an invoice is issued from the subscription."
msgstr ""
#: ../../ecommerce/shopper_experience/payment.rst:79
msgid "How to use other acquirers (advanced)"
msgstr ""
#: ../../ecommerce/shopper_experience/payment.rst:81
msgid "Odoo can submit single payment requests and redirect to any payment acquirer. But there is no call-back, i.e. Odoo doesn't track the transaction status. So you will confirm orders manually once you get paid."
msgstr ""
#: ../../ecommerce/shopper_experience/payment.rst:85
msgid "How to:"
msgstr ""
#: ../../ecommerce/shopper_experience/payment.rst:87
msgid "Switch to :doc:`Developer mode <../../../general/developer_mode/activate>`."
msgstr ""
#: ../../ecommerce/shopper_experience/payment.rst:89
msgid "Take the **Custom** payment method."
msgstr ""
#: ../../ecommerce/shopper_experience/payment.rst:91
msgid "Set up the payment form (S2S Form Template) as instructed by your payment acquirer. You can start from *default_acquirer_button* that you can duplicate."
msgstr ""
#: ../../ecommerce/shopper_experience/payment.rst:96
msgid "Other configurations"
msgstr ""
#: ../../ecommerce/shopper_experience/payment.rst:98
msgid "Odoo can also be used for more advanced payment processes like installment plans (e.g. `Paypal Installment Plans <https://developer.paypal.com/docs/classic/paypal-payments-standard/integration-guide/installment_buttons>`__)."
msgstr ""
#: ../../ecommerce/shopper_experience/payment.rst:102
msgid "Such a customization service is made on-demand by our technical experts based on your own requirements. A business advisor can reach you out for such matter. `Contact us <https://www.odoo.com/page/contactus>`_."
msgstr ""
#: ../../ecommerce/shopper_experience/payment.rst:109
msgid ":doc:`paypal`"
msgstr ""
#: ../../ecommerce/shopper_experience/payment.rst:110
msgid ":doc:`wire_transfer`"
msgstr ""
#: ../../ecommerce/shopper_experience/payment_acquirer.rst:3
msgid "How to manage orders paid with payment acquirers"
msgstr ""
@ -826,7 +590,7 @@ msgid "When the order is confirmed you can also have an invoice automatically is
msgstr ""
#: ../../ecommerce/shopper_experience/payment_acquirer.rst:54
msgid "If you choose this mode you are requested to select a payment journal in order to record payments in your books. This payment is automatically reconcilied with the invoice, marking it as paid. Select your **bank account** if you get paid immediately on your bank account. If you don't you can create a specific journal for the payment acquirer (type = Bank). That way, you can track online payments in an intermediary account of your books until you get paid into your bank account (see :doc:`../../accounting/receivables/customer_payments/credit_cards`)."
msgid "If you choose this mode you are requested to select a payment journal in order to record payments in your books. This payment is automatically reconcilied with the invoice, marking it as paid. Select your **bank account** if you get paid immediately on your bank account. If you don't you can create a specific journal for the payment acquirer (type = Bank). That way, you can track online payments in an intermediary account of your books until you get paid into your bank account (see :doc:`../../general/payment_acquirers/payment_acquirers`)."
msgstr ""
#: ../../ecommerce/shopper_experience/payment_acquirer.rst:63
@ -845,214 +609,6 @@ msgstr ""
msgid "With other payment acquirers, you can manage the capture in their own interfaces, not from Odoo."
msgstr ""
#: ../../ecommerce/shopper_experience/paypal.rst:3
msgid "Configure your Paypal account"
msgstr ""
#: ../../ecommerce/shopper_experience/paypal.rst:5
msgid "Paypal is available and popular worldwide. It doesnt charge any subscription fee and creating an account is very easy. Thats why we definitely recommend it for starters in Odoo. It works as a seamless flow where the customer is routed to Paypal website to register the payment."
msgstr ""
#: ../../ecommerce/shopper_experience/paypal.rst:12
msgid "Paypal account"
msgstr ""
#: ../../ecommerce/shopper_experience/paypal.rst:14
msgid "A business account is needed to get paid with Paypal. Create a `Paypal Business Account <https://www.paypal.com/us/merchantsignup/ applicationChecklist?signupType=CREATE_NEW_ACCOUNT&productIntentId=wp_standard>`_ or upgrade your Personal account to a Business account. Go to the Paypal settings and click on *Upgrade to a Business account*. Then follow the few configuration steps."
msgstr ""
#: ../../ecommerce/shopper_experience/paypal.rst:23
msgid "Settings in Paypal"
msgstr ""
#: ../../ecommerce/shopper_experience/paypal.rst:26
msgid "First, lets see how to set up your Paypal account in order to build a seamless customer experience with Odoo."
msgstr ""
#: ../../ecommerce/shopper_experience/paypal.rst:28
msgid "Log in and open the settings. Go to :menuselection:`Products & Services --> Website payments` and click **Update** on **Website preferences**."
msgstr ""
#: ../../ecommerce/shopper_experience/paypal.rst:34
msgid "Auto Return"
msgstr ""
#: ../../ecommerce/shopper_experience/paypal.rst:36
msgid "*Auto Return* automatically redirects your customers to Odoo once the payment is processed. Check *Auto Return* and enter your domain name with the suffix ``/shop/confirmation`` as *Return URL* (e.g. ``https://yourcompany.odoo.com/shop/confirmation``)."
msgstr ""
#: ../../ecommerce/shopper_experience/paypal.rst:41
msgid "This URL is requested in Paypal but not used in practice as Odoo transmits it at each transaction. Dont worry if you manage several sales channels or Odoo databases."
msgstr ""
#: ../../ecommerce/shopper_experience/paypal.rst:49
msgid "Payment Data Transfer (PDT)"
msgstr ""
#: ../../ecommerce/shopper_experience/paypal.rst:51
msgid "*Payment Data Transfer* delivers the payment confirmation to Odoo as soon as it is processed. Without it, Odoo cannot end the sales flow. This setting must be activated as well. When saving, an *Identity Token* is generated. You will be later requested to enter it in Odoo."
msgstr ""
#: ../../ecommerce/shopper_experience/paypal.rst:59
msgid "Paypal Account Optional"
msgstr ""
#: ../../ecommerce/shopper_experience/paypal.rst:61
msgid "We advise you to not prompt customers to log in with a Paypal account when they get to pay. Let them pay with debit/credit cards as well, or you might lose some deals. Make sure this setting is turned on."
msgstr ""
#: ../../ecommerce/shopper_experience/paypal.rst:68
msgid "Instant Payment Notification (IPN)"
msgstr ""
#: ../../ecommerce/shopper_experience/paypal.rst:70
msgid "PDT sends order confirmations once and only once. As a result, your site must be running when it happens; otherwise, it will never receive the message. Thats why we advise to activate the *Instant Payment Notification* (IPN) on top. With IPN, delivery of order confirmations is virtually guaranteed since IPN resends a confirmation until your site acknowledges receipt."
msgstr ""
#: ../../ecommerce/shopper_experience/paypal.rst:77
msgid "To activate IPN, get back to *Website payments* menu and click *Update* in *Instant Payment Notification*."
msgstr ""
#: ../../ecommerce/shopper_experience/paypal.rst:79
msgid "The *Notification URL* to set is your domain name + “payment/paypal/ipn” (e.g. ``https://yourcompany.odoo.com/payment/paypal/ipn``)."
msgstr ""
#: ../../ecommerce/shopper_experience/paypal.rst:85
msgid "Payment Messages Format"
msgstr ""
#: ../../ecommerce/shopper_experience/paypal.rst:87
msgid "If you use accented characters (or anything else than basic Latin characters) for your customer names, addresses... you MUST configure the encoding format of the payment request sent by Odoo to Paypal."
msgstr ""
#: ../../ecommerce/shopper_experience/paypal.rst:93
msgid "If you don't configure this setting, some transactions fail without notice."
msgstr ""
#: ../../ecommerce/shopper_experience/paypal.rst:95
msgid "To do so, open:"
msgstr ""
#: ../../ecommerce/shopper_experience/paypal.rst:97
msgid "`this page for a test account <https://sandbox.paypal.com/cgi-bin/customerprofileweb?cmd=_profile-language-encoding>`__"
msgstr ""
#: ../../ecommerce/shopper_experience/paypal.rst:99
msgid "`this page for a production account <https://www.paypal.com/cgi-bin/customerprofileweb?cmd=_profile-language-encoding>`__"
msgstr ""
#: ../../ecommerce/shopper_experience/paypal.rst:101
msgid "Then, click *More Options* and set the two default encoding formats as **UTF-8**."
msgstr ""
#: ../../ecommerce/shopper_experience/paypal.rst:109
msgid "Your Paypal account is ready!"
msgstr ""
#: ../../ecommerce/shopper_experience/paypal.rst:112
msgid "If you want your customers to pay without creating a Paypal account, *Paypal Account Optional* needs to be turned on."
msgstr ""
#: ../../ecommerce/shopper_experience/paypal.rst:118
msgid "For Encrypted Website Payments & EWP_SETTINGS error, please check the `Paypal documentation <https://developer.paypal.com/docs/ classic/paypal-payments-standard/integration-guide/encryptedwebpayments/ #encrypted-website-payments-ewp>`_."
msgstr ""
#: ../../ecommerce/shopper_experience/paypal.rst:124
msgid "Settings in Odoo"
msgstr ""
#: ../../ecommerce/shopper_experience/paypal.rst:127
msgid "Activation"
msgstr ""
#: ../../ecommerce/shopper_experience/paypal.rst:129
msgid "Activate *Paypal* from the config bar of Sales, Invoicing and eCommerce apps, or from the configuration menu of *Payment Acquirers*."
msgstr ""
#: ../../ecommerce/shopper_experience/paypal.rst:133
msgid "Credentials"
msgstr ""
#: ../../ecommerce/shopper_experience/paypal.rst:135
msgid "Odoo requires three Paypal credentials:"
msgstr ""
#: ../../ecommerce/shopper_experience/paypal.rst:137
msgid "*Email ID* is your login email address in Paypal."
msgstr ""
#: ../../ecommerce/shopper_experience/paypal.rst:138
msgid "*Merchant ID* can be found in the settings of your Paypal account, in :menuselection:`Profile --> About the business`."
msgstr ""
#: ../../ecommerce/shopper_experience/paypal.rst:140
msgid "*Paypal PDT Token* is given in *Website payments* configuration as explained here above."
msgstr ""
#: ../../ecommerce/shopper_experience/paypal.rst:146
msgid "Transaction fees"
msgstr ""
#: ../../ecommerce/shopper_experience/paypal.rst:148
msgid "You can charge extra fees to your customers for paying with Paypal; This to cover the transaction fees Paypal charges you. Once redirected to Paypal, your customer sees an extra applied to the order amount."
msgstr ""
#: ../../ecommerce/shopper_experience/paypal.rst:151
msgid "To activate this, go to the Configuration tab of Paypal configuration in Odoo and check *Add Extra Fees*."
msgstr ""
#: ../../ecommerce/shopper_experience/paypal.rst:157
msgid "You can refer to `Paypal Fees <https://www.paypal.com/webapps/mpp/paypal-fees>`__ to set up fees."
msgstr ""
#: ../../ecommerce/shopper_experience/paypal.rst:161
msgid "`Traders in the EU <https://europa.eu/youreurope/citizens/consumers/shopping/pricing-payments/ index_en.htm>`_ are not allowed to charge extra fees for paying with credit cards."
msgstr ""
#: ../../ecommerce/shopper_experience/paypal.rst:165
msgid "Go live!"
msgstr ""
#: ../../ecommerce/shopper_experience/paypal.rst:167
msgid "Your configuration is ready to roll. Make sure *Production* mode is on. Then publish the payment method by clicking the *Published* button right next to it."
msgstr ""
#: ../../ecommerce/shopper_experience/paypal.rst:176
msgid "Paypal is now available in your payment form available in eCommerce, Sales and Invoicing apps. Customers are redirected to Paypal website when hitting *Pay Now*. They get back to a confirmation page in Odoo once the payment is processed."
msgstr ""
#: ../../ecommerce/shopper_experience/paypal.rst:185
msgid "Test environment"
msgstr ""
#: ../../ecommerce/shopper_experience/paypal.rst:187
msgid "You can test the entire payment flow in Odoo thanks to Paypal Sandbox accounts."
msgstr ""
#: ../../ecommerce/shopper_experience/paypal.rst:189
msgid "Log in to `Paypal Developer Site <https://developer.paypal.com/>`__ with your Paypal credentials."
msgstr ""
#: ../../ecommerce/shopper_experience/paypal.rst:191
msgid "This will create two sandbox accounts:"
msgstr ""
#: ../../ecommerce/shopper_experience/paypal.rst:193
msgid "A business account (to use as merchant, e.g. `pp.merch01-facilitator@example.com <mailto:pp.merch01-facilitator@example.com>`__)."
msgstr ""
#: ../../ecommerce/shopper_experience/paypal.rst:195
msgid "A default personal account (to use as shopper, e.g. `pp.merch01-buyer@example.com <mailto:pp.merch01-buyer@example.com>`__)."
msgstr ""
#: ../../ecommerce/shopper_experience/paypal.rst:197
msgid "Log in to Paypal Sandbox with the merchant account and follow the same configuration instructions. Enter your sandbox credentials in Odoo and make sure Paypal is still set on *Test Environment*. Also, make sure the automatic invoicing is not activated in your eCommerce settings, to not generate invoices when a fictitious transaction is completed."
msgstr ""
#: ../../ecommerce/shopper_experience/paypal.rst:203
msgid "Run a test transaction from Odoo using the sandbox personal account."
msgstr ""
#: ../../ecommerce/shopper_experience/portal.rst:3
msgid "How customers can access their customer account"
msgstr ""
@ -1085,42 +641,6 @@ msgstr ""
msgid "If the customer is set as a contact of a company in your address book, they will see all the documents whose the customer belongs to this company."
msgstr ""
#: ../../ecommerce/shopper_experience/wire_transfer.rst:3
msgid "How to get paid with wire transfers"
msgstr ""
#: ../../ecommerce/shopper_experience/wire_transfer.rst:5
msgid "**Wire Transfer** is the default payment method available. The aim is providing your customers with your bank details so they can pay on their own. This is very easy to start with but slow and inefficient process-wise. Opt for payment acquirers as soon as you can!"
msgstr ""
#: ../../ecommerce/shopper_experience/wire_transfer.rst:13
msgid "How to provide customers with payment instructions"
msgstr ""
#: ../../ecommerce/shopper_experience/wire_transfer.rst:14
msgid "Put your payment instructions in the **Thanks Message** of your payment method."
msgstr ""
#: ../../ecommerce/shopper_experience/wire_transfer.rst:19
msgid "They will appear to the customers when they place an order."
msgstr ""
#: ../../ecommerce/shopper_experience/wire_transfer.rst:26
msgid "How to manage an order once you get paid"
msgstr ""
#: ../../ecommerce/shopper_experience/wire_transfer.rst:28
msgid "Whenever a customer pays by wire transfer, the order stays in an intermediary stage **Quotation Sent** (i.e. unpaid order). When you get paid, you confirm the order manually to launch the delivery."
msgstr ""
#: ../../ecommerce/shopper_experience/wire_transfer.rst:35
msgid "How to create other manual payment methods"
msgstr ""
#: ../../ecommerce/shopper_experience/wire_transfer.rst:37
msgid "If you manage a B2B business, you can create other manually-processed payment methods like paying by check. To do so, just rename *Wire Transfer* or duplicate it."
msgstr ""
#: ../../ecommerce/taxes.rst:3
msgid "Collect taxes"
msgstr ""

View File

@ -8,7 +8,7 @@ msgid ""
msgstr ""
"Project-Id-Version: Odoo 13.0\n"
"Report-Msgid-Bugs-To: \n"
"POT-Creation-Date: 2020-03-19 13:03+0100\n"
"POT-Creation-Date: 2020-09-24 12:02+0200\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"
@ -62,7 +62,7 @@ msgid "Cost: 0.0"
msgstr ""
#: ../../expense/expense.rst:33
msgid "Don't forget to set an expense tax on each expense type (and an account if you use Odoo Accounting). It's usually a good practice to use a tax that is configured with *Tax Included in Price* (see: :doc:`../accounting/fiscality/taxes/tax_included`). That way, employees report expenses with prices including taxes, which is usually the expected behaviour."
msgid "Don't forget to set an expense tax on each expense type (and an account if you use Odoo Accounting). It's usually a good practice to use a tax that is configured with :ref:`Tax Included in Price <taxes/included-in-price>`. That way, employees report expenses with prices including taxes, which is usually the expected behaviour."
msgstr ""
#: ../../expense/expense.rst:41
@ -110,7 +110,7 @@ msgid "The only thing to do is setting up an email alias in :menuselection:`Expe
msgstr ""
#: ../../expense/expense.rst:83
msgid "The expense product is set automatically if the mail subject contains the product's internal reference between brackets (e.g. [Food]). Type the expense amount in the mail subject to set it on the expense too."
msgid "The expense product is set automatically if the mail subject contains the product's internal reference in first position. Type the expense amount in the mail subject to set it on the expense too (e.g. Ref001 Food 100€)."
msgstr ""
#: ../../expense/expense.rst:88

View File

@ -8,7 +8,7 @@ msgid ""
msgstr ""
"Project-Id-Version: Odoo 13.0\n"
"Report-Msgid-Bugs-To: \n"
"POT-Creation-Date: 2020-03-19 13:03+0100\n"
"POT-Creation-Date: 2020-09-24 12:02+0200\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"
@ -43,7 +43,7 @@ msgstr ""
msgid "Go to :menuselection:`Helpdesk --> Configuration --> Helpdesk Teams --> Edit` and enable :menuselection:`Onsite Interventions --> Save`."
msgstr ""
#: ../../fsm/helpdesk/plan_onsite.rst:15
#: ../../fsm/helpdesk/plan_onsite.rst:17
msgid "Now once your helpdesk team needs, they have the option to *Plan Intervention* from tickets."
msgstr ""
@ -168,7 +168,7 @@ msgid "Create projects per team, or per working site, and have a more accurate a
msgstr ""
#: ../../fsm/overview/manage_employees_schedule.rst:42
msgid ":doc:`../../project/configuration/setup`"
msgid ":doc:`../../project/overview/setup`"
msgstr ""
#: ../../fsm/overview/planning_itinerary.rst:3
@ -223,7 +223,7 @@ msgstr ""
msgid "Second, go to :menuselection:`Configuration --> Projects` and enable *Extra Quotations*."
msgstr ""
#: ../../fsm/sales/create_quotations.rst:21
#: ../../fsm/sales/create_quotations.rst:23
msgid "You can now create *New Quotations* directly from your tasks."
msgstr ""

File diff suppressed because it is too large Load Diff

View File

@ -8,7 +8,7 @@ msgid ""
msgstr ""
"Project-Id-Version: Odoo 13.0\n"
"Report-Msgid-Bugs-To: \n"
"POT-Creation-Date: 2020-03-19 13:03+0100\n"
"POT-Creation-Date: 2020-09-24 12:02+0200\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"
@ -20,411 +20,609 @@ msgstr ""
msgid "Helpdesk"
msgstr ""
#: ../../helpdesk/after_sales.rst:3
msgid "After sales features: refund, coupon, return, repair, onsite interventions"
#: ../../helpdesk/advanced.rst:3
msgid "Advanced"
msgstr ""
#: ../../helpdesk/after_sales.rst:5
msgid "As my business grows, having the tools to allow my helpdesk team to record, track and manage issues raised easy and efficiently, is key. Odoos Helpdesk app allows me to generate credit notes, return products, grant coupons, do repairs and plan onsite interventions from a tickets page."
#: ../../helpdesk/advanced/after_sales.rst:3
msgid "After Sales Features"
msgstr ""
#: ../../helpdesk/after_sales.rst:10
msgid "Set up the After Sales services"
#: ../../helpdesk/advanced/after_sales.rst:5
msgid "As your business grows, having the right tool to support your helpdesk team on recording, tracking and managing issues raised easy and efficiently, is key. Odoos Helpdesk application allows you to generate credit notes, manage returns, products, repairs, grant coupons, and even plan onsite interventions from a tickets page."
msgstr ""
#: ../../helpdesk/after_sales.rst:12
msgid "Go to :menuselection:`Configuration --> Helpdesk Teams` and enable the After Sales options: *Refunds, Returns, Coupons, Repairs and Onsite Interventions*."
#: ../../helpdesk/advanced/after_sales.rst:11
msgid "Set up the after sales services"
msgstr ""
#: ../../helpdesk/after_sales.rst:19
#: ../../helpdesk/advanced/after_sales.rst:13
msgid "Go to :menuselection:`Helpdesk --> Configuration --> Helpdesk Teams` and enable the after sales options: *Refunds, Returns, Coupons, Repairs and Onsite Interventions*."
msgstr ""
#: ../../helpdesk/advanced/after_sales.rst:20
msgid "Generate credit notes from tickets"
msgstr ""
#: ../../helpdesk/after_sales.rst:21
msgid "I can use a credit note to refund a customer or adjust the amount due. For that, Ill simply go to my ticket page, click on *Refund* and select the corresponding *Invoice*. Clicking on *Reverse* the credit note will be generated, and I can *Post* it while still being in the *Helpdesk* app."
#: ../../helpdesk/advanced/after_sales.rst:22
msgid "You can use a credit note to refund a customer or adjust the amount due. For that, simply go to your ticket page, click on *Refund* and select the corresponding *Invoice*. Clicking on *Reverse* generates a credit note, and you can *Post* it while still being in the *Helpdesk* app."
msgstr ""
#: ../../helpdesk/after_sales.rst:29
#: ../../helpdesk/advanced/after_sales.rst:30
msgid "Allow product returns from tickets"
msgstr ""
#: ../../helpdesk/after_sales.rst:31
msgid "The process of a product return from my customer back to my warehouse will be taken into action when, at the ticket page, I choose the option *Return*."
#: ../../helpdesk/advanced/after_sales.rst:32
msgid "The process of a product return from your customer back to your warehouse is taken into action when, at the ticket page, you choose the option *Return*."
msgstr ""
#: ../../helpdesk/after_sales.rst:38
#: ../../helpdesk/advanced/after_sales.rst:39
msgid "Grant coupons from tickets"
msgstr ""
#: ../../helpdesk/after_sales.rst:40
msgid "First, be sure to have your *Coupon Program* planned at the *Sales or Website* app. At the *Helpdesk* app, I will open my ticket and click on *Coupon*, choose the :menuselection:`Coupon Program --> Generate`."
#: ../../helpdesk/advanced/after_sales.rst:41
msgid "First, be sure to have your *Coupon Program* planned in the *Sales* or *Website* application. Then, in *Helpdesk*, open your ticket, click on *Coupon*, and choose the respective one."
msgstr ""
#: ../../helpdesk/after_sales.rst:48
#: ../../helpdesk/advanced/after_sales.rst:48
msgid "Repairs from tickets"
msgstr ""
#: ../../helpdesk/after_sales.rst:50
msgid "Clicking on *Repair* option, on my ticket page, a new repair order form will be shown. Fill up the rest of the fields as needed and choose the next step."
#: ../../helpdesk/advanced/after_sales.rst:50
msgid "Clicking on *Repair* option, on your ticket page, a new repair order form is shown. Fill in the information as needed and choose the next step."
msgstr ""
#: ../../helpdesk/after_sales.rst:57
#: ../../helpdesk/advanced/after_sales.rst:57
msgid "Plan onsite interventions from tickets"
msgstr ""
#: ../../helpdesk/after_sales.rst:59
msgid "At the ticket page, I can now configure my onsite interventions exactly the same way I would do being on the *Field Service* app, clicking on *Plan Intervention*."
#: ../../helpdesk/advanced/after_sales.rst:59
msgid "At the ticket's page click on *Plan Intervention*, and set up your onsite intervention exactly the same way as if you were on the *Field Service* application."
msgstr ""
#: ../../helpdesk/after_sales.rst:66
#: ../../helpdesk/advanced/after_sales.rst:67
msgid ":doc:`../../fsm/overview/invoicing_time`"
msgstr ""
#: ../../helpdesk/advanced/after_sales.rst:68
msgid "`Coupons <https://www.odoo.com/slides/slide/coupon-programs-640?fullscreen=1>`_"
msgstr ""
#: ../../helpdesk/after_sales.rst:67
msgid ":doc:`../manufacturing/repair/repair`"
#: ../../helpdesk/advanced/after_sales.rst:69
msgid ":doc:`../../manufacturing/repair/repair`"
msgstr ""
#: ../../helpdesk/close_tickets.rst:3
msgid "Allow customers to close their tickets"
#: ../../helpdesk/advanced/close_tickets.rst:3
msgid "Allow Customers to Close their Tickets"
msgstr ""
#: ../../helpdesk/close_tickets.rst:5
#: ../../helpdesk/advanced/close_tickets.rst:5
msgid "Allowing customers to close their tickets gives them autonomy and minimize misunderstandings about when an issue is considered solved, or not. It makes communication and actions more efficient."
msgstr ""
#: ../../helpdesk/close_tickets.rst:9
#: ../../helpdesk/advanced/close_tickets.rst:9
msgid "Configure the feature"
msgstr ""
#: ../../helpdesk/close_tickets.rst:11
#: ../../helpdesk/advanced/close_tickets.rst:11
msgid "To configure the feature go to :menuselection:`Helpdesk --> Settings --> Helpdesk Teams --> Edit` and enable *Ticket closing*."
msgstr ""
#: ../../helpdesk/close_tickets.rst:18
msgid "In order to designate to which stage the ticket will migrate to once it is closed, go to :menuselection:`Overview --> Tickets`."
#: ../../helpdesk/advanced/close_tickets.rst:18
msgid "In order to designate to which stage the ticket migrates to once it is closed, go to :menuselection:`Helpdesk --> Overview --> Tickets`."
msgstr ""
#: ../../helpdesk/close_tickets.rst:25
msgid "You can either create a new kanban stage or work with an existing one. For both scenarios, go to :menuselection:`Settings --> Edit Stage` and enable *Closing Stage*."
#: ../../helpdesk/advanced/close_tickets.rst:25
msgid "You can either create a new Kanban stage or work with an existing one. For both scenarios, go to :menuselection:`Helpdesk --> Settings --> Edit Stage` and enable *Closing Stage*."
msgstr ""
#: ../../helpdesk/close_tickets.rst:32
msgid "If a closing stage is not specified, by default, the ticket will be transferred to the last stage; contrarily, if you have more than one stage set as closing, the ticket will be put in the first one."
#: ../../helpdesk/advanced/close_tickets.rst:32
msgid "If a closing stage is not specified, by default, the ticket is moved to the last stage; contrarily, if you have more than one stage set as closing, the ticket is put in the first one."
msgstr ""
#: ../../helpdesk/close_tickets.rst:35
#: ../../helpdesk/advanced/close_tickets.rst:36
msgid "The Costumer Portal"
msgstr ""
#: ../../helpdesk/close_tickets.rst:37
msgid "Now, once the user logs in to his Portal, the option *Close this ticket* is available."
#: ../../helpdesk/advanced/close_tickets.rst:38
msgid "Now, once the user logs into his Portal, the option *Close this ticket* is available."
msgstr ""
#: ../../helpdesk/close_tickets.rst:44
#: ../../helpdesk/advanced/close_tickets.rst:45
msgid "Get reports on tickets closed by costumers"
msgstr ""
#: ../../helpdesk/close_tickets.rst:46
msgid "To do an analysis of the tickets that have been closed by costumers go to :menuselection:`Reporting --> Tickets --> Filters --> Add Custom filter --> Closed by partner --> Applied`."
#: ../../helpdesk/advanced/close_tickets.rst:47
msgid "To do an analysis of the tickets that have been closed by costumers go to :menuselection:`Helpdesk --> Reporting --> Tickets --> Filters --> Add Custom filter --> Closed by partner --> Applied`."
msgstr ""
#: ../../helpdesk/getting_started.rst:3
msgid "Get started with Odoo Helpdesk"
msgstr ""
#: ../../helpdesk/getting_started.rst:6
#: ../../helpdesk/overview.rst:3
msgid "Overview"
msgstr ""
#: ../../helpdesk/getting_started.rst:9
msgid "Getting started with Odoo Helpdesk"
#: ../../helpdesk/overview/forum_and_elearning.rst:3
msgid "Forum and eLearning"
msgstr ""
#: ../../helpdesk/getting_started.rst:11
msgid "Installing Odoo Helpdesk:"
#: ../../helpdesk/overview/forum_and_elearning.rst:6
msgid "Forum"
msgstr ""
#: ../../helpdesk/getting_started.rst:13
msgid "Open the Apps module, search for \"Helpdesk\", and click install"
#: ../../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 ""
#: ../../helpdesk/getting_started.rst:19
msgid "Set up Helpdesk teams"
#: ../../helpdesk/overview/forum_and_elearning.rst:14
#: ../../helpdesk/overview/forum_and_elearning.rst:52
#: ../../helpdesk/overview/ratings.rst:10
#: ../../helpdesk/timesheet_and_invoice/invoice_time.rst:11
msgid "Set up"
msgstr ""
#: ../../helpdesk/getting_started.rst:21
msgid "By default, Odoo Helpdesk comes with a team installed called \"Support\""
#: ../../helpdesk/overview/forum_and_elearning.rst:16
msgid "Go to :menuselection:`Helpdesk --> Configuration --> Helpdesk Team` and enable *Help Center*."
msgstr ""
#: ../../helpdesk/getting_started.rst:26
msgid "To modify this team, or create additional teams, select \"Configuration\" in the purple bar and select \"Settings\""
#: ../../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 ""
#: ../../helpdesk/getting_started.rst:32
msgid "Here you can create new teams, decide what team members to add to this team, how your customers can submit tickets and set up SLA policies and ratings. For the assignation method you can have tickets assigned randomly, balanced, or manually."
#: ../../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 ""
#: ../../helpdesk/getting_started.rst:38
msgid "How to set up different stages for each team"
#: ../../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 ""
#: ../../helpdesk/getting_started.rst:40
msgid "First you will need to activate the :doc:`Developer mode <../../general/developer_mode/activate>`."
#: ../../helpdesk/overview/forum_and_elearning.rst:45
msgid "eLearning"
msgstr ""
#: ../../helpdesk/getting_started.rst:42
msgid "Now, when you return to your Helpdesk module and select \"Configuration\" in the purple bar you will find additional options, like \"Stages\". Here you can create new stages and assign those stages to 1 or multiple teams allowing for customizable stages for each team!"
#: ../../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 ""
#: ../../helpdesk/getting_started.rst:48
msgid "Start receiving tickets"
#: ../../helpdesk/overview/forum_and_elearning.rst:54
msgid "Go to :menuselection:`Helpdesk --> Configuration --> Helpdesk Teams` and enable *eLearning*."
msgstr ""
#: ../../helpdesk/getting_started.rst:51
msgid "How can my customers submit tickets?"
#: ../../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 ""
#: ../../helpdesk/getting_started.rst:53
msgid "Select \"Configuration\" in the purple bar and select \"Settings\", select your Helpdesk team. Under \"Channels you will find 4 options:"
#: ../../helpdesk/overview/forum_and_elearning.rst:67
msgid "To keep track of your course statistics, go to *eLearning* and *View Course*."
msgstr ""
#: ../../helpdesk/getting_started.rst:59
msgid "Email Alias allows for customers to email the alias you choose to create a ticket. The subject line of the email with become the Subject on the ticket."
#: ../../helpdesk/overview/getting_started.rst:3
msgid "Getting Started"
msgstr ""
#: ../../helpdesk/getting_started.rst:66
msgid "Website Form allows your customer to go to yourwebsite.com/helpdesk/support-1/submit and submit a ticket via a website form - much like odoo.com/help!"
#: ../../helpdesk/overview/getting_started.rst:5
msgid "Helpdesk teams provide your customers with support to queries or errors they might encounter while using your product/service. Therefore, a successful scheme where you can organize multiple teams with their customized pipeline, visibilities settings, and ticket traceability is essential."
msgstr ""
#: ../../helpdesk/getting_started.rst:73
msgid "Live Chat allows your customers to submit a ticket via Live Chat on your website. Your customer will begin the live chat and your Live Chat Operator can create the ticket by using the command /helpdesk Subject of Ticket."
#: ../../helpdesk/overview/getting_started.rst:10
msgid "Set up teams"
msgstr ""
#: ../../helpdesk/getting_started.rst:81
msgid "The final option to submit tickets is through an API connection. View the documentation `here <https://www.odoo.com/documentation/13.0/webservices/odoo.html>`_."
#: ../../helpdesk/overview/getting_started.rst:12
msgid "To modify or create teams, go to :menuselection:`Helpdesk --> Configuration --> Helpdesk Teams`."
msgstr ""
#: ../../helpdesk/getting_started.rst:85
msgid "Tickets have been created, now what?"
#: ../../helpdesk/overview/getting_started.rst:14
msgid "Setting up multiple teams allows you to group tickets by your channels (example: BE/US), or by your support services' types (example: IT, accounting, admin, etc.)."
msgstr ""
#: ../../helpdesk/getting_started.rst:87
msgid "Now your employees can start working on them! If you have selecting a manual assignation method then your employees will need to assign themselves to tickets using the \"Assign To Me\" button on the top left of a ticket or by adding themselves to the \"Assigned to\" field."
#: ../../helpdesk/overview/getting_started.rst:21
msgid "Teams productivity and visibility"
msgstr ""
#: ../../helpdesk/getting_started.rst:95
msgid "If you have selected \"Random\" or \"Balanced\" assignation method, your tickets will be assigned to a member of that Helpdesk team."
#: ../../helpdesk/overview/getting_started.rst:23
msgid "Teams can have individual *Assignment Methods* to ensure that tickets get redirected to the right person:"
msgstr ""
#: ../../helpdesk/getting_started.rst:98
msgid "From there they will begin working on resolving the tickets! When they are completed, they will move the ticket to the solved stage."
#: ../../helpdesk/overview/getting_started.rst:26
msgid "*Manually*: tickets are manually assigned, allowing employees to manage their own workload and target tickets they are experts at;"
msgstr ""
#: ../../helpdesk/getting_started.rst:102
msgid "How do I mark this ticket as urgent?"
#: ../../helpdesk/overview/getting_started.rst:28
msgid "*Random*: tickets are randomly assigned and everyone gets the same amount. This method ensures that all tickets are handled as the assignment happens automatically;"
msgstr ""
#: ../../helpdesk/getting_started.rst:104
msgid "On your tickets you will see stars. You can determine how urgent a ticket is but selecting one or more stars on the ticket. You can do this in the Kanban view or on the ticket form."
#: ../../helpdesk/overview/getting_started.rst:30
msgid "*Balanced*: tickets are assigned to the person with the least amount of tickets so that everyone fairly gets the same amount. Thereby, you ensure that all tickets get to be taken care of."
msgstr ""
#: ../../helpdesk/getting_started.rst:111
msgid "To set up a Service Level Agreement Policy for your employees, first activate the setting under \"Settings\""
#: ../../helpdesk/overview/getting_started.rst:40
msgid "For the *Random* and *Balanced* assignment methods, you can set the *Team Members* among whom tickets are assigned. Leave the field empty to include all employees (with the proper access rights)."
msgstr ""
#: ../../helpdesk/getting_started.rst:117
msgid "From here, select \"Configure SLA Policies\" and click \"Create\"."
#: ../../helpdesk/overview/getting_started.rst:43
msgid "The *Team Visibility* feature allows you to specify who can see and access the teams tickets. Therefore, tickets with sensible information are only seen by the right people. Leave the field empty to include all employees (with the proper access rights)."
msgstr ""
#: ../../helpdesk/getting_started.rst:119
msgid "You will fill in information like the Helpdesk team, what the minimum priority is on the ticket (the stars) and the targets for the ticket."
#: ../../helpdesk/overview/getting_started.rst:46
msgid "Set up stages and share it among teams"
msgstr ""
#: ../../helpdesk/getting_started.rst:126
msgid "What if a ticket is blocked or is ready to be worked on?"
#: ../../helpdesk/overview/getting_started.rst:48
msgid "To set up stages, go to :menuselection:`Helpdesk --> Configuration --> Stages`. Then, create and/or edit stages as you need and set specific teams to use certain stages under *Team*."
msgstr ""
#: ../../helpdesk/getting_started.rst:128
msgid "If a ticket cannot be resolved or is blocked, you can adjust the \"Kanban State\" on the ticket. You have 3 options:"
#: ../../helpdesk/overview/getting_started.rst:55
msgid "Stages can be shared between one or multiple teams, allowing you to adapt the pipeline to your individual needs. They also apply a visibility and access rule, as other teams are not able to see or use the stage."
msgstr ""
#: ../../helpdesk/getting_started.rst:131
msgid "Grey - Normal State"
#: ../../helpdesk/overview/getting_started.rst:64
msgid ":doc:`../../general/odoo_basics/add_user`"
msgstr ""
#: ../../helpdesk/getting_started.rst:133
msgid "Red - Blocked"
#: ../../helpdesk/overview/ratings.rst:3
msgid "Ratings"
msgstr ""
#: ../../helpdesk/getting_started.rst:135
msgid "Green - Ready for next stage"
#: ../../helpdesk/overview/ratings.rst:5
msgid "Allow customers to rate their experience with your helpdesk teams to strengthen your credibility and gain their trust. Reviews can also influence a customers decision and open space for feedback that can help you improve the quality of your services."
msgstr ""
#: ../../helpdesk/getting_started.rst:137
msgid "Like the urgency stars you can adjust the state in the Kanban or on the Ticket form."
#: ../../helpdesk/overview/ratings.rst:12
msgid "Go to :menuselection:`Helpdesk --> Configuration --> Helpdesk Teams` and enable *Ratings on tickets*. The feature automatically adds a default email template on the non-folded *closing stage(s)* of that team."
msgstr ""
#: ../../helpdesk/getting_started.rst:144
msgid "How can my employees log time against a ticket?"
#: ../../helpdesk/overview/ratings.rst:21
msgid "To edit the email template and the stage(s) set as the closing ones, go to the Kanban view of your helpdesk team and click on *Settings*, then on *Edit Stage*."
msgstr ""
#: ../../helpdesk/getting_started.rst:146
msgid "First, head over to \"Settings\" and select the option for \"Timesheet on Ticket\". You will see a field appear where you can select the project the timesheets will log against."
#: ../../helpdesk/overview/ratings.rst:28
msgid "Now, once a ticket reaches the stage(s) designated as the *Closing Stage*, an email is sent to the customer."
msgstr ""
#: ../../helpdesk/getting_started.rst:153
msgid "Now that you have selected a project, you can save. If you move back to your tickets, you will see a new tab called \"Timesheets\""
#: ../../helpdesk/overview/ratings.rst:35
msgid "Ratings can be seen on the :doc:`chatter <../../project/tasks/collaborate>` of each ticket, under the *See Customer Satisfaction* link on the main dashboard, and through *Reporting*."
msgstr ""
#: ../../helpdesk/getting_started.rst:159
msgid "Here you employees can add a line to add work they have done for this ticket."
#: ../../helpdesk/overview/ratings.rst:39
msgid "Ratings visible on the customer portal"
msgstr ""
#: ../../helpdesk/getting_started.rst:163
msgid "How to allow your customers to rate the service they received"
#: ../../helpdesk/overview/ratings.rst:41
msgid "Go to :menuselection:`Helpdesk --> Configuration --> Helpdesk Teams` and enable *Display Rating on Customer Portal*. Now, by clicking on the helpdesk teams name on their ticket, customers can see its ratings."
msgstr ""
#: ../../helpdesk/getting_started.rst:165
msgid "First, you will need to activate the ratings setting under \"Settings\""
#: ../../helpdesk/overview/ratings.rst:51
msgid ":doc:`../../portal/my_odoo_portal`"
msgstr ""
#: ../../helpdesk/getting_started.rst:170
msgid "Now, when a ticket is moved to its solved or completed stage, it will send an email to the customer asking how their service went."
#: ../../helpdesk/overview/ratings.rst:52
#: ../../helpdesk/overview/receiving_tickets.rst:88
#: ../../helpdesk/overview/sla.rst:47
msgid ":doc:`../advanced/close_tickets`"
msgstr ""
#: ../../helpdesk/invoice_time.rst:3
msgid "Record and invoice time for tickets"
#: ../../helpdesk/overview/receiving_tickets.rst:3
msgid "Start Receiving Tickets"
msgstr ""
#: ../../helpdesk/invoice_time.rst:5
msgid "You may have service contracts with your clients to provide them assistance in case of a problem. For this purpose, Odoo will help you record the time spent fixing the issue and most importantly, to invoice it to your clients."
#: ../../helpdesk/overview/receiving_tickets.rst:5
msgid "Offering a variety of channels from where your customers can contact you grants them flexibility and the right to choose the best one for themselves. And, in order to make sure inquiries across all channels get addressed, it is essential to have a solution where all interactions come in one place."
msgstr ""
#: ../../helpdesk/invoice_time.rst:11
msgid "The modules needed"
#: ../../helpdesk/overview/receiving_tickets.rst:11
msgid "Channels options to submit tickets"
msgstr ""
#: ../../helpdesk/invoice_time.rst:13
msgid "In order to record and invoice time for tickets, the following modules are needed : Helpdesk, Project, Timesheets, Sales. If you are missing one of them, go to the Apps module, search for it and then click on *Install*."
#: ../../helpdesk/overview/receiving_tickets.rst:13
msgid "Go to :menuselection:`Helpdesk --> Configuration --> Helpdesk Teams`, and enable the following features as you want them to be available to your users."
msgstr ""
#: ../../helpdesk/invoice_time.rst:19
msgid "Get started to offer the helpdesk service"
#: ../../helpdesk/overview/receiving_tickets.rst:21
msgid "Email Alias"
msgstr ""
#: ../../helpdesk/invoice_time.rst:22
msgid "Step 1 : start a helpdesk project"
#: ../../helpdesk/overview/receiving_tickets.rst:24
msgid "Let your customers submit tickets by sending an email to your support email address. The subject line of the email becomes the title of the ticket and the content is shown in the Chatter."
msgstr ""
#: ../../helpdesk/invoice_time.rst:24
msgid "To start a dedicated project for the helpdesk service, first go to :menuselection:`Project --> Configuration --> Settings` and make sure that the *Timesheets* feature is activated."
#: ../../helpdesk/overview/receiving_tickets.rst:26
msgid "Select *Configure domain name* to be redirected to *Settings* and, from there, enable *External Email Servers* to determine or change your *Alias Domain*."
msgstr ""
#: ../../helpdesk/invoice_time.rst:31
msgid "Then, go to your dashboard, create the new project and allow timesheets for it."
#: ../../helpdesk/overview/receiving_tickets.rst:35
msgid "Using your own email server is required to send and receive emails in Odoo Community and Enterprise. Online users benefit from a ready-to-use email server."
msgstr ""
#: ../../helpdesk/invoice_time.rst:35
msgid "Step 2 : gather a helpdesk team"
#: ../../helpdesk/overview/receiving_tickets.rst:39
msgid "Website Form"
msgstr ""
#: ../../helpdesk/invoice_time.rst:37
msgid "To set a team in charge of the helpdesk, go to :menuselection:`Helpdesk --> Configuration --> Helpdesk Teams` and create a new team or select an existing one. On the form, tick the box in front of *Timesheet on Ticket* to activate the feature. Make sure to select the helpdesk project you have previously created as well."
#: ../../helpdesk/overview/receiving_tickets.rst:41
msgid "Allow your customers to submit a ticket by filling in a form through your website."
msgstr ""
#: ../../helpdesk/invoice_time.rst:47
msgid "Step 3 : launch the helpdesk service"
#: ../../helpdesk/overview/receiving_tickets.rst:42
msgid "Once the feature is activated, get redirected to your website by clicking on *Go to Website*."
msgstr ""
#: ../../helpdesk/invoice_time.rst:49
msgid "Finally, to launch the new helpdesk service, first go to :menuselection:`Sales --> Configuration --> Settings` and make sure that the *Units of Measure* feature is activated."
#: ../../helpdesk/overview/receiving_tickets.rst:49
msgid "From the website page customize the form as you like. Then, publish it by clicking on *Unpublished*."
msgstr ""
#: ../../helpdesk/invoice_time.rst:56
msgid "Then, go to :menuselection:`Products --> Products` and create a new one. Make sure that the product is set as a service."
#: ../../helpdesk/overview/receiving_tickets.rst:56
msgid "Live Chat"
msgstr ""
#: ../../helpdesk/invoice_time.rst:63
msgid "Here, we suggest that you set the *Unit of Measure* as *Hour(s)*, but any unit will do."
#: ../../helpdesk/overview/receiving_tickets.rst:59
msgid "Through live interactions with your website visitors, helpdesk tickets can be instantly created and redirected to the right person."
msgstr ""
#: ../../helpdesk/invoice_time.rst:66
msgid "Finally, select the invoicing management you would like to have under the *Sales* tab of the product form. Here, we recommend the following configuration :"
#: ../../helpdesk/overview/receiving_tickets.rst:61
msgid "Click on your helpdesk team's name - for the example below: *Customer Care* - and :doc:`set up your channel <../../livechat/overview/get_started>`."
msgstr ""
#: ../../helpdesk/invoice_time.rst:73
msgid "Now, you are ready to start receiving tickets !"
#: ../../helpdesk/overview/receiving_tickets.rst:68
msgid "Now, your operators can create tickets by using the :doc:`command <../../livechat/overview/responses>` */helpdesk (subject_of_ticket)*."
msgstr ""
#: ../../helpdesk/invoice_time.rst:76
msgid "Solve issues and record time spent"
#: ../../helpdesk/overview/receiving_tickets.rst:72
msgid "Prioritize tickets"
msgstr ""
#: ../../helpdesk/invoice_time.rst:79
msgid "Step 1 : place an order"
#: ../../helpdesk/overview/receiving_tickets.rst:74
msgid "Use the stars to prioritize your tickets. The most urgent ones appear at the top of your list on the Kanban view."
msgstr ""
#: ../../helpdesk/invoice_time.rst:81
msgid "You are now in the Helpdesk module and you have just received a ticket from a client. To place a new order, go to :menuselection:`Sales --> Orders --> Orders` and create one for the help desk service product you have previously recorded. Set the number of hours needed to assist the client and confirm the sale."
#: ../../helpdesk/overview/receiving_tickets.rst:77
msgid "1 star = *Low priority*"
msgstr ""
#: ../../helpdesk/invoice_time.rst:91
msgid "Step 2 : link the task to the ticket"
#: ../../helpdesk/overview/receiving_tickets.rst:78
msgid "2 stars = *High priority*"
msgstr ""
#: ../../helpdesk/invoice_time.rst:93
msgid "If you access the dedicated helpdesk project, you will notice that a new task has automatically been generated with the order. To link this task with the client ticket, go to the Helpdesk module, access the ticket in question and select the task on its form."
#: ../../helpdesk/overview/receiving_tickets.rst:79
msgid "3 stars = *Urgent*"
msgstr ""
#: ../../helpdesk/invoice_time.rst:102
msgid "Step 3 : record the time spent to help the client"
#: ../../helpdesk/overview/receiving_tickets.rst:87
#: ../../helpdesk/overview/reports.rst:60
msgid ":doc:`sla`"
msgstr ""
#: ../../helpdesk/invoice_time.rst:104
msgid "The job is done and the client's issue is sorted out. To record the hours performed for this task, go back to the ticket form and add them under the *Timesheets* tab."
#: ../../helpdesk/overview/receiving_tickets.rst:89
msgid ":doc:`../../discuss/advanced/email_servers`"
msgstr ""
#: ../../helpdesk/invoice_time.rst:112
msgid "The hours recorded on the ticket will also automatically appear in the Timesheet module and on the dedicated task."
#: ../../helpdesk/overview/reports.rst:3
msgid "Reports for a Better Support"
msgstr ""
#: ../../helpdesk/invoice_time.rst:116
msgid "Step 4 : invoice the client"
#: ../../helpdesk/overview/reports.rst:5
msgid "An efficient customer service solution should have a built-in reporting option. Reports allow you to track trends, identify areas for improvement, manage employees workloads and, most importantly, meet your customers expectations."
msgstr ""
#: ../../helpdesk/invoice_time.rst:118
msgid "To invoice the client, go back to the Sales module and select the order that had been placed. Notice that the hours recorded on the ticket form now appear as the delivered quantity."
#: ../../helpdesk/overview/reports.rst:10
msgid "Cases"
msgstr ""
#: ../../helpdesk/invoice_time.rst:125
msgid "All that is left to do, is to create the invoice from the order and then validate it. Now you just have to wait for the client's payment !"
#: ../../helpdesk/overview/reports.rst:12
msgid "Some examples of the reports Odoo Helpdesk can generate include:"
msgstr ""
#: ../../helpdesk/reinvoice_from_project.rst:3
msgid "Turn helpdesk hours into invoices directly from a project task"
#: ../../helpdesk/overview/reports.rst:14
msgid "The number of tickets *grouped by* team and ticket type."
msgstr ""
#: ../../helpdesk/reinvoice_from_project.rst:5
#: ../../helpdesk/overview/reports.rst:17
msgid "In this manner, you are able to evaluate which ticket types have been the most frequent ones, plus the workload of your teams."
msgstr ""
#: ../../helpdesk/overview/reports.rst:19
msgid "Apply *Time Ranges* if you would like to make comparisons to a *Previous Period* or a *Previous Year*."
msgstr ""
#: ../../helpdesk/overview/reports.rst:25
msgid "The number of tickets closed per day, per team."
msgstr ""
#: ../../helpdesk/overview/reports.rst:27
msgid "Get an overview of how many requests each team is closing per day in order to measure their performance. Identify productivity levels to understand how many requests they are able to handle."
msgstr ""
#: ../../helpdesk/overview/reports.rst:35
msgid "Filter it by *Assignee* to see Key Performance Indicators (KPI) per agent."
msgstr ""
#: ../../helpdesk/overview/reports.rst:37
msgid "The number of hours tickets are taking to be solved, grouped by team and ticket type."
msgstr ""
#: ../../helpdesk/overview/reports.rst:39
msgid "Check if your expectations are met by *measuring* the *Time to close (hours)*. Your customers not only expect fast responses but they also want their issues to be handled quickly."
msgstr ""
#: ../../helpdesk/overview/reports.rst:48
msgid "Save filters"
msgstr ""
#: ../../helpdesk/overview/reports.rst:50
msgid "Save the filters you use the most and avoid having to reconstruct them every time they are needed. To do so, set the groups, filters, and measures needed. Then, go to *Favorites*."
msgstr ""
#: ../../helpdesk/overview/reports.rst:59
msgid ":doc:`receiving_tickets`"
msgstr ""
#: ../../helpdesk/overview/sla.rst:3
msgid "Service Level Agreements (SLA)"
msgstr ""
#: ../../helpdesk/overview/sla.rst:5
msgid "Service Level Agreements (SLA) are commitments you make with your customers to outline how a service is delivered. It bolsters trust between you and your customers as it makes clear what needs to be done, to what standard, and when."
msgstr ""
#: ../../helpdesk/overview/sla.rst:10
msgid "Create your policies"
msgstr ""
#: ../../helpdesk/overview/sla.rst:13
msgid "First, enable the feature on the settings of the team you would like policies to be applied, going to :menuselection:`Helpdesk --> Configuration --> Helpdesk Teams`."
msgstr ""
#: ../../helpdesk/overview/sla.rst:15
msgid "Create your policies through the teams settings page or go to :menuselection:`Helpdesk --> Configuration --> SLA Policies`."
msgstr ""
#: ../../helpdesk/overview/sla.rst:23
msgid "Choose to which **Team** the policy is relevant and the **Minimum Priority** a ticket needs to have for the policy to be applied."
msgstr ""
#: ../../helpdesk/overview/sla.rst:27
msgid "**Target** is the stage a ticket needs to reach within the period defined to satisfy the SLA. The period is based on the tickets creation date, and a deadline is set on the tickets form once it matches an SLA policy rule. If a ticket has more than one policy applied to it, the closest deadline of all SLAs is the one considered."
msgstr ""
#: ../../helpdesk/overview/sla.rst:29
msgid "When a ticket has satisfied an SLA policy, the SLA tag appears in green and the deadline field is not shown anymore."
msgstr ""
#: ../../helpdesk/overview/sla.rst:37
msgid "SLA Analysis"
msgstr ""
#: ../../helpdesk/overview/sla.rst:39
msgid "Go to :menuselection:`Helpdesk --> Reporting --> SLA Status Analysis`. Apply *Filters* and *Group by* to identify tickets that should be prioritized and keep track of upcoming deadlines."
msgstr ""
#: ../../helpdesk/timesheet_and_invoice.rst:3
msgid "Timesheet and Invoice"
msgstr ""
#: ../../helpdesk/timesheet_and_invoice/invoice_time.rst:3
msgid "Invoice Time Spent on Tickets (Prepaid Support Services)"
msgstr ""
#: ../../helpdesk/timesheet_and_invoice/invoice_time.rst:5
msgid "Have the option to work with prepaid support services, meaning that a sales order and a corresponding invoice are issued and, once the service is done, you can deduct the time spent. Odoo allows it to happen because the applications are fully integrated, resulting in faster responses to your customer needs."
msgstr ""
#: ../../helpdesk/timesheet_and_invoice/invoice_time.rst:14
msgid "Step 1: Set up a helpdesk team"
msgstr ""
#: ../../helpdesk/timesheet_and_invoice/invoice_time.rst:17
msgid "Go to :menuselection:`Helpdesk --> Configuration --> Helpdesk Teams`, create or edit an existing team, and enable *Timesheet on Ticket* and *Time Reinvoicing*."
msgstr ""
#: ../../helpdesk/timesheet_and_invoice/invoice_time.rst:20
msgid "Select or create a project under *Timesheet on Ticket*. The selected/created is the one at which employees timesheet on by default. However, it can be ultimately modified on each ticket."
msgstr ""
#: ../../helpdesk/timesheet_and_invoice/invoice_time.rst:28
msgid "Step 2: Set up a service"
msgstr ""
#: ../../helpdesk/timesheet_and_invoice/invoice_time.rst:31
msgid "Go to :menuselection:`Sales --> Configuration --> Settings` and enable *Units of Measure* to optionally be able to choose *hours* (for example) as the unit of measure of your service."
msgstr ""
#: ../../helpdesk/timesheet_and_invoice/invoice_time.rst:33
msgid "Then, go to :menuselection:`Sales --> Products --> Products`, create or edit an existing one, and set its *Product Type* as *Service*."
msgstr ""
#: ../../helpdesk/timesheet_and_invoice/invoice_time.rst:40
msgid "Now, select the invoicing management you would like to have under the *Sales* tab. We recommend the following configuration:"
msgstr ""
#: ../../helpdesk/timesheet_and_invoice/invoice_time.rst:47
msgid "This configuration ensures that the customer is invoiced by the number of hours predicted in the sales order, meaning that less or extra hours recorded are not taken into account. It also ensures that every time a sales order is confirmed, a new task is created under the right project, automating the process."
msgstr ""
#: ../../helpdesk/timesheet_and_invoice/invoice_time.rst:53
msgid "We recommend setting up a specific project, as it was done for this flow example. The important thing to remember is that the sales order item needs to be set on the corresponding project or task, in order to reinvoice the time spent on a ticket."
msgstr ""
#: ../../helpdesk/timesheet_and_invoice/invoice_time.rst:58
msgid "Prevision an invoice and record time"
msgstr ""
#: ../../helpdesk/timesheet_and_invoice/invoice_time.rst:61
msgid "Step 1: Place an order"
msgstr ""
#: ../../helpdesk/timesheet_and_invoice/invoice_time.rst:63
msgid "Go to :menuselection:`Sales --> Orders --> Orders` and create one for the helpdesk service product you have previously set up, with the customer who needs the ticket to be opened. Set the number of hours needed to assist the customer and *Confirm* the order."
msgstr ""
#: ../../helpdesk/timesheet_and_invoice/invoice_time.rst:72
msgid "Step 2: Invoice the customer"
msgstr ""
#: ../../helpdesk/timesheet_and_invoice/invoice_time.rst:74
msgid "In *Sales*, select the respective sales order to *Create Invoice*."
msgstr ""
#: ../../helpdesk/timesheet_and_invoice/invoice_time.rst:82
msgid "Step 3: Link the task to the ticket"
msgstr ""
#: ../../helpdesk/timesheet_and_invoice/invoice_time.rst:84
msgid "Now, in *Helpdesk*, create or edit the respective ticket and link it to the task created by the confirmation of the sales order."
msgstr ""
#: ../../helpdesk/timesheet_and_invoice/invoice_time.rst:92
msgid "Step 4: Record the time spent"
msgstr ""
#: ../../helpdesk/timesheet_and_invoice/invoice_time.rst:94
msgid "Still on the respective helpdesk ticket, record the hours performed under the *Timesheets* tab."
msgstr ""
#: ../../helpdesk/timesheet_and_invoice/invoice_time.rst:100
msgid "Note that the hours recorded on the ticket form are shown on the *Delivered* column in the sales order."
msgstr ""
#: ../../helpdesk/timesheet_and_invoice/invoice_time.rst:108
msgid "Hours recorded on the ticket are automatically shown in *Timesheets* and on the dedicated task."
msgstr ""
#: ../../helpdesk/timesheet_and_invoice/invoice_time.rst:111
msgid ":doc:`reinvoice_from_project`"
msgstr ""
#: ../../helpdesk/timesheet_and_invoice/invoice_time.rst:112
msgid ":doc:`../../inventory/management/products/uom`"
msgstr ""
#: ../../helpdesk/timesheet_and_invoice/reinvoice_from_project.rst:3
msgid "Invoice Time Spent on Tickets (Postpaid Support Services)"
msgstr ""
#: ../../helpdesk/timesheet_and_invoice/reinvoice_from_project.rst:5
msgid "Directly pull the billable time you have tracked on your helpdesk tickets into sales orders and invoices through a project task. It gives you more control over what you charge your client, and it is more efficient."
msgstr ""
#: ../../helpdesk/reinvoice_from_project.rst:10
#: ../../helpdesk/timesheet_and_invoice/reinvoice_from_project.rst:10
msgid "Configuration"
msgstr ""
#: ../../helpdesk/reinvoice_from_project.rst:12
msgid "Go to :menuselection:`Helpdesk --> Configuration --> Helpdesk team --> Edit` and enable the options *Timesheet on Ticket* and *Time Reinvoicing*. Under *Timesheet on Ticket*, choose the *Project* to which the tickets (and timesheets) will be linked by default. Open its *External link* to enable the feature *Bill from tasks*."
#: ../../helpdesk/timesheet_and_invoice/reinvoice_from_project.rst:13
msgid "Go to :menuselection:`Helpdesk --> Configuration --> Helpdesk team --> Edit` and enable the options *Timesheet on Ticket* and *Time Reinvoicing*."
msgstr ""
#: ../../helpdesk/reinvoice_from_project.rst:22
#: ../../helpdesk/timesheet_and_invoice/reinvoice_from_project.rst:15
msgid "Under *Timesheet on Ticket*, choose the *Project* to which tickets (and timesheets) will be linked by default. Open its *External link* to enable the feature *Bill from tasks*."
msgstr ""
#: ../../helpdesk/timesheet_and_invoice/reinvoice_from_project.rst:22
msgid "Create a sales order and an invoice"
msgstr ""
#: ../../helpdesk/reinvoice_from_project.rst:24
msgid "Now, once you added the time you spent on the helpdesk ticket, under the *Timesheets* tab, access the task clicking on its name."
#: ../../helpdesk/timesheet_and_invoice/reinvoice_from_project.rst:24
msgid "Now, once you have recorded the time you spent on the helpdesk ticket, under the *Timesheets* tab, access the task clicking on its name."
msgstr ""
#: ../../helpdesk/reinvoice_from_project.rst:31
#: ../../helpdesk/timesheet_and_invoice/reinvoice_from_project.rst:31
msgid "*Create Sales Order* and proceed to create the invoice."
msgstr ""

File diff suppressed because it is too large Load Diff

View File

@ -8,7 +8,7 @@ msgid ""
msgstr ""
"Project-Id-Version: Odoo 13.0\n"
"Report-Msgid-Bugs-To: \n"
"POT-Creation-Date: 2020-01-16 09:46+0100\n"
"POT-Creation-Date: 2020-09-24 12:02+0200\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"
@ -53,42 +53,50 @@ msgid "Power on the IoT Box."
msgstr ""
#: ../../iot/config/connect.rst:28
msgid "Then click on the Scan button."
msgid "Read the Pairing Code from a screen or a receipt printer connected to the IoT Box."
msgstr ""
#: ../../iot/config/connect.rst:34
#: ../../iot/config/connect.rst:32
msgid "Input the Pairing Code and click on the Pair button."
msgstr ""
#: ../../iot/config/connect.rst:35
msgid "Recent changes in modern web browsers forced us to modify the connection wizard. If your screen is different from the screenshots, make sure that the ``iot_pairing`` module is installed."
msgstr ""
#: ../../iot/config/connect.rst:40
msgid "WiFi Connection"
msgstr ""
#: ../../iot/config/connect.rst:36
#: ../../iot/config/connect.rst:42
msgid "Power on the IoT Box"
msgstr ""
#: ../../iot/config/connect.rst:38
#: ../../iot/config/connect.rst:44
msgid "Copy the token"
msgstr ""
#: ../../iot/config/connect.rst:43
#: ../../iot/config/connect.rst:48
msgid "Connect to the IoT Box WiFi Network (make sure there is no ethernet cable plugged in your computer)."
msgstr ""
#: ../../iot/config/connect.rst:49
#: ../../iot/config/connect.rst:53
msgid "You will be redirected to the IoT Box Homepage (if it doesn't work, connect to the IP address of the box). Give a name to your IoT Box (not required) and paste the token, then click on next."
msgstr ""
#: ../../iot/config/connect.rst:57
#: ../../iot/config/connect.rst:60
msgid "If you are on Runbot, do not forget to add the -all or -base in the token (e.g. this token **http://375228-saas-11-5-iot-f3f920.runbot16.odoo.com\\|4957098401** should become **http://375228-saas-11-5-iot-f3f920-all.runbot16.odoo.com\\|4957098401**)."
msgstr ""
#: ../../iot/config/connect.rst:63
#: ../../iot/config/connect.rst:66
msgid "Choose the WiFi network you want to connect with (enter the password if there is one) and click on Submit. Wait a few seconds before being redirected to your database."
msgstr ""
#: ../../iot/config/connect.rst:70
#: ../../iot/config/connect.rst:72
msgid "You should now see the IoT Box."
msgstr ""
#: ../../iot/config/connect.rst:76
#: ../../iot/config/connect.rst:78
msgid "IoT Box Schema"
msgstr ""
@ -137,7 +145,7 @@ msgid "To check it, go to your database and verify if your database address star
msgstr ""
#: ../../iot/config/iot_notfound.rst:19
msgid "If your IoT Box image is from an earlier version, then you will have to reflash the SD card of your IoT Box to update the image (the latest image can be found `here <http://nightly/odoo.com>`__)."
msgid "If your IoT Box image is from an earlier version, then you will have to reflash the SD card of your IoT Box to update the image (the latest image can be found `here <http://nightly.odoo.com/master/posbox/iotbox/>`__)."
msgstr ""
#: ../../iot/config/iot_notfound.rst:24

View File

@ -8,7 +8,7 @@ msgid ""
msgstr ""
"Project-Id-Version: Odoo 13.0\n"
"Report-Msgid-Bugs-To: \n"
"POT-Creation-Date: 2019-10-03 11:39+0200\n"
"POT-Creation-Date: 2020-09-24 12:02+0200\n"
"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
"Language-Team: LANGUAGE <LL@li.org>\n"
@ -16,127 +16,197 @@ msgstr ""
"Content-Type: text/plain; charset=UTF-8\n"
"Content-Transfer-Encoding: 8bit\n"
#: ../../livechat/livechat.rst:5
msgid "Live Chat"
#: ../../livechat/overview.rst:3
msgid "Overview"
msgstr ""
#: ../../livechat/livechat.rst:8
msgid "Chat in real time with website visitors"
#: ../../livechat/overview/get_started.rst:3
msgid "Get Started with Live Chat"
msgstr ""
#: ../../livechat/livechat.rst:10
msgid "With Odoo Live Chat, you can establish a direct contact with your website visitors. A simple dialog box will be available on their screen and will allow them to get in touch with one of your sales representatives. This way, you can easily turn prospects into potential business opportunities. You will also be able to provide assistance to your customers. Overall, this is the perfect tool to improve customer satisfaction."
#: ../../livechat/overview/get_started.rst:5
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 ""
#: ../../livechat/livechat.rst:19
msgid "Configuration"
#: ../../livechat/overview/get_started.rst:10
msgid "Set up"
msgstr ""
#: ../../livechat/livechat.rst:21
msgid "To get the Live Chat feature, open the Apps module, search for \"Live Chat\" and then click on install."
#: ../../livechat/overview/get_started.rst:12
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`."
msgstr ""
#: ../../livechat/livechat.rst:27
msgid "The Live Chat module provides you a direct access to your channels. There, operators can easily join and leave the chat."
#: ../../livechat/overview/get_started.rst:21
msgid "Select the channel to be linked to your website or create one on the fly."
msgstr ""
#: ../../livechat/livechat.rst:34
msgid "Add the live chat to an Odoo website"
#: ../../livechat/overview/get_started.rst:27
msgid "For both scenarios, under:"
msgstr ""
#: ../../livechat/livechat.rst:36
msgid "If your website was created with Odoo, then the live chat is automatically added to it. All that is left to do, is to go to :menuselection:`Website --> Configuration --> Settings` to select the channel to be linked to the website."
#: ../../livechat/overview/get_started.rst:30
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 ""
#: ../../livechat/livechat.rst:45
msgid "Add the live chat to an external website"
#: ../../livechat/overview/get_started.rst:33
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."
msgstr ""
#: ../../livechat/livechat.rst:47
msgid "If your website was not created with Odoo, go to the Live Chat module and then select the channel to be linked. There, you can simply copy paste the code available into your website. A specific url you can send to customers or suppliers for them to access the live chat is also provided."
#: ../../livechat/overview/get_started.rst:36
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."
msgstr ""
#: ../../livechat/livechat.rst:54
msgid "Hide / display the live chat according to rules"
#: ../../livechat/overview/get_started.rst:43
msgid "GeoIP, which refers to the process of finding a computer terminals geographical location by its IP address, must be installed on your server. Otherwise, under *Channel Rules*, countries are not taken into account."
msgstr ""
#: ../../livechat/livechat.rst:56
msgid "Rules for the live chat can be defined on the channel form. For instance, you can choose to display the chat in the countries you speak the language of. On the contrary, you are able to hide the chat in countries your company does not sell in. If you select *Auto popup*, you can also set the length of time it takes for the chat to appear."
#: ../../livechat/overview/get_started.rst:48
msgid "External options"
msgstr ""
#: ../../livechat/livechat.rst:66
msgid "Prepare automatic messages"
#: ../../livechat/overview/get_started.rst:51
msgid "If your website was not created with Odoo, you can find the code to be added to your own, under the *Widget* tab."
msgstr ""
#: ../../livechat/livechat.rst:68
msgid "On the channel form, in the *Options* section, several messages can be typed to appear automatically on the chat. This will entice visitors to reach you through the live chat."
#: ../../livechat/overview/get_started.rst:52
msgid "Odoo also offers an URL you can send to users so they can have access to a single live chat page."
msgstr ""
#: ../../livechat/livechat.rst:76
msgid "Start chatting with customers"
#: ../../livechat/overview/get_started.rst:59
msgid "Managing chat requests"
msgstr ""
#: ../../livechat/livechat.rst:78
msgid "In order to start chatting with customers, first make sure that the channel is published on your website. To do so, select *Unpublished on Website* on the top right corner of the channel form to toggle the *Published* setting. Then, the live chat can begin once an operator has joined the channel."
#: ../../livechat/overview/get_started.rst:61
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 ""
#: ../../livechat/livechat.rst:88
msgid "If no operator is available and/or if the channel is unpublished on the website, then the live chat button will not appear to visitors."
#: ../../livechat/overview/get_started.rst:69
msgid "Conversations are dispatched based on the current workload of the online operators."
msgstr ""
#: ../../livechat/livechat.rst:92
msgid "Conversations initiated by visitors also appear in the Discuss module in addition to popping up as a direct message. Therefore, inquiries can be answered wherever you are in Odoo."
#: ../../livechat/overview/get_started.rst:72
msgid "Leave or join a channel"
msgstr ""
#: ../../livechat/livechat.rst:96
msgid "If there are several operators who have all joined a channel, the system will dispatch visitor sessions randomly between them."
#: ../../livechat/overview/get_started.rst:74
msgid "Go to :menuselection:`Website --> Configuration --> Settings`, access your channel under *Live Chat*, and *Join Channel* or *Leave Channel*."
msgstr ""
#: ../../livechat/livechat.rst:100
#: ../../livechat/overview/get_started.rst:82
#: ../../livechat/overview/responses.rst:48
msgid ":doc:`ratings`"
msgstr ""
#: ../../livechat/overview/get_started.rst:83
#: ../../livechat/overview/ratings.rst:45
msgid ":doc:`responses`"
msgstr ""
#: ../../livechat/overview/ratings.rst:3
msgid "Ratings"
msgstr ""
#: ../../livechat/overview/ratings.rst:5
msgid "Giving users the opportunity to rate their interactions can help you improving the experience you offer. That means staying on top of your customers' needs, besides keeping track of your operators performances."
msgstr ""
#: ../../livechat/overview/ratings.rst:10
msgid "Customer Rating"
msgstr ""
#: ../../livechat/overview/ratings.rst:12
msgid "Once the user chooses to close the chat window, he can rate his interaction."
msgstr ""
#: ../../livechat/overview/ratings.rst:14
msgid "If the user is *Not satisfied* or *Highly dissatisfied*, a field allowing for an explanation is shown."
msgstr ""
#: ../../livechat/overview/ratings.rst:15
msgid "A copy of the conversation can also be sent by email."
msgstr ""
#: ../../livechat/overview/ratings.rst:22
msgid "The rating is shown on the chat window itself for the operator."
msgstr ""
#: ../../livechat/overview/ratings.rst:28
msgid "And under :menuselection:`Report --> Customer Ratings`."
msgstr ""
#: ../../livechat/overview/ratings.rst:35
msgid "Make the rating public"
msgstr ""
#: ../../livechat/overview/ratings.rst:37
msgid "Go to :menuselection:`Website --> Configuration --> Settings`, access your channel form, click on *Go to Website* and on *Unpublished*, to publish the rating of that channel on your website."
msgstr ""
#: ../../livechat/overview/responses.rst:3
msgid "Commands and Canned Responses"
msgstr ""
#: ../../livechat/overview/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 ""
#: ../../livechat/overview/responses.rst:9
msgid "Use commands"
msgstr ""
#: ../../livechat/livechat.rst:102
msgid "Commands are useful shortcuts for completing certain actions or to access information you might need. To use this feature, simply type the commands into the chat. The following actions are available :"
#: ../../livechat/overview/responses.rst:11
msgid "Commands are shortcuts that do specific actions within the chat window:"
msgstr ""
#: ../../livechat/livechat.rst:106
msgid "**/help** : show a helper message."
#: ../../livechat/overview/responses.rst:13
msgid "**/help**: shows a help message."
msgstr ""
#: ../../livechat/livechat.rst:108
msgid "**/helpdesk** : create a helpdesk ticket."
#: ../../livechat/overview/responses.rst:14
msgid "**/helpdesk**: creates a helpdesk ticket."
msgstr ""
#: ../../livechat/livechat.rst:110
msgid "**/helpdesk\\_search** : search for a helpdesk ticket."
#: ../../livechat/overview/responses.rst:15
msgid "**/helpdesk_search**: searches for a helpdesk ticket."
msgstr ""
#: ../../livechat/livechat.rst:112
msgid "**/history** : see 15 last visited pages."
#: ../../livechat/overview/responses.rst:16
msgid "**/history**: shows the last 15 visited pages."
msgstr ""
#: ../../livechat/livechat.rst:114
msgid "**/lead** : create a new lead."
#: ../../livechat/overview/responses.rst:17
msgid "**/lead**: creates a new lead."
msgstr ""
#: ../../livechat/livechat.rst:116
msgid "**/leave** : leave the channel."
#: ../../livechat/overview/responses.rst:18
msgid "**/leave**: leaves the channel."
msgstr ""
#: ../../livechat/livechat.rst:119
msgid "If a helpdesk ticket is created from the chat, then the conversation it was generated from will automatically appear as the description of the ticket. The same goes for the creation of a lead."
#: ../../livechat/overview/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 ""
#: ../../livechat/livechat.rst:124
#: ../../livechat/overview/responses.rst:0
msgid "- For *leads*: the *CRM* application must be installed on your database."
msgstr ""
#: ../../livechat/overview/responses.rst:26
msgid "To access the ticket or lead created from the chat, click on the shortcut link."
msgstr ""
#: ../../livechat/overview/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."
msgstr ""
#: ../../livechat/overview/responses.rst:37
msgid "Send canned responses"
msgstr ""
#: ../../livechat/livechat.rst:126
msgid "Canned responses allow you to create substitutes to generic sentences you frequently use. Typing a word instead of several will save you a lot of time. To add canned responses, go to :menuselection:`LIVE CHAT --> Configuration --> Canned Responses` and create as many as you need to. Then, to use them during a chat, simply type \":\" followed by the shortcut you assigned."
#: ../../livechat/overview/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`."
msgstr ""
#: ../../livechat/livechat.rst:136
msgid "You now have all of the tools needed to chat in live with your website visitors, enjoy !"
#: ../../livechat/overview/responses.rst:41
msgid "To use them during a conversation, simply type **:** followed by the shortcut word you created."
msgstr ""

View File

@ -8,7 +8,7 @@ msgid ""
msgstr ""
"Project-Id-Version: Odoo 13.0\n"
"Report-Msgid-Bugs-To: \n"
"POT-Creation-Date: 2020-02-11 14:56+0100\n"
"POT-Creation-Date: 2020-09-24 12:02+0200\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"
@ -167,7 +167,7 @@ msgstr ""
#: ../../manufacturing/management/flexible_components_consumption.rst:16
#: ../../manufacturing/management/kit_shipping.rst:31
#: ../../manufacturing/management/kit_shipping.rst:66
#: ../../manufacturing/management/subcontracting.rst:9
#: ../../manufacturing/management/subcontracting.rst:26
#: ../../manufacturing/management/use_mps.rst:9
msgid "Configuration"
msgstr ""
@ -497,119 +497,223 @@ msgid "Now, each time you will plan a manufacturing order for the top-level prod
msgstr ""
#: ../../manufacturing/management/subcontracting.rst:3
msgid "Subcontract the manufacturing"
msgid "Subcontract your Manufacturing"
msgstr ""
#: ../../manufacturing/management/subcontracting.rst:5
msgid "Some businesses subcontract the production of finished products through subcontractors. This can be easily managed through Odoo."
msgid "Outsourcing a portion of some or all your companys manufacturing needs is not easy. To make it work right, you have to:"
msgstr ""
#: ../../manufacturing/management/subcontracting.rst:8
msgid "Manage the inventory of raw materials at your subcontractor;"
msgstr ""
#: ../../manufacturing/management/subcontracting.rst:9
msgid "Ship new materials to your subcontractors based on your forecasted demand;"
msgstr ""
#: ../../manufacturing/management/subcontracting.rst:11
msgid "Go to the :menuselection:`Manufacturing app --> Configuration --> Settings` and tick the box *Subcontracting*."
msgid "Keep track of manufacturing operations done at the subcontractor location;"
msgstr ""
#: ../../manufacturing/management/subcontracting.rst:17
msgid "You can now define subcontracted *Bill of Materials*. Therefore, you need to go to :menuselection:`Manufacturing --> Master Data --> Bill of Materials` and hit *Create*. In this *BoM*, list the components which will be used by the subcontractor to manufacture the subcontracted finished product. Specify that the *BoM* type is *Subcontracting* and define one or several subcontractors who will provide you the product."
#: ../../manufacturing/management/subcontracting.rst:13
msgid "Control incoming goods quality;"
msgstr ""
#: ../../manufacturing/management/subcontracting.rst:29
msgid "And... the configuration part is already done!"
#: ../../manufacturing/management/subcontracting.rst:14
msgid "Control subcontractors bills."
msgstr ""
#: ../../manufacturing/management/subcontracting.rst:32
msgid "Receive or buy a subcontracted product"
#: ../../manufacturing/management/subcontracting.rst:16
msgid "Here is an example of subcontracting the manufacturing of “C”, which is produced out of raw materials “A” and “B”."
msgstr ""
#: ../../manufacturing/management/subcontracting.rst:34
msgid "You have two options to trigger the subcontracting of a product:"
#: ../../manufacturing/management/subcontracting.rst:23
msgid "With its subcontracting feature, Odoo helps you handle this flow easily."
msgstr ""
#: ../../manufacturing/management/subcontracting.rst:36
msgid "**Option A**: You can buy the subcontracted product from your subcontractor"
#: ../../manufacturing/management/subcontracting.rst:28
msgid "To use the subcontracting feature, go to :menuselection:`Manufacturing --> Configuration --> Settings` and tick the box *Subcontracting*."
msgstr ""
#: ../../manufacturing/management/subcontracting.rst:35
msgid "To define if a product must be subcontracted, use a *Bill of Materials (BoM)* of type *Subcontracting*."
msgstr ""
#: ../../manufacturing/management/subcontracting.rst:38
msgid "**Option B**: You can directly receive the subcontracted product"
msgid "To create a new *BoM*, go to :menuselection:`Manufacturing --> Master Data --> Bill of Materials` and hit create. Then, list the components your subcontractor needs to manufacture the product. For costing purposes, you might want to register all the components, even the ones that are sourced directly from the subcontractor."
msgstr ""
#: ../../manufacturing/management/subcontracting.rst:40
msgid "Lets start with option A (option B is just a simpler version of it)."
#: ../../manufacturing/management/subcontracting.rst:44
msgid "Once you have set the *BoM Type* to *Subcontracting*, specify one or several subcontractors."
msgstr ""
#: ../../manufacturing/management/subcontracting.rst:42
msgid "Create a new purchase order. The vendor must be a subcontractor. The unit price should be the cost you are paying to the subcontractor for the subcontracting (thus, its not necessarily the total cost of the subcontracted product)."
msgstr ""
#: ../../manufacturing/management/subcontracting.rst:50
msgid "The validation of the purchase order automatically creates the receipt. Whenever you receive the product, you can validate the receipt. The following stock moves are created:"
#: ../../manufacturing/management/subcontracting.rst:52
msgid "Basic Subcontracting Flow"
msgstr ""
#: ../../manufacturing/management/subcontracting.rst:54
msgid "For the components"
msgid "To let your subcontractor know how many products you need, create and send them purchase orders (PO). To do so, open the *Purchase* app and create a new one. Be sure to send the PO to a vendor that is defined as a subcontractor on the *BoM*."
msgstr ""
#: ../../manufacturing/management/subcontracting.rst:56
msgid "From Subcontracting To Production"
#: ../../manufacturing/management/subcontracting.rst:63
msgid "Once the *PO* is validated (1), a pending receipt is created. When the products are received, validate the receipt (2), with the actual quantity received. Then Odoo automatically created several inventory moves:"
msgstr ""
#: ../../manufacturing/management/subcontracting.rst:58
msgid "For the subcontracted product"
#: ../../manufacturing/management/subcontracting.rst:68
msgid "Consume the components at the subcontractors location, based on the *BoM* (3);"
msgstr ""
#: ../../manufacturing/management/subcontracting.rst:60
msgid "From Production to Subcontracting"
#: ../../manufacturing/management/subcontracting.rst:70
msgid "Produce finished goods at the subcontractors location (4);"
msgstr ""
#: ../../manufacturing/management/subcontracting.rst:62
msgid "From Subcontracting to Stock"
#: ../../manufacturing/management/subcontracting.rst:71
msgid "Move products from the subcontractors location to YourCompany through the validated receipt (5)."
msgstr ""
#: ../../manufacturing/management/subcontracting.rst:64
msgid "The *Subcontracting Location* represents the place where the products are at your subcontractors warehouse. It is configured as an internal location, the components that are sent to the subcontractor are still valued in your stock."
#: ../../manufacturing/management/subcontracting.rst:74
msgid "Of course, Odoo does all the transactions for you, automatically. Simply control the vendor bill with the usual matching process with the purchase order."
msgstr ""
#: ../../manufacturing/management/subcontracting.rst:69
msgid "For option B, you can simply create the receipt manually with a partner of type subcontractor defined on it."
#: ../../manufacturing/management/subcontracting.rst:79
msgid "The *PO* is optional. If you create a receipt manually, with the right subcontractor, Odoo still performs all the moves. Useful if the subcontractor does not bill a fixed price per item, but rather the time and materials used."
msgstr ""
#: ../../manufacturing/management/subcontracting.rst:73
msgid "Receive or buy a subcontracted product with tracked components"
#: ../../manufacturing/management/subcontracting.rst:85
msgid "Inventory Valuation"
msgstr ""
#: ../../manufacturing/management/subcontracting.rst:75
msgid "In case the subcontracted product you receive from your subcontractor contains tracked components, you will need to specify the *serial/lot numbers* of the components in question for traceability. This operation is included in the receipt of the subcontracted product."
#: ../../manufacturing/management/subcontracting.rst:87
msgid "The cost of the manufactured product “C” is defined as:"
msgstr ""
#: ../../manufacturing/management/subcontracting.rst:80
msgid "On the receipt, you see a *Record Components* button appearing when necessary. If you click on it, a *Produce* wizard opens in which you will have to enter the *serial/lot numbers* of the components, and the finished product if it is also tracked, like in the below example."
#: ../../manufacturing/management/subcontracting.rst:89
msgid "**C = A + B + s**"
msgstr ""
#: ../../manufacturing/management/subcontracting.rst:91
msgid "Once this information has been entered, you will see a new icon on the receipt stock move, which will allow you to find back the components which are part of the finished product."
msgid "With:"
msgstr ""
#: ../../manufacturing/management/subcontracting.rst:99
msgid "Resupply the subcontractor with the components"
#: ../../manufacturing/management/subcontracting.rst:93
msgid "**A**: Cost of raw materials coming from YourCompany;"
msgstr ""
#: ../../manufacturing/management/subcontracting.rst:101
msgid "There are 3 ways to manage the resupply of your subcontractor with the components:"
#: ../../manufacturing/management/subcontracting.rst:96
msgid "**B**: Cost of raw materials sourced directly from the"
msgstr ""
#: ../../manufacturing/management/subcontracting.rst:104
msgid "**Manually**: You create a delivery order in which you set the subcontractor as a partner and you choose the components to deliver."
#: ../../manufacturing/management/subcontracting.rst:96
msgid "subcontractor;"
msgstr ""
#: ../../manufacturing/management/subcontracting.rst:110
msgid "You therefore need to activate *Multi-locations* in the inventory settings."
#: ../../manufacturing/management/subcontracting.rst:98
msgid "**s**: Cost of the subcontracted service."
msgstr ""
#: ../../manufacturing/management/subcontracting.rst:100
msgid "Sending raw materials to your subcontractors (**A**) does not impact the inventory valuation, the components still belonging to your company. To manage this, the *Subcontracting Location* is configured as an *Internal Location* so that the components are still valued in the inventory."
msgstr ""
#: ../../manufacturing/management/subcontracting.rst:106
msgid "Then, the vendor price set on the product C form has to be what has to be paid to the subcontractor for his parts and service time: **B + s**. The product cost has to be: **A + B + s**, how much the product is valued in the accounting."
msgstr ""
#: ../../manufacturing/management/subcontracting.rst:111
msgid "Finally, the subcontractor bill matches the purchase order, with the proposed price coming from the finished products C."
msgstr ""
#: ../../manufacturing/management/subcontracting.rst:115
msgid "**With reordering rules**: You can define a *reordering rule* on the *Subcontracting location* to ensure that they are always enough components sent to your subcontractors. When the reordering rule is triggered, a delivery order is created for the product is automatically created."
msgid "If managing the replenishment of raw materials **B** at your subcontractors location is not needed, simply include the cost of **B** in the subcontractors price **s** and remove the products *B* from the *BoM*."
msgstr ""
#: ../../manufacturing/management/subcontracting.rst:120
msgid "**On order**: You can also deliver the components to your subcontractors each time you order a subcontracted product. For this, you need to tick the route *Resupply Subcontractor on Order* on the wanted components."
#: ../../manufacturing/management/subcontracting.rst:121
msgid "Traceability"
msgstr ""
#: ../../manufacturing/management/subcontracting.rst:123
msgid "In case the products received from the subcontractor contain tracked components, their serial or lot numbers need to be specified during the receipt."
msgstr ""
#: ../../manufacturing/management/subcontracting.rst:127
msgid "On the receipt of the subcontracted product, a *Record Components* button appears when necessary. Click on it to open a dialog and record the serial/lot numbers of the components. If the finished product is also tracked, its serial/lot number can be registered here too."
msgstr ""
#: ../../manufacturing/management/subcontracting.rst:136
msgid "For audit purposes, it is possible to check the lot numbers recorded on a receipt by using the icon on the right of the finished products:"
msgstr ""
#: ../../manufacturing/management/subcontracting.rst:144
msgid "Automate Replenishment of Subcontractors"
msgstr ""
#: ../../manufacturing/management/subcontracting.rst:146
msgid "To manage the resupply of your subcontractor, activate *Multi-locations* in :menuselection:`Inventory --> Configuration --> Configuration`. Then, the inventory at the subcontractor location can be tracked."
msgstr ""
#: ../../manufacturing/management/subcontracting.rst:151
msgid "It is possible to resupply subcontractors by sending products from the company locations, or by sending products from another supplier to the subcontractors."
msgstr ""
#: ../../manufacturing/management/subcontracting.rst:156
msgid "Replenishment from the warehouse"
msgstr ""
#: ../../manufacturing/management/subcontracting.rst:158
msgid "Resupplying subcontractors manually is the simplest approach. To do so, create delivery orders in which the subcontractor is set as a delivery address and fill the components to deliver."
msgstr ""
#: ../../manufacturing/management/subcontracting.rst:162
msgid "To automate the subcontractors replenishment propositions, there are two approaches:"
msgstr ""
#: ../../manufacturing/management/subcontracting.rst:165
msgid "Reordering rules;"
msgstr ""
#: ../../manufacturing/management/subcontracting.rst:166
msgid "Replenish on order flow."
msgstr ""
#: ../../manufacturing/management/subcontracting.rst:168
msgid "For the first one, just define a reordering rule on the subcontracting location, with a minimum and maximum inventory level. When the reordering rule is triggered, a delivery order is created to ship the components to the subcontractor."
msgstr ""
#: ../../manufacturing/management/subcontracting.rst:177
msgid "The second approach is to use a “pull” flow. Here, the demand in the finished product (real demand or forecasted one through the Master Production Schedule) triggers the replenishment of the subcontractor. To do so, select the route *Resupply Subcontractor on Order* on the wanted components."
msgstr ""
#: ../../manufacturing/management/subcontracting.rst:188
msgid "Replenishment from another supplier"
msgstr ""
#: ../../manufacturing/management/subcontracting.rst:190
msgid "When purchasing items to another supplier, it is possible to ask him to deliver the subcontractor directly. To do so, activate the *Drop Shipping* feature in :menuselection:`Purchase --> Configuration --> Configuration`."
msgstr ""
#: ../../manufacturing/management/subcontracting.rst:195
msgid "Now, set the *Dropship* option in the *Deliver To* field of the *Other Information* tab. Then, provide the address of the subcontractor for the shipping."
msgstr ""
#: ../../manufacturing/management/subcontracting.rst:203
msgid "That way, the supplier can ship items directly and you simply receive and pay the bill. However, it is still required to validate receipts for the subcontractor."
msgstr ""
#: ../../manufacturing/management/subcontracting.rst:212
msgid "Quality Control"
msgstr ""
#: ../../manufacturing/management/subcontracting.rst:214
msgid "Controlling the quality of the products manufactured by subcontractors is possible thanks to the Odoo Quality app. Quality checks can be made on a manufacturing step but, because the manufacturing process is handled by an external party, it can be defined on the product reception."
msgstr ""
#: ../../manufacturing/management/subcontracting.rst:224
msgid "To create a quality check at the receipt, open the *Quality* app and create a new *Control Point* on the reception."
msgstr ""
#: ../../manufacturing/management/subcontracting.rst:231
msgid "By doing so, a quality check is automatically created each time a finished product is received."
msgstr ""
#: ../../manufacturing/management/unbuild.rst:3

View File

@ -8,7 +8,7 @@ msgid ""
msgstr ""
"Project-Id-Version: Odoo 13.0\n"
"Report-Msgid-Bugs-To: \n"
"POT-Creation-Date: 2020-01-16 09:46+0100\n"
"POT-Creation-Date: 2020-09-24 12:02+0200\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"
@ -20,95 +20,99 @@ msgstr ""
msgid "Planning"
msgstr ""
#: ../../planning/duplicate_a_planning.rst:3
msgid "Create a schedule and make encoding easier"
#: ../../planning/overview.rst:3
msgid "Overview"
msgstr ""
#: ../../planning/duplicate_a_planning.rst:4
#: ../../planning/overview/duplicate_a_planning.rst:3
msgid "Create a Schedule and Make Encoding Easier"
msgstr ""
#: ../../planning/overview/duplicate_a_planning.rst:5
msgid "Organize regular schedules or forecast projects in a long term basis. Create shifts to manage your tasks, assign employees, and stay organized at a high level."
msgstr ""
#: ../../planning/duplicate_a_planning.rst:8
#: ../../planning/overview/duplicate_a_planning.rst:9
msgid "Organize your team by roles"
msgstr ""
#: ../../planning/duplicate_a_planning.rst:9
#: ../../planning/overview/duplicate_a_planning.rst:11
msgid "Go to :menuselection:`Configuration --> Roles --> Create`. Optionally, go to the *Employees* application, select the respective employee, and under *Work Information* select the *Default Planning Role*."
msgstr ""
#: ../../planning/duplicate_a_planning.rst:18
#: ../../planning/overview/duplicate_a_planning.rst:20
msgid "Make shifts recurrent"
msgstr ""
#: ../../planning/duplicate_a_planning.rst:19
#: ../../planning/overview/duplicate_a_planning.rst:22
msgid "While creating a shift, select *Repeat* and configure as needed, saving you from the need of re-planning it."
msgstr ""
#: ../../planning/duplicate_a_planning.rst:28
msgid "Repeated shifts are generated for the next six months. A modification is possible in developer mode, from *Settings*."
#: ../../planning/overview/duplicate_a_planning.rst:30
msgid "Repeated shifts are generated for the next six months. A modification is possible in :doc:`Developer mode <../../general/developer_mode/activate>`, from *Settings*."
msgstr ""
#: ../../planning/duplicate_a_planning.rst:32
#: ../../planning/overview/duplicate_a_planning.rst:38
msgid "To duplicate a shift in the Gantt view, press CTRL + drag and drop."
msgstr ""
#: ../../planning/duplicate_a_planning.rst:36
#: ../../planning/overview/duplicate_a_planning.rst:41
msgid "Save shifts as templates"
msgstr ""
#: ../../planning/duplicate_a_planning.rst:37
msgid "If creating a shift on the fly and knowing that you will use that template in the future, click on *Save as a Template*."
#: ../../planning/overview/duplicate_a_planning.rst:43
msgid "If creating a shift on the fly and know you might use that template in the future, click on *Save as a Template*."
msgstr ""
#: ../../planning/duplicate_a_planning.rst:46
#: ../../planning/overview/duplicate_a_planning.rst:51
msgid "To create a template in advance, go to :menuselection:`Configuration --> Shifts Templates --> Create`."
msgstr ""
#: ../../planning/duplicate_a_planning.rst:51
#: ../../planning/overview/duplicate_a_planning.rst:55
msgid "Duplicate a planning from the previous week"
msgstr ""
#: ../../planning/duplicate_a_planning.rst:52
#: ../../planning/overview/duplicate_a_planning.rst:57
msgid "When in the Gantt view, either under *Schedule by Employee, Role or Project*, instead of re-planning shifts that have been planned before, simply click on *Copy Previous Week*."
msgstr ""
#: ../../planning/duplicate_a_planning.rst:61
#: ../../planning/overview/duplicate_a_planning.rst:65
msgid "The integration with the *Time off* and *Employee* applications, show you grayed cells to the days when the employee does not work and is on vacation time, for example."
msgstr ""
#: ../../planning/send_planned_shifts.rst:3
msgid "Send planned shifts and give employees autonomy over shifts"
#: ../../planning/overview/send_planned_shifts.rst:3
msgid "Send Planned Shifts and Give Employees Autonomy Over Shifts"
msgstr ""
#: ../../planning/send_planned_shifts.rst:4
msgid "If you are not on top of your tasks and shifts you might fall behind, loosing productivity. Allowing your employees to have a say over shifts helps you to be on top of your workload, and gives them flexibility."
#: ../../planning/overview/send_planned_shifts.rst:5
msgid "If you are not on top of your tasks and shifts you might fall behind, losing productivity. Allowing your employees to have a say over shifts helps you to be on top of your workload, and gives them flexibility."
msgstr ""
#: ../../planning/send_planned_shifts.rst:9
#: ../../planning/overview/send_planned_shifts.rst:10
msgid "Publish and send the planned week by email"
msgstr ""
#: ../../planning/send_planned_shifts.rst:10
#: ../../planning/overview/send_planned_shifts.rst:12
msgid "Once you have your shifts planned, click on *Send Schedule*. Select *Include Open shift* if you would like the *Unassigned* shifts to be seen."
msgstr ""
#: ../../planning/send_planned_shifts.rst:17
msgid "Choose if you just want to *Publish* or *Publish and Send*. If you *Publish and Send*, employees will get an email that will redirect them to their planned tasks:"
#: ../../planning/overview/send_planned_shifts.rst:19
msgid "Choose if you just want to *Publish* or *Publish and Send*. If you *Publish and Send*, employees get an email that redirects them to their planned tasks:"
msgstr ""
#: ../../planning/send_planned_shifts.rst:25
#: ../../planning/overview/send_planned_shifts.rst:26
msgid "Employees will not be able to see shifts until they have been published."
msgstr ""
#: ../../planning/send_planned_shifts.rst:29
#: ../../planning/overview/send_planned_shifts.rst:29
msgid "Let employees unassign themselves from shifts"
msgstr ""
#: ../../planning/send_planned_shifts.rst:30
#: ../../planning/overview/send_planned_shifts.rst:31
msgid "Go to *Configuration* and enable *Allow Unassignment*. From now on, when an employee opens his tasks, he can indicate his unavailability clicking on *I am unavailable*. The shift will be opened again, allowing someone else to take it."
msgstr ""
#: ../../planning/send_planned_shifts.rst:45
#: ../../planning/overview/send_planned_shifts.rst:44
msgid "Employees have portal access; users have access to the database."
msgstr ""

File diff suppressed because it is too large Load Diff

File diff suppressed because it is too large Load Diff

View File

@ -8,7 +8,7 @@ msgid ""
msgstr ""
"Project-Id-Version: Odoo 13.0\n"
"Report-Msgid-Bugs-To: \n"
"POT-Creation-Date: 2020-03-19 13:03+0100\n"
"POT-Creation-Date: 2020-09-24 12:02+0200\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"
@ -245,7 +245,7 @@ msgid "In some industries, you may receive a bill from a vendor before receiving
msgstr ""
#: ../../purchase/purchases/rfq/3_way_matching.rst:9
msgid "To define whether the vendor bill should be paid or not, you can use what we call *3-way matching*. It refers to the comparaison of the information appearing on the *Purchase Order*, the *Vendor Bill* and the *Receipt*."
msgid "To define whether the vendor bill should be paid or not, you can use what we call *3-way matching*. It refers to the comparison of the information appearing on the *Purchase Order*, the *Vendor Bill* and the *Receipt*."
msgstr ""
#: ../../purchase/purchases/rfq/3_way_matching.rst:14

View File

@ -8,7 +8,7 @@ msgid ""
msgstr ""
"Project-Id-Version: Odoo 13.0\n"
"Report-Msgid-Bugs-To: \n"
"POT-Creation-Date: 2020-01-16 09:46+0100\n"
"POT-Creation-Date: 2020-09-24 12:02+0200\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"
@ -197,107 +197,140 @@ msgstr ""
msgid "Define Quality Control Points"
msgstr ""
#: ../../quality/control/control_points.rst:6
#: ../../quality/control/control_points.rst:5
msgid "Quality is an important factor when it comes to products or services. Nowadays, quality has become the differentiating factor for all goods and services. It is vital for businesses to deliver products that meet or exceed expectations. It also helps minimize waste."
msgstr ""
#: ../../quality/control/control_points.rst:10
msgid "That is why most manufacturers would not think of eliminating the quality control from their manufacturing process. After all, removing quality controls would dramatically increase the number of defective products that the company then has to rework or scrap."
msgstr ""
#: ../../quality/control/control_points.rst:15
msgid "Then, using business applications to ensure data quality is important. With Odoo insuring the rear, any major problem can be avoided before occurring!"
msgstr ""
#: ../../quality/control/control_points.rst:20
msgid "Quality Control Points"
msgstr ""
#: ../../quality/control/control_points.rst:8
msgid "If it is the first *Quality Control Point* that you create, know that you need to open the *Quality* app. Then, go to :menuselection:`Quality Control --> Control Points`. Once there, you have to define the product on which the quality control will take place, as well as the operation at which it should take place."
msgstr ""
#: ../../quality/control/control_points.rst:14
msgid "The *Quality Control Points* can take place during transfers or during the manufacturing process of the products. If you work with routings on your *Bill of Materials*, you have to precise at which step of the manufacturing process the quality control point should be applied."
msgstr ""
#: ../../quality/control/control_points.rst:19
msgid "The control type defines at which frequency the quality checks should take place:"
msgstr ""
#: ../../quality/control/control_points.rst:22
msgid "All Operations: all the operations will generate quality checks to perform;"
msgid "To create a *Quality Control Point*, go to :menuselection:`Quality --> Quality Control --> Control Points`. Once there, define the product on which the quality control point should take place. The operation at which it takes place also is to be defined here."
msgstr ""
#: ../../quality/control/control_points.rst:24
msgid "Randomly: the quality checks will only be performed on x% of the operation. You must define the percentage yourself, on the control point;"
msgstr ""
#: ../../quality/control/control_points.rst:26
msgid "Periodically: the quality checks will be performed periodically. The periodicity is based on the period you define (once a day, once a week)."
#: ../../quality/control/control_points.rst:27
msgid "The *Quality Control Points* take place during transfers or during the manufacturing process of the products. If working with routings on *Bill of Materials*, you have to precise at which step of the manufacturing process the quality control point needs to be applied."
msgstr ""
#: ../../quality/control/control_points.rst:32
msgid "Quality Control Point Types"
msgid "The *Control Type* defines at which frequency the quality checks should take place:"
msgstr ""
#: ../../quality/control/control_points.rst:34
msgid "Now that the rest is configured, you need to define the type of quality check."
#: ../../quality/control/control_points.rst:35
msgid "**All operations**: all the operations automatically generate quality checks to perform;"
msgstr ""
#: ../../quality/control/control_points.rst:38
msgid "Some of the types are only available with the manufacturing application."
msgid "**Randomly**: the quality checks only perform on x% of the operation. The percentage needs to be defined on the control point;"
msgstr ""
#: ../../quality/control/control_points.rst:41
msgid "Text"
msgid "**Periodically**: the quality checks are performed periodically. The periodicity is based on the defined period (once a day, once a week)."
msgstr ""
#: ../../quality/control/control_points.rst:43
msgid "This control point type allows you to give instructions to your workers during the transfer, or the manufacturing process."
#: ../../quality/control/control_points.rst:50
msgid "Quality Control Point Types"
msgstr ""
#: ../../quality/control/control_points.rst:56
msgid "Take a Picture"
#: ../../quality/control/control_points.rst:52
msgid "Now, one thing remains to be configured: the type of quality check. There are several types that can be used: text, take a picture, pass-fail, take a measure, register consumed material, register by-product, and print label."
msgstr ""
#: ../../quality/control/control_points.rst:58
msgid "This control point type asks you to take a picture of the product in a transfer, or when manufacturing it."
msgid "Some types are available only with the manufacturing application installed."
msgstr ""
#: ../../quality/control/control_points.rst:71
msgid "Pass-Fail"
#: ../../quality/control/control_points.rst:62
msgid "Text"
msgstr ""
#: ../../quality/control/control_points.rst:73
msgid "This type of control point requires that you specify if the products pass or fail a specific text. It can be applied for both transfers or manufacturing orders."
#: ../../quality/control/control_points.rst:64
msgid "This control point type allows giving instructions to workers during the transfer or during the manufacturing process."
msgstr ""
#: ../../quality/control/control_points.rst:80
msgid "For this kind of control point type, you have the possibility to define a failure message that will give instructions to follow in case of quality check failure."
msgid "Take a Picture"
msgstr ""
#: ../../quality/control/control_points.rst:94
msgid "Take a Measure"
#: ../../quality/control/control_points.rst:82
msgid "This control point type asks to take a picture of the product applied in a transfer or when manufacturing it."
msgstr ""
#: ../../quality/control/control_points.rst:96
msgid "This control point type requires you to enter the products measurements during a transfer, or during the manufacturing process."
#: ../../quality/control/control_points.rst:98
msgid "This process can be simplified by using a connected :doc:`camera <../../iot/devices/measurement_tool>`."
msgstr ""
#: ../../quality/control/control_points.rst:102
msgid "For this kind of control point type, you also have the possibility to define a failure message that will give instructions to the worker."
msgid "Pass-Fail"
msgstr ""
#: ../../quality/control/control_points.rst:115
#: ../../quality/control/control_points.rst:104
msgid "*Pass-Fail* requires to specify if the products pass or fail specific criteria. It can be applied for both transfers or manufacturing orders."
msgstr ""
#: ../../quality/control/control_points.rst:111
msgid "For this kind of type, there is the possibility to define a failure message giving instructions to follow in case of failure."
msgstr ""
#: ../../quality/control/control_points.rst:127
msgid "Take a Measure"
msgstr ""
#: ../../quality/control/control_points.rst:129
msgid "Taking measures requires to enter the products measurements during a transfer or during the manufacturing process."
msgstr ""
#: ../../quality/control/control_points.rst:132
msgid "To use it, it necessary to specify the norm for your products measurements, but also a tolerance threshold. Doing so, all the products with good measures can are automatically accepted."
msgstr ""
#: ../../quality/control/control_points.rst:140
msgid "As for *Pass-Fail*, this type allows defining a failure message that gives instructions to the worker."
msgstr ""
#: ../../quality/control/control_points.rst:156
msgid "This process can be simplified by using connected :doc:`measurement tools <../../iot/devices/camera>`."
msgstr ""
#: ../../quality/control/control_points.rst:159
msgid "Register Consumed Materials"
msgstr ""
#: ../../quality/control/control_points.rst:117
msgid "This control point type requires you register the component serial/lot numbers during the manufacturing process. It is only available if you work with routings."
#: ../../quality/control/control_points.rst:161
msgid "When using *Register Consumed Materials*, it is required to register the components serial/lot numbers during the manufacturing process."
msgstr ""
#: ../../quality/control/control_points.rst:128
#: ../../quality/control/control_points.rst:165
#: ../../quality/control/control_points.rst:182
msgid "This type is only available when working with routings."
msgstr ""
#: ../../quality/control/control_points.rst:176
msgid "Register By-Products"
msgstr ""
#: ../../quality/control/control_points.rst:130
msgid "With this control point type, you must register the serial/lot number of the by-products that are manufactured. It is also only available with routings."
#: ../../quality/control/control_points.rst:178
msgid "With *Register By-Products*, it is required to register the serial/lot number of the by-products that are manufactured."
msgstr ""
#: ../../quality/control/control_points.rst:141
#: ../../quality/control/control_points.rst:193
msgid "Print Label"
msgstr ""
#: ../../quality/control/control_points.rst:143
msgid "This control point type allows you to print labels to add to the product during the manufacturing process."
#: ../../quality/control/control_points.rst:195
msgid "*Print Label*, as its name points out, allows printing labels to add to the product during the manufacturing process."
msgstr ""
#: ../../quality/control/control_points.rst:207
msgid "This process can be simplified by using a connected :doc:`printer <../../iot/devices/printer>`."
msgstr ""

File diff suppressed because it is too large Load Diff

View File

@ -8,7 +8,7 @@ msgid ""
msgstr ""
"Project-Id-Version: Odoo 13.0\n"
"Report-Msgid-Bugs-To: \n"
"POT-Creation-Date: 2020-03-19 13:03+0100\n"
"POT-Creation-Date: 2020-09-24 12:02+0200\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"
@ -25,54 +25,46 @@ msgid "Overview"
msgstr ""
#: ../../sms_marketing/overview/contact_lists_and_blacklist.rst:3
msgid "Contact lists and Blacklist"
msgid "Contact Lists and Blacklist"
msgstr ""
#: ../../sms_marketing/overview/contact_lists_and_blacklist.rst:4
msgid "Creating your own list of contacts, or importing it, is useful when you want to create specific groups of people, such as the subscribers of your newsletter. It is also the best way to get started if you are coming from another system and already have built an audience. It makes the SMS distribution a lot easier."
#: ../../sms_marketing/overview/contact_lists_and_blacklist.rst:5
msgid "Creating your own list of contacts, or importing it, is useful when you want to create specific groups of people, such as the subscribers of your newsletter. It is also the best way to get started if you are coming from another system and already have built an audience. It makes the SMS distribution easier."
msgstr ""
#: ../../sms_marketing/overview/contact_lists_and_blacklist.rst:11
msgid "Contact lists"
msgstr ""
#: ../../sms_marketing/overview/contact_lists_and_blacklist.rst:12
#: ../../sms_marketing/overview/contact_lists_and_blacklist.rst:13
msgid "Go to :menuselection:`Contacts lists --> Contacts lists --> Create`."
msgstr ""
#: ../../sms_marketing/overview/contact_lists_and_blacklist.rst:15
msgid "Choose a name for your *Mailing list*, and activate the option *Public* if you would like to make the mailing list accessible to your recipients in the unsubscription page to allow them to update their subscription preferences."
msgstr ""
#: ../../sms_marketing/overview/contact_lists_and_blacklist.rst:16
msgid "Once inside the list, you can again *Create* or *Import* contacts for that specific list."
msgid "Choose a name for your *Mailing list*, and activate the option *Is Public* if you would like to make the mailing list accessible to your recipients in the unsubscription page (allowing users to update their subscription preferences)."
msgstr ""
#: ../../sms_marketing/overview/contact_lists_and_blacklist.rst:22
msgid "History with the Log Notes"
msgstr ""
#: ../../sms_marketing/overview/contact_lists_and_blacklist.rst:23
msgid "A record of the mailings sent is kept in the chatter of the recipient (whether it is a contact or an opportunity, for example)."
#: ../../sms_marketing/overview/contact_lists_and_blacklist.rst:25
msgid "A record of the mailings sent is kept on the recipient's chatter (whether it is a contact or an opportunity, for example)."
msgstr ""
#: ../../sms_marketing/overview/contact_lists_and_blacklist.rst:31
msgid "This is important as you and your team can easily keep track and see a history of interactions with your contacts or prospects, granting you the ability to better understand them."
#: ../../sms_marketing/overview/contact_lists_and_blacklist.rst:28
msgid "This is important as you and team members can easily keep track and see a history of the interactions with your contacts or prospects. Example: your sales representative can easily find out which SMS mailing promotions a customer has received or not."
msgstr ""
#: ../../sms_marketing/overview/contact_lists_and_blacklist.rst:33
msgid "Example: your sales representative can easily find out which SMS mailing promotions a customer has received or not."
msgstr ""
#: ../../sms_marketing/overview/contact_lists_and_blacklist.rst:37
#: ../../sms_marketing/overview/contact_lists_and_blacklist.rst:35
msgid "Blacklist"
msgstr ""
#: ../../sms_marketing/overview/contact_lists_and_blacklist.rst:39
msgid "If you are coming from another software and have a list of clients who have already asked to be blacklisted, you can import those entries in your database."
#: ../../sms_marketing/overview/contact_lists_and_blacklist.rst:38
msgid "If you are coming from another software and have a list of clients who have already asked to be blacklisted, you can import those entries to your database."
msgstr ""
#: ../../sms_marketing/overview/contact_lists_and_blacklist.rst:40
#: ../../sms_marketing/overview/contact_lists_and_blacklist.rst:39
msgid "For that, go to :menuselection:`Configuration --> Phone Blacklist --> Import`."
msgstr ""
@ -80,188 +72,188 @@ msgstr ""
msgid "Integrations and Templates"
msgstr ""
#: ../../sms_marketing/overview/integrations_and_template.rst:4
msgid "Using SMS to reach people can be a strategy not just used for advertisement purposes but also as a reminder of events or issued invoices to your costumers, for example."
#: ../../sms_marketing/overview/integrations_and_template.rst:5
msgid "Using SMS to reach people can be a strategy not just used for advertisement purposes, but also as a reminder of events or issued invoices to your costumers, for example."
msgstr ""
#: ../../sms_marketing/overview/integrations_and_template.rst:9
msgid "Organize Email Marketing and SMS Campaigns"
msgid "Campaigns"
msgstr ""
#: ../../sms_marketing/overview/integrations_and_template.rst:10
msgid "First, make sure to have the necessary feature activated. Go to the :menuselection:`Email Marketing app --> Configuration --> Settings --> activate the option Mailing Campaigns`."
#: ../../sms_marketing/overview/integrations_and_template.rst:11
msgid "First, make sure to have the necessary feature activated. Go to the :menuselection:`Email Marketing app --> Configuration --> Settings` and enable *Mailing Campaigns*."
msgstr ""
#: ../../sms_marketing/overview/integrations_and_template.rst:16
msgid "Now, you will also have the menu *Campaigns* included in your *SMS Marketing* page, allowing you to have an overview of your SMS mailings and your email marketing ones."
#: ../../sms_marketing/overview/integrations_and_template.rst:17
msgid "Now, the menu *Campaigns* is also available on the *SMS Marketing* app, allowing you to manage and have an overview of your SMS mailings under campaigns."
msgstr ""
#: ../../sms_marketing/overview/integrations_and_template.rst:22
msgid "This feature is especially useful if you have aggregated campaigns, as you have a global reporting view. In addition to that, you can create stages in your kanban view to better organize the work being done."
#: ../../sms_marketing/overview/integrations_and_template.rst:23
msgid "This feature is especially useful if you have aggregated campaigns, as you have a global reporting view. In addition to that, you can create stages in your Kanban view to better organize the work being done."
msgstr ""
#: ../../sms_marketing/overview/integrations_and_template.rst:30
#: ../../sms_marketing/overview/integrations_and_template.rst:31
msgid "Sending SMSs through the Contacts app"
msgstr ""
#: ../../sms_marketing/overview/integrations_and_template.rst:32
#: ../../sms_marketing/overview/integrations_and_template.rst:34
msgid "Sending SMSs through the contacts form is available by default in Odoo. It makes your work easier if you need to send an SMS to a specific contact, for example."
msgstr ""
#: ../../sms_marketing/overview/integrations_and_template.rst:34
#: ../../sms_marketing/overview/integrations_and_template.rst:36
msgid "For that, go to the *Contacts* app, select the contact and click on the *SMS* icon next to the phone number."
msgstr ""
#: ../../sms_marketing/overview/integrations_and_template.rst:39
msgid "If you would like to send a message in a batch here, you could go to :menuselection:`List View --> select all the contacts --> Action --> Send SMS`."
msgstr ""
#: ../../sms_marketing/overview/integrations_and_template.rst:47
msgid "Set up SMS Templates"
#: ../../sms_marketing/overview/integrations_and_template.rst:41
msgid "If you would like to send a message to multiple contacts at once, choose the *List View*, select all the contacts needed, and under *Action* select *Send SMS*."
msgstr ""
#: ../../sms_marketing/overview/integrations_and_template.rst:48
msgid "To set up *SMS Templates*, activate the :doc:`Developer mode <../../general/developer_mode/activate>`. Now, go to :menuselection:`Technical --> Phone/SMS section --> SMS Templates`."
msgid "Set up SMS templates"
msgstr ""
#: ../../sms_marketing/overview/integrations_and_template.rst:59
#: ../../sms_marketing/overview/integrations_and_template.rst:50
msgid "To set up *SMS Templates*, activate the :doc:`Developer mode <../../general/developer_mode/activate>`, then go to :menuselection:`Technical --> SMS Templates`."
msgstr ""
#: ../../sms_marketing/overview/integrations_and_template.rst:60
msgid "Use *Dynamic Placeholders* to adapt automatically the content of the SMS to the context."
msgstr ""
#: ../../sms_marketing/overview/integrations_and_template.rst:62
msgid "SMS Text Messaging is available throughout Odoo! Here are some of our extra notable integrations:"
msgstr ""
#: ../../sms_marketing/overview/integrations_and_template.rst:64
msgid "*CRM*: send SMSs to your leads and opportunities."
#: ../../sms_marketing/overview/integrations_and_template.rst:63
msgid "SMS Text Messaging is available throughout Odoo:"
msgstr ""
#: ../../sms_marketing/overview/integrations_and_template.rst:65
msgid "*Subscription*: alert customers about their subscription."
msgid "*CRM*: send SMSs to your leads and opportunities."
msgstr ""
#: ../../sms_marketing/overview/integrations_and_template.rst:66
msgid "*Accounting*: send payment reminders."
msgid "*Subscription*: alert customers about their subscription."
msgstr ""
#: ../../sms_marketing/overview/integrations_and_template.rst:67
msgid "*Marketing Automation*: automate your SMS marketing campaigns."
msgid "*Accounting*: send payment reminders."
msgstr ""
#: ../../sms_marketing/overview/integrations_and_template.rst:68
msgid "*Inventory*: send an automatic confirmation when a delivery order is done."
msgid "*Marketing Automation*: automate your SMS marketing campaigns."
msgstr ""
#: ../../sms_marketing/overview/integrations_and_template.rst:69
msgid "*Sign*: receive a validation code to verify your identity before signing a document online."
msgid "*Inventory*: send an automatic confirmation when a delivery order is done."
msgstr ""
#: ../../sms_marketing/overview/integrations_and_template.rst:70
msgid "*SEPA debit payment provider*: send a verification code to your customers."
msgid "*Sign*: receive a validation code to verify your identity before signing a document online."
msgstr ""
#: ../../sms_marketing/overview/integrations_and_template.rst:71
msgid "*SEPA debit payment provider*: send a verification code to your customers."
msgstr ""
#: ../../sms_marketing/overview/integrations_and_template.rst:72
msgid "*Studio*: send an SMS according to your needs by using automated actions."
msgstr ""
#: ../../sms_marketing/overview/integrations_and_template.rst:74
#: ../../sms_marketing/overview/integrations_and_template.rst:75
msgid "For more information about SMS integrations in Odoo and a list of frequently asked questions, go to :doc:`../pricing/pricing_and_faq`."
msgstr ""
#: ../../sms_marketing/overview/integrations_and_template.rst:79
msgid ":doc:`../../social_marketing/overview/campaigns`"
msgstr ""
#: ../../sms_marketing/overview/integrations_and_template.rst:80
msgid ":doc:`../../discuss/advanced/email_template`"
msgstr ""
#: ../../sms_marketing/overview/sms_mailing_reports.rst:3
msgid "Build, Send and Get Reports from a SMS Mailing"
msgstr ""
#: ../../sms_marketing/overview/sms_mailing_reports.rst:4
msgid "Using SMS Marketing as part of your communication strategies can empower you to expand your markets, considering that in some countries emails are not very used or used at all. It also helps to boost conversion rates, as this strategy has a high open-rate percentage among people who use smartphones - people usually dont keep unread SMSs!"
#: ../../sms_marketing/overview/sms_mailing_reports.rst:5
msgid "Using SMS Marketing as part of your communication strategies can empower you to expand your markets, considering that in some countries emails are not very used or used at all. It also helps to boost conversion rates, as this strategy has a high open-rate percentage among people who use smartphones."
msgstr ""
#: ../../sms_marketing/overview/sms_mailing_reports.rst:11
msgid "Install the app"
msgid "Get started"
msgstr ""
#: ../../sms_marketing/overview/sms_mailing_reports.rst:13
msgid "Go to *Apps*, search for *SMS Marketing* and click on *Install*."
msgstr ""
#: ../../sms_marketing/overview/sms_mailing_reports.rst:16
msgid "Build an SMS mailing"
msgstr ""
#: ../../sms_marketing/overview/sms_mailing_reports.rst:18
msgid "Go to :menuselection:`SMS Marketing --> Create`."
msgstr ""
#: ../../sms_marketing/overview/sms_mailing_reports.rst:24
msgid "First, you will be able to specify a *subject* name that will help you to remember what the mailing is about."
#: ../../sms_marketing/overview/sms_mailing_reports.rst:18
msgid "Specify a *subject* name to help you remembering what the mailing is about."
msgstr ""
#: ../../sms_marketing/overview/sms_mailing_reports.rst:26
msgid "Under *recipients*, choose to whom you would like the SMS to be sent. If you choose *Contact*, all your Odoo contacts (vendor, customers, etc.) will receive your SMS."
#: ../../sms_marketing/overview/sms_mailing_reports.rst:20
msgid "Under *Recipients*, choose to whom you would like the SMS to be sent. If you choose *Contact*, all your Odoo contacts (vendor, customers, etc.) receive your SMS."
msgstr ""
#: ../../sms_marketing/overview/sms_mailing_reports.rst:28
msgid "From there, you can refine your recipient list with the *add filter* option. In the example below, the message will be sent to contacts living in Belgium."
#: ../../sms_marketing/overview/sms_mailing_reports.rst:22
msgid "From there, you can refine your recipient list with the *add filter* option. In the example below, the message would be sent to the contacts living in Belgium."
msgstr ""
#: ../../sms_marketing/overview/sms_mailing_reports.rst:27
msgid "The *Mailing list* option, on the other hand, allows you to choose the specific mailing lists you created to group specific contacts. You are allowed to select multiple ones."
msgstr ""
#: ../../sms_marketing/overview/sms_mailing_reports.rst:34
msgid "The *Mailing list* option, on the other hand, allows you to choose mailing lists you ve created with specific contacts or people who have subscribed to your Newsletters, or both! Note that you are allowed to select more than one *Mailing list*."
msgid "Under the *SMS Content* tab, links can be included and Odoo automatically generates *link trackers* in order to generate data about these links."
msgstr ""
#: ../../sms_marketing/overview/sms_mailing_reports.rst:42
msgid "Under the *SMS Content* tab, links can be included and Odoo will automatically generate *link trackers*. Thank to those, you will be able to get data about those links."
#: ../../sms_marketing/overview/sms_mailing_reports.rst:36
msgid "Under *Settings* you have the option *Include opt-out link*. If activated, the contact is able to unsubscribe from the mailing list."
msgstr ""
#: ../../sms_marketing/overview/sms_mailing_reports.rst:45
msgid "On *Settings* you have the option *include opt-out link* available. If activated, the contact will be able to unsubscribe from the mailing list he is not interested in anymore."
msgstr ""
#: ../../sms_marketing/overview/sms_mailing_reports.rst:52
#: ../../sms_marketing/overview/sms_mailing_reports.rst:43
msgid "In the *Link Tracker* menu under *Configuration*, you can see the history of your sent links, access them and look at statistics."
msgstr ""
#: ../../sms_marketing/overview/sms_mailing_reports.rst:59
#: ../../sms_marketing/overview/sms_mailing_reports.rst:50
msgid "Double-check that you have the phone number of your contacts saved."
msgstr ""
#: ../../sms_marketing/overview/sms_mailing_reports.rst:63
msgid "Sending my mailing"
#: ../../sms_marketing/overview/sms_mailing_reports.rst:53
msgid "Send a mailing"
msgstr ""
#: ../../sms_marketing/overview/sms_mailing_reports.rst:67
#: ../../sms_marketing/overview/sms_mailing_reports.rst:57
msgid "Once you have your mailing created, you must choose when you would like it to be delivered:"
msgstr ""
#: ../../sms_marketing/overview/sms_mailing_reports.rst:69
msgid "Put in queue: the mailing will be triggered with the next automatic run. Interesting option if you do not mind when the triggering will happen."
#: ../../sms_marketing/overview/sms_mailing_reports.rst:59
msgid "*Put in Queue*: the mailing is triggered with the next automatic run. Interesting option if you do not need the message to be sent at a specific time."
msgstr ""
#: ../../sms_marketing/overview/sms_mailing_reports.rst:71
msgid "Send now: sends the message immediately. Advised to use this option if there are not that many recipients."
#: ../../sms_marketing/overview/sms_mailing_reports.rst:61
msgid "*Send Now*: sends the message immediately. Use this option if the recipient list is not excessive."
msgstr ""
#: ../../sms_marketing/overview/sms_mailing_reports.rst:73
msgid "Schedule: allows you to choose a day and time. Best option for mailings that you would like to send during a specific event, to promote an offer while it is active or to simply plan your content strategy in advance."
#: ../../sms_marketing/overview/sms_mailing_reports.rst:62
msgid "*Schedule*: allows you to choose a day and time. Best option for mailings that you would like to send during a specific event, to promote an offer while it is active, or to simply plan your content strategy in advance."
msgstr ""
#: ../../sms_marketing/overview/sms_mailing_reports.rst:76
msgid "Test: allows you to send an SMS to one or multiple numbers for test purposes. Check, for example, if the link provided lands on the right page while making sure they are responsive. If sending it to multiple numbers, you must remember to use a comma between them."
#: ../../sms_marketing/overview/sms_mailing_reports.rst:65
msgid "*Test*: allows you to send an SMS to one or multiple numbers for test purposes. Check, for example, if the link provided lands on the right page while making sure they are responsive. If sending it to multiple numbers, you must remember to use a comma between them."
msgstr ""
#: ../../sms_marketing/overview/sms_mailing_reports.rst:82
#: ../../sms_marketing/overview/sms_mailing_reports.rst:70
msgid "Visualize reports"
msgstr ""
#: ../../sms_marketing/overview/sms_mailing_reports.rst:83
msgid "On the *Reporting* menu, with just a few clicks, you are capable of applying filters, measures and adopt different layouts to do an analysis of the performance of your SMS mailings."
#: ../../sms_marketing/overview/sms_mailing_reports.rst:72
msgid "Under the *Reporting* menu apply filters, measures, and adopt different layouts to do analyses of the performance of your SMS mailings."
msgstr ""
#: ../../sms_marketing/overview/sms_mailing_reports.rst:90
msgid "You can also check the price to send an SMS on your country when clicking on the *information* icon when creating a new SMS."
#: ../../sms_marketing/overview/sms_mailing_reports.rst:79
msgid "You can also check the price to send an SMS for your country by clicking on the *Information* icon."
msgstr ""
#: ../../sms_marketing/overview/sms_mailing_reports.rst:97
msgid "**Buy Credits!** In order to take advantage of the app and its features, make sure you have purchased credits. For more information on that access: :doc:`../pricing/pricing_and_faq`"
#: ../../sms_marketing/overview/sms_mailing_reports.rst:86
msgid "**Buy Credits:** in order to take advantage of the app and its features, make sure you have purchased credits. For more information: :doc:`../pricing/pricing_and_faq`."
msgstr ""
#: ../../sms_marketing/pricing.rst:3

View File

@ -8,7 +8,7 @@ msgid ""
msgstr ""
"Project-Id-Version: Odoo 13.0\n"
"Report-Msgid-Bugs-To: \n"
"POT-Creation-Date: 2020-03-19 13:03+0100\n"
"POT-Creation-Date: 2020-09-24 12:02+0200\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"
@ -37,7 +37,7 @@ msgid "Go to :menuselection:`Social Marketing --> Campaigns --> Create`."
msgstr ""
#: ../../social_marketing/overview/campaigns.rst:16
msgid "As you create content, tabs for that specific channel will be shown. The overview of the campaign shows you global metric such as:"
msgid "As you create content, tabs for that specific channel are shown. The overview of the campaign displays global metrics such as:"
msgstr ""
#: ../../social_marketing/overview/campaigns.rst:19
@ -127,7 +127,7 @@ msgid "To define which pages are tracked, on the *Website* application, go to :m
msgstr ""
#: ../../social_marketing/overview/livechat.rst:60
msgid ":doc:`../../livechat/livechat`"
msgid ":doc:`../../livechat/overview/get_started`"
msgstr ""
#: ../../social_marketing/overview/manage_social.rst:3

View File

@ -8,7 +8,7 @@ msgid ""
msgstr ""
"Project-Id-Version: Odoo 13.0\n"
"Report-Msgid-Bugs-To: \n"
"POT-Creation-Date: 2020-03-19 13:03+0100\n"
"POT-Creation-Date: 2020-09-24 12:02+0200\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"
@ -61,186 +61,200 @@ msgid "Release date"
msgstr ""
#: ../../support/supported_versions.rst:26
msgid "**Odoo 14.0**"
msgstr ""
#: ../../support/supported_versions.rst:26
#: ../../support/supported_versions.rst:26
#: ../../support/supported_versions.rst:26
msgid "🏁"
msgstr ""
#: ../../support/supported_versions.rst:26
msgid "October 2020"
msgstr ""
#: ../../support/supported_versions.rst:28
msgid "**Odoo 13.0**"
msgstr ""
#: ../../support/supported_versions.rst:26
#: ../../support/supported_versions.rst:26
#: ../../support/supported_versions.rst:26
#: ../../support/supported_versions.rst:28
#: ../../support/supported_versions.rst:28
#: ../../support/supported_versions.rst:28
#: ../../support/supported_versions.rst:30
#: ../../support/supported_versions.rst:30
#: ../../support/supported_versions.rst:30
#: ../../support/supported_versions.rst:32
#: ../../support/supported_versions.rst:32
#: ../../support/supported_versions.rst:32
#: ../../support/supported_versions.rst:34
#: ../../support/supported_versions.rst:34
#: ../../support/supported_versions.rst:34
#: ../../support/supported_versions.rst:36
#: ../../support/supported_versions.rst:36
#: ../../support/supported_versions.rst:36
msgid "|green|"
msgstr ""
#: ../../support/supported_versions.rst:26
#: ../../support/supported_versions.rst:28
msgid "October 2019"
msgstr ""
#: ../../support/supported_versions.rst:28
#: ../../support/supported_versions.rst:30
msgid "Odoo 12.saas~3"
msgstr ""
#: ../../support/supported_versions.rst:28
#: ../../support/supported_versions.rst:28
#: ../../support/supported_versions.rst:32
#: ../../support/supported_versions.rst:32
#: ../../support/supported_versions.rst:36
#: ../../support/supported_versions.rst:36
#: ../../support/supported_versions.rst:30
#: ../../support/supported_versions.rst:30
#: ../../support/supported_versions.rst:34
#: ../../support/supported_versions.rst:34
#: ../../support/supported_versions.rst:38
#: ../../support/supported_versions.rst:38
#: ../../support/supported_versions.rst:42
#: ../../support/supported_versions.rst:42
#: ../../support/supported_versions.rst:40
#: ../../support/supported_versions.rst:40
#: ../../support/supported_versions.rst:44
#: ../../support/supported_versions.rst:44
#: ../../support/supported_versions.rst:46
#: ../../support/supported_versions.rst:46
#: ../../support/supported_versions.rst:48
#: ../../support/supported_versions.rst:48
#: ../../support/supported_versions.rst:50
msgid "N/A"
msgstr ""
#: ../../support/supported_versions.rst:28
#: ../../support/supported_versions.rst:30
msgid "August 2019"
msgstr ""
#: ../../support/supported_versions.rst:30
#: ../../support/supported_versions.rst:32
msgid "**Odoo 12.0**"
msgstr ""
#: ../../support/supported_versions.rst:30
#: ../../support/supported_versions.rst:32
msgid "October 2018"
msgstr ""
#: ../../support/supported_versions.rst:32
#: ../../support/supported_versions.rst:34
msgid "Odoo 11.saas~3"
msgstr ""
#: ../../support/supported_versions.rst:32
#: ../../support/supported_versions.rst:34
msgid "April 2018"
msgstr ""
#: ../../support/supported_versions.rst:34
#: ../../support/supported_versions.rst:36
msgid "**Odoo 11.0**"
msgstr ""
#: ../../support/supported_versions.rst:34
#: ../../support/supported_versions.rst:36
msgid "October 2017"
msgstr ""
#: ../../support/supported_versions.rst:34
#: ../../support/supported_versions.rst:36
msgid "*End-of-support is planned for October 2020*"
msgstr ""
#: ../../support/supported_versions.rst:36
#: ../../support/supported_versions.rst:38
msgid "Odoo 10.saas~15"
msgstr ""
#: ../../support/supported_versions.rst:36
#: ../../support/supported_versions.rst:38
#: ../../support/supported_versions.rst:40
#: ../../support/supported_versions.rst:40
#: ../../support/supported_versions.rst:42
#: ../../support/supported_versions.rst:42
#: ../../support/supported_versions.rst:44
#: ../../support/supported_versions.rst:46
#: ../../support/supported_versions.rst:48
#: ../../support/supported_versions.rst:50
msgid "|orange|"
msgstr ""
#: ../../support/supported_versions.rst:36
#: ../../support/supported_versions.rst:38
msgid "March 2017"
msgstr ""
#: ../../support/supported_versions.rst:38
#: ../../support/supported_versions.rst:40
msgid "Odoo 10.saas~14"
msgstr ""
#: ../../support/supported_versions.rst:38
#: ../../support/supported_versions.rst:40
msgid "January 2017"
msgstr ""
#: ../../support/supported_versions.rst:40
#: ../../support/supported_versions.rst:42
msgid "**Odoo 10.0**"
msgstr ""
#: ../../support/supported_versions.rst:40
#: ../../support/supported_versions.rst:44
#: ../../support/supported_versions.rst:48
#: ../../support/supported_versions.rst:42
#: ../../support/supported_versions.rst:46
#: ../../support/supported_versions.rst:50
msgid "|red|"
msgstr ""
#: ../../support/supported_versions.rst:40
#: ../../support/supported_versions.rst:42
msgid "October 2016"
msgstr ""
#: ../../support/supported_versions.rst:42
#: ../../support/supported_versions.rst:44
msgid "Odoo 9.saas~11"
msgstr ""
#: ../../support/supported_versions.rst:42
#: ../../support/supported_versions.rst:44
msgid "May 2016"
msgstr ""
#: ../../support/supported_versions.rst:44
#: ../../support/supported_versions.rst:46
msgid "**Odoo 9.0**"
msgstr ""
#: ../../support/supported_versions.rst:44
#: ../../support/supported_versions.rst:46
msgid "October 2015"
msgstr ""
#: ../../support/supported_versions.rst:46
#: ../../support/supported_versions.rst:48
msgid "Odoo 8.saas~6"
msgstr ""
#: ../../support/supported_versions.rst:46
#: ../../support/supported_versions.rst:48
msgid "February 2015"
msgstr ""
#: ../../support/supported_versions.rst:48
#: ../../support/supported_versions.rst:50
msgid "**Odoo 8.0**"
msgstr ""
#: ../../support/supported_versions.rst:48
#: ../../support/supported_versions.rst:50
msgid "September 2014"
msgstr ""
#: ../../support/supported_versions.rst:54
#: ../../support/supported_versions.rst:56
msgid "|green| Supported version"
msgstr ""
#: ../../support/supported_versions.rst:56
#: ../../support/supported_versions.rst:58
msgid "|red| End-of-support"
msgstr ""
#: ../../support/supported_versions.rst:58
#: ../../support/supported_versions.rst:60
msgid "N/A Never released for this platform"
msgstr ""
#: ../../support/supported_versions.rst:60
#: ../../support/supported_versions.rst:62
msgid "|orange| Some of our older customers may still run this version on our Odoo Online servers, we provide help only on blocking issues and advise you to upgrade."
msgstr ""
#: ../../support/supported_versions.rst:62
#: ../../support/supported_versions.rst:64
msgid "🏁 Future version, not released yet"
msgstr ""
#: ../../support/supported_versions.rst:75
#: ../../support/supported_versions.rst:77
msgid "I run an older version of Odoo/OpenERP/TinyERP"
msgstr ""
#: ../../support/supported_versions.rst:77
#: ../../support/supported_versions.rst:79
msgid "OpenERP 7.0, 6.1, 6.0 and 5.0 is not supported anymore, on any platform."
msgstr ""
#: ../../support/supported_versions.rst:79
#: ../../support/supported_versions.rst:81
msgid "TinyERP 4.0, 3.0, 2.0 and 1.0 is not supported anymore, on any platform."
msgstr ""
#: ../../support/supported_versions.rst:81
#: ../../support/supported_versions.rst:83
msgid "You should consider `upgrading <https://upgrade.odoo.com/>`_ your database."
msgstr ""
@ -285,7 +299,7 @@ msgid "Issues that might occur in a test database after upgrading to a newer ver
msgstr ""
#: ../../support/what_can_i_expect.rst:34
msgid "*Odoo Support does not make changes to your production database, but gives you the material and knowledge to do it yourself!*"
msgid "*Odoo Support does not make changes to your production database without your agreement and gives you the material and knowledge to do it yourself!*"
msgstr ""
#: ../../support/what_can_i_expect.rst:39

View File

@ -8,7 +8,7 @@ msgid ""
msgstr ""
"Project-Id-Version: Odoo 13.0\n"
"Report-Msgid-Bugs-To: \n"
"POT-Creation-Date: 2020-03-19 13:03+0100\n"
"POT-Creation-Date: 2020-09-24 12:02+0200\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"
@ -112,6 +112,74 @@ msgstr ""
msgid "As a last step, authorize Odoo to access Google API."
msgstr ""
#: ../../website/optimize/link_tracker.rst:3
msgid "Track clicks and visitors using Link Trackers"
msgstr ""
#: ../../website/optimize/link_tracker.rst:5
msgid "Link Trackers allow you to track your marketing campaigns (emails, banner ads, blog posts, social media posts, affiliate links, etc.). This way, you are able to identify your best traffic sources and make informed decisions about the distribution of your marketing budget."
msgstr ""
#: ../../website/optimize/link_tracker.rst:10
msgid "Configuration"
msgstr ""
#: ../../website/optimize/link_tracker.rst:12
msgid "Go to :menuselection:`Website --> Configuration --> Settings` and activate *Link Trackers*."
msgstr ""
#: ../../website/optimize/link_tracker.rst:19
msgid "Set up traceable URLs"
msgstr ""
#: ../../website/optimize/link_tracker.rst:21
msgid "Go to :menuselection:`Website --> Go to website --> Promote --> Track this page`. Here, you are able to get a specific tracked URL based on the campaign, medium, and source being used."
msgstr ""
#: ../../website/optimize/link_tracker.rst:28
msgid "**URL**: url of the page you want to track (e.g. the home page or a product's page)."
msgstr ""
#: ../../website/optimize/link_tracker.rst:29
msgid "**Campaign**: context of your link (e.g. a special promotion)."
msgstr ""
#: ../../website/optimize/link_tracker.rst:30
msgid "**Medium**: channel used to share (deliver) your link (e.g. an email or a Facebook ad)."
msgstr ""
#: ../../website/optimize/link_tracker.rst:31
msgid "**Source**: platform where the traffic originates (e.g. Google or Twitter)."
msgstr ""
#: ../../website/optimize/link_tracker.rst:33
msgid "Now, click on *Get tracked link* to generate a URL that you can post or send by the source you have decided on."
msgstr ""
#: ../../website/optimize/link_tracker.rst:37
msgid "Follow-up on tracked links"
msgstr ""
#: ../../website/optimize/link_tracker.rst:39
msgid "To look at statistics of your links, go to :menuselection:`Website --> Go to website --> Promote --> Track this page`. Besides being able to see the *Most Clicked* and *Recently Used* links, click on *Stats* to see complete statistics about the number of clicks and the country of origin of those clicks."
msgstr ""
#: ../../website/optimize/link_tracker.rst:50
msgid "You can also access the link tracker by typing *odoo.com/r* on your browser."
msgstr ""
#: ../../website/optimize/link_tracker.rst:51
msgid "Activate the developer mode (:menuselection:`Settings --> Activate the developer mode`) and get access to the *Link Tracker* module and its back-end functionalities."
msgstr ""
#: ../../website/optimize/link_tracker.rst:53
msgid "Integrated with :doc:`Google Analytics <google_analytics>`, those trackers allow you to see the number of clicks and visitors to keep you on top of your marketing campaigns."
msgstr ""
#: ../../website/optimize/link_tracker.rst:55
msgid "The integration with the :doc:`CRM <../../crm/track_leads/prospect_visits>` application allows you to understand where your leads and opportunities are coming from."
msgstr ""
#: ../../website/optimize/seo.rst:3
msgid "How to do Search Engine Optimisation in Odoo (SEO)"
msgstr ""
@ -1005,7 +1073,7 @@ msgid "If you set up a custom domain *mydomain.com* name for *mydatabase.odoo.co
msgstr ""
#: ../../website/publish/domain_name.rst:120
msgid ":doc:`../../discuss/email_servers`"
msgid ":doc:`../../discuss/advanced/email_servers`"
msgstr ""
#: ../../website/publish/multi_website.rst:3