[I18N] Export 14.0 source terms
This commit is contained in:
Martin Trigaux
parent
21b1add8a8
commit
e218ae4991
87
.tx/config
87
.tx/config
@ -2,157 +2,182 @@
|
||||
host = https://www.transifex.com
|
||||
type = PO
|
||||
|
||||
[odoo-13-doc.accounting]
|
||||
[odoo-14-doc.accounting]
|
||||
file_filter = locale/<lang>/LC_MESSAGES/accounting.po
|
||||
source_file = locale/sources/accounting.pot
|
||||
source_lang = en
|
||||
|
||||
[odoo-13-doc.applications]
|
||||
[odoo-14-doc.applications]
|
||||
file_filter = locale/<lang>/LC_MESSAGES/applications.po
|
||||
source_file = locale/sources/applications.pot
|
||||
source_lang = en
|
||||
|
||||
[odoo-13-doc.crm]
|
||||
[odoo-14-doc.contributing]
|
||||
file_filter = locale/<lang>/LC_MESSAGES/contributing.po
|
||||
source_file = locale/sources/contributing.pot
|
||||
source_lang = en
|
||||
|
||||
[odoo-14-doc.crm]
|
||||
file_filter = locale/<lang>/LC_MESSAGES/crm.po
|
||||
source_file = locale/sources/crm.pot
|
||||
source_lang = en
|
||||
|
||||
[odoo-13-doc.db_management]
|
||||
[odoo-14-doc.db_management]
|
||||
file_filter = locale/<lang>/LC_MESSAGES/db_management.po
|
||||
source_file = locale/sources/db_management.pot
|
||||
source_lang = en
|
||||
|
||||
[odoo-13-doc.discuss]
|
||||
[odoo-14-doc.discuss]
|
||||
file_filter = locale/<lang>/LC_MESSAGES/discuss.po
|
||||
source_file = locale/sources/discuss.pot
|
||||
source_lang = en
|
||||
|
||||
[odoo-13-doc.ecommerce]
|
||||
[odoo-14-doc.ecommerce]
|
||||
file_filter = locale/<lang>/LC_MESSAGES/ecommerce.po
|
||||
source_file = locale/sources/ecommerce.pot
|
||||
source_lang = en
|
||||
|
||||
[odoo-13-doc.email_marketing]
|
||||
[odoo-14-doc.email_marketing]
|
||||
file_filter = locale/<lang>/LC_MESSAGES/email_marketing.po
|
||||
source_file = locale/sources/email_marketing.pot
|
||||
source_lang = en
|
||||
|
||||
[odoo-13-doc.expense]
|
||||
[odoo-14-doc.expense]
|
||||
file_filter = locale/<lang>/LC_MESSAGES/expense.po
|
||||
source_file = locale/sources/expense.pot
|
||||
source_lang = en
|
||||
|
||||
[odoo-13-doc.fsm]
|
||||
[odoo-14-doc.events]
|
||||
file_filter = locale/<lang>/LC_MESSAGES/events.po
|
||||
source_file = locale/sources/events.pot
|
||||
source_lang = en
|
||||
|
||||
[odoo-14-doc.fsm]
|
||||
file_filter = locale/<lang>/LC_MESSAGES/fsm.po
|
||||
source_file = locale/sources/fsm.pot
|
||||
source_lang = en
|
||||
|
||||
[odoo-13-doc.general]
|
||||
[odoo-14-doc.general]
|
||||
file_filter = locale/<lang>/LC_MESSAGES/general.po
|
||||
source_file = locale/sources/general.pot
|
||||
source_lang = en
|
||||
|
||||
[odoo-13-doc.getting_started]
|
||||
[odoo-14-doc.getting_started]
|
||||
file_filter = locale/<lang>/LC_MESSAGES/getting_started.po
|
||||
source_file = locale/sources/getting_started.pot
|
||||
source_lang = en
|
||||
|
||||
[odoo-13-doc.helpdesk]
|
||||
[odoo-14-doc.helpdesk]
|
||||
file_filter = locale/<lang>/LC_MESSAGES/helpdesk.po
|
||||
source_file = locale/sources/helpdesk.pot
|
||||
source_lang = en
|
||||
|
||||
[odoo-13-doc.index]
|
||||
[odoo-14-doc.index]
|
||||
file_filter = locale/<lang>/LC_MESSAGES/index.po
|
||||
source_file = locale/sources/index.pot
|
||||
source_lang = en
|
||||
|
||||
[odoo-13-doc.inventory]
|
||||
[odoo-14-doc.inventory]
|
||||
file_filter = locale/<lang>/LC_MESSAGES/inventory.po
|
||||
source_file = locale/sources/inventory.pot
|
||||
source_lang = en
|
||||
|
||||
[odoo-13-doc.iot]
|
||||
[odoo-14-doc.iot]
|
||||
file_filter = locale/<lang>/LC_MESSAGES/iot.po
|
||||
source_file = locale/sources/iot.pot
|
||||
source_lang = en
|
||||
|
||||
[odoo-13-doc.livechat]
|
||||
[odoo-14-doc.livechat]
|
||||
file_filter = locale/<lang>/LC_MESSAGES/livechat.po
|
||||
source_file = locale/sources/livechat.pot
|
||||
source_lang = en
|
||||
|
||||
[odoo-13-doc.mobile]
|
||||
[odoo-14-doc.mobile]
|
||||
file_filter = locale/<lang>/LC_MESSAGES/mobile.po
|
||||
source_file = locale/sources/mobile.pot
|
||||
source_lang = en
|
||||
|
||||
[odoo-13-doc.marketing_automation]
|
||||
[odoo-14-doc.marketing_automation]
|
||||
file_filter = locale/<lang>/LC_MESSAGES/marketing_automation.po
|
||||
source_file = locale/sources/marketing_automation.pot
|
||||
source_lang = en
|
||||
|
||||
[odoo-13-doc.manufacturing]
|
||||
[odoo-14-doc.manufacturing]
|
||||
file_filter = locale/<lang>/LC_MESSAGES/manufacturing.po
|
||||
source_file = locale/sources/manufacturing.pot
|
||||
source_lang = en
|
||||
|
||||
[odoo-13-doc.planning]
|
||||
[odoo-14-doc.planning]
|
||||
file_filter = locale/<lang>/LC_MESSAGES/planning.po
|
||||
source_file = locale/sources/planning.pot
|
||||
source_lang = en
|
||||
|
||||
[odoo-13-doc.point_of_sale]
|
||||
[odoo-14-doc.point_of_sale]
|
||||
file_filter = locale/<lang>/LC_MESSAGES/point_of_sale.po
|
||||
source_file = locale/sources/point_of_sale.pot
|
||||
source_lang = en
|
||||
|
||||
[odoo-13-doc.portal]
|
||||
[odoo-14-doc.portal]
|
||||
file_filter = locale/<lang>/LC_MESSAGES/portal.po
|
||||
source_file = locale/sources/portal.pot
|
||||
source_lang = en
|
||||
|
||||
[odoo-13-doc.practical]
|
||||
[odoo-14-doc.practical]
|
||||
file_filter = locale/<lang>/LC_MESSAGES/practical.po
|
||||
source_file = locale/sources/practical.pot
|
||||
source_lang = en
|
||||
|
||||
[odoo-13-doc.project]
|
||||
[odoo-14-doc.project]
|
||||
file_filter = locale/<lang>/LC_MESSAGES/project.po
|
||||
source_file = locale/sources/project.pot
|
||||
source_lang = en
|
||||
|
||||
[odoo-13-doc.purchase]
|
||||
[odoo-14-doc.purchase]
|
||||
file_filter = locale/<lang>/LC_MESSAGES/purchase.po
|
||||
source_file = locale/sources/purchase.pot
|
||||
source_lang = en
|
||||
|
||||
[odoo-13-doc.quality]
|
||||
[odoo-14-doc.quality]
|
||||
file_filter = locale/<lang>/LC_MESSAGES/quality.po
|
||||
source_file = locale/sources/quality.pot
|
||||
source_lang = en
|
||||
|
||||
[odoo-13-doc.sales]
|
||||
[odoo-14-doc.sales]
|
||||
file_filter = locale/<lang>/LC_MESSAGES/sales.po
|
||||
source_file = locale/sources/sales.pot
|
||||
source_lang = en
|
||||
|
||||
[odoo-13-doc.sms_marketing]
|
||||
[odoo-14-doc.sms_marketing]
|
||||
file_filter = locale/<lang>/LC_MESSAGES/sms_marketing.po
|
||||
source_file = locale/sources/sms_marketing.pot
|
||||
source_lang = en
|
||||
|
||||
[odoo-13-doc.social_marketing]
|
||||
[odoo-14-doc.social_marketing]
|
||||
file_filter = locale/<lang>/LC_MESSAGES/social_marketing.po
|
||||
source_file = locale/sources/social_marketing.pot
|
||||
source_lang = en
|
||||
|
||||
[odoo-13-doc.support]
|
||||
[odoo-14-doc.studio]
|
||||
file_filter = locale/<lang>/LC_MESSAGES/studio.po
|
||||
source_file = locale/sources/studio.pot
|
||||
source_lang = en
|
||||
|
||||
[odoo-14-doc.support]
|
||||
file_filter = locale/<lang>/LC_MESSAGES/support.po
|
||||
source_file = locale/sources/support.pot
|
||||
source_lang = en
|
||||
|
||||
[odoo-13-doc.website]
|
||||
[odoo-14-doc.survey]
|
||||
file_filter = locale/<lang>/LC_MESSAGES/survey.po
|
||||
source_file = locale/sources/survey.pot
|
||||
source_lang = en
|
||||
|
||||
[odoo-14-doc.timesheets]
|
||||
file_filter = locale/<lang>/LC_MESSAGES/timesheets.po
|
||||
source_file = locale/sources/timesheets.pot
|
||||
source_lang = en
|
||||
|
||||
[odoo-14-doc.website]
|
||||
file_filter = locale/<lang>/LC_MESSAGES/website.po
|
||||
source_file = locale/sources/website.pot
|
||||
source_lang = en
|
||||
|
||||
File diff suppressed because it is too large
Load Diff
@ -6,9 +6,9 @@
|
||||
#, fuzzy
|
||||
msgid ""
|
||||
msgstr ""
|
||||
"Project-Id-Version: Odoo 11.0\n"
|
||||
"Project-Id-Version: Odoo 13.0\n"
|
||||
"Report-Msgid-Bugs-To: \n"
|
||||
"POT-Creation-Date: 2018-10-19 10:03+0200\n"
|
||||
"POT-Creation-Date: 2020-09-22 16:26+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"
|
||||
|
||||
1320
locale/sources/contributing.pot
Normal file
1320
locale/sources/contributing.pot
Normal file
File diff suppressed because it is too large
Load Diff
@ -8,7 +8,7 @@ msgid ""
|
||||
msgstr ""
|
||||
"Project-Id-Version: Odoo 13.0\n"
|
||||
"Report-Msgid-Bugs-To: \n"
|
||||
"POT-Creation-Date: 2019-11-22 08:57+0100\n"
|
||||
"POT-Creation-Date: 2020-09-22 16:26+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,7 +39,9 @@ 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
|
||||
#: ../../crm/track_leads/prospect_visits.rst:12
|
||||
msgid "Configuration"
|
||||
@ -85,10 +87,6 @@ msgstr ""
|
||||
msgid "Here’s how, from the list view. Select the opportunities or leads you want to merge and the action button will appear. Then, you can select merge."
|
||||
msgstr ""
|
||||
|
||||
#: ../../crm/acquire_leads/convert.rst:66
|
||||
msgid "..note::"
|
||||
msgstr ""
|
||||
|
||||
#: ../../crm/acquire_leads/convert.rst:67
|
||||
msgid "It is also possible to merge more than 2 opportunities or leads."
|
||||
msgstr ""
|
||||
@ -106,7 +104,7 @@ msgid "Configure email aliases"
|
||||
msgstr ""
|
||||
|
||||
#: ../../crm/acquire_leads/generate_from_email.rst:13
|
||||
msgid "Each sales channel can have its own email alias, to generate leads/opportunities automatically assigned to it. It is useful if you manage several sales teams with specific business processes. You will find the configuration of sales channels under :menuselection:`Configuration --> Sales Channels`."
|
||||
msgid "Each sales teams can have its own email alias, to generate leads/opportunities automatically assigned to it. It is useful if you manage several sales teams with specific business processes. You will find the configuration of sales teams under :menuselection:`Configuration --> Sales Teams`."
|
||||
msgstr ""
|
||||
|
||||
#: ../../crm/acquire_leads/generate_from_website.rst:3
|
||||
@ -211,23 +209,24 @@ msgid "The generated leads will have the name of the company."
|
||||
msgstr ""
|
||||
|
||||
#: ../../crm/acquire_leads/lead_mining.rst:50
|
||||
#: ../../crm/optimize/partner_autocomplete.rst:36
|
||||
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 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:64
|
||||
#: ../../crm/acquire_leads/lead_mining.rst:65
|
||||
msgid "The blue box will automatically tell you how many credits are going to be consumed."
|
||||
msgstr ""
|
||||
|
||||
#: ../../crm/acquire_leads/lead_mining.rst:67
|
||||
#: ../../crm/acquire_leads/lead_mining.rst:68
|
||||
msgid "If you are on Odoo Online (SAAS) and have the Enterprise version, you benefit from free trial credits to test the feature."
|
||||
msgstr ""
|
||||
|
||||
#: ../../crm/acquire_leads/lead_mining.rst:69
|
||||
msgid "More information about `In-App Purchases <https://www.odoo.com/documentation/user/13.0/general/in_app_purchase/in_app_purchase.html?highlight=iap>`__, (IAP)."
|
||||
#: ../../crm/acquire_leads/lead_mining.rst:71
|
||||
msgid ":doc:`In-App Purchases (IAP) <../../general/in_app_purchase/in_app_purchase>`"
|
||||
msgstr ""
|
||||
|
||||
#: ../../crm/acquire_leads/send_quotes.rst:3
|
||||
@ -266,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 ""
|
||||
@ -454,6 +537,54 @@ msgstr ""
|
||||
msgid "The downside of using a softphone on your cell phone is that your calls will not be logged in Odoo as the softphone acts as an independent separate app."
|
||||
msgstr ""
|
||||
|
||||
#: ../../crm/optimize/partner_autocomplete.rst:3
|
||||
msgid "Enrich your contacts base with Partner Autocomplete"
|
||||
msgstr ""
|
||||
|
||||
#: ../../crm/optimize/partner_autocomplete.rst:5
|
||||
msgid "Parter Autocomplete helps you to enrich your contacts database with corporate data. Select one of the companies suggested in the dropdown, and quickly get all the information you need."
|
||||
msgstr ""
|
||||
|
||||
#: ../../crm/optimize/partner_autocomplete.rst:11
|
||||
msgid "Go to :menuselection:`Settings --> Contacts` and activate the *Partner Autocomplete* feature."
|
||||
msgstr ""
|
||||
|
||||
#: ../../crm/optimize/partner_autocomplete.rst:18
|
||||
msgid "Enrich your contacts with corporate data"
|
||||
msgstr ""
|
||||
|
||||
#: ../../crm/optimize/partner_autocomplete.rst:22
|
||||
msgid "From any module, once you start to create a new contact typing the name of it, the system will suggest a potential match. If you select it, the contact will be populated with corporate data."
|
||||
msgstr ""
|
||||
|
||||
#: ../../crm/optimize/partner_autocomplete.rst:23
|
||||
msgid "For example, after typing *Odoo*, you will get the following information:"
|
||||
msgstr ""
|
||||
|
||||
#: ../../crm/optimize/partner_autocomplete.rst:33
|
||||
msgid "Partner Autocomplete also works if you enter a VAT number instead of a company name."
|
||||
msgstr ""
|
||||
|
||||
#: ../../crm/optimize/partner_autocomplete.rst:39
|
||||
msgid "*Partner Autocomplete* is an *In-App Purchase (IAP)* service, which requires prepaid credits to be used. Each request will consume one credit."
|
||||
msgstr ""
|
||||
|
||||
#: ../../crm/optimize/partner_autocomplete.rst:41
|
||||
msgid "To buy credits, go to :menuselection:`Settings --> Contacts --> Partner Autocomplete or Odoo IAP --> View My Services` and select a package."
|
||||
msgstr ""
|
||||
|
||||
#: ../../crm/optimize/partner_autocomplete.rst:44
|
||||
msgid "If you run out of credits, the only information that will be populated when clicking on the suggested company will be the website link and the logo."
|
||||
msgstr ""
|
||||
|
||||
#: ../../crm/optimize/partner_autocomplete.rst:46
|
||||
msgid "If you are on Odoo Online (SAAS) and you have the Enterprise version, you benefit from free trial credits to test the feature."
|
||||
msgstr ""
|
||||
|
||||
#: ../../crm/optimize/partner_autocomplete.rst:48
|
||||
msgid "Learn about our *Privacy Policy* `here <https://iap.odoo.com/privacy#header_2>`_."
|
||||
msgstr ""
|
||||
|
||||
#: ../../crm/optimize/setup.rst:3
|
||||
msgid "Configure your VOIP Asterisk server for Odoo"
|
||||
msgstr ""
|
||||
@ -622,70 +753,34 @@ msgstr ""
|
||||
msgid "In Odoo, the configuration should be done in the user's preferences."
|
||||
msgstr ""
|
||||
|
||||
#: ../../crm/optimize/setup.rst:206
|
||||
msgid "The SIP Login/Browser's Extension is the number you configured previously in the sip.conf file. In our example, 1060. The SIP Password is the secret you chose in the sip.conf file. The extension of your office's phone is not a required field but it is used if you want to transfer your call from Odoo to an external phone also configured in the sip.conf file."
|
||||
#: ../../crm/optimize/setup.rst:210
|
||||
msgid "The SIP Login/Browser's Extension is the number you configured previously in the sip.conf file (in our example: 1060)."
|
||||
msgstr ""
|
||||
|
||||
#: ../../crm/optimize/setup.rst:212
|
||||
msgid "The configuration should also be done in the sale settings under the title \"PBX Configuration\". You need to put the IP you define in the http.conf file and the WebSocket should be: ws://127.0.0.1:8088/ws. The part \"127.0.0.1\" needs to be the same as the IP defined previously and the \"8088\" is the port you defined in the http.conf file."
|
||||
msgid "The SIP Password is the secret you chose in the sip.conf file."
|
||||
msgstr ""
|
||||
|
||||
#: ../../crm/optimize/setup.rst:214
|
||||
msgid "The extension of your office's phone is not a required field but it is used if you want to transfer your call from Odoo to an external phone also configured in the sip.conf file."
|
||||
msgstr ""
|
||||
|
||||
#: ../../crm/optimize/setup.rst:217
|
||||
msgid "The configuration should also be done in the General Settings under the \"Integrations\" section."
|
||||
msgstr ""
|
||||
|
||||
#: ../../crm/optimize/setup.rst:222
|
||||
msgid "The PBX Server IP should be the same as the IP you define in the http.conf file."
|
||||
msgstr ""
|
||||
|
||||
#: ../../crm/optimize/setup.rst:224
|
||||
msgid "The WebSocket should be: ws://localhost:XXXX/ws where \"localhost\" needs to be the same as the IP defined previously and \"XXXX\" needs to be the port defined in the http.conf file."
|
||||
msgstr ""
|
||||
|
||||
#: ../../crm/performance.rst:3
|
||||
msgid "Analyze performance"
|
||||
msgstr ""
|
||||
|
||||
#: ../../crm/performance/turnover.rst:3
|
||||
msgid "Get an accurate probable turnover"
|
||||
msgstr ""
|
||||
|
||||
#: ../../crm/performance/turnover.rst:5
|
||||
msgid "As you progress in your sales cycle, and move from one stage to another, you can expect to have more precise information about a given opportunity giving you an better idea of the probability of closing it, this is important to see your expected turnover in your various reports."
|
||||
msgstr ""
|
||||
|
||||
#: ../../crm/performance/turnover.rst:11
|
||||
msgid "Configure your kanban stages"
|
||||
msgstr ""
|
||||
|
||||
#: ../../crm/performance/turnover.rst:13
|
||||
msgid "By default, Odoo Kanban view has four stages: New, Qualified, Proposition, Won. Respectively with a 10, 30, 70 and 100% probability of success. You can add stages as well as edit them. By refining default probability of success for your business on stages, you can make your probable turnover more and more accurate."
|
||||
msgstr ""
|
||||
|
||||
#: ../../crm/performance/turnover.rst:25
|
||||
msgid "Every one of your opportunities will have the probability set by default but you can modify them manually of course."
|
||||
msgstr ""
|
||||
|
||||
#: ../../crm/performance/turnover.rst:29
|
||||
msgid "Set your opportunity expected revenue & closing date"
|
||||
msgstr ""
|
||||
|
||||
#: ../../crm/performance/turnover.rst:31
|
||||
msgid "When you get information on a prospect, it is important to set an expected revenue and expected closing date. This will let you see your total expected revenue by stage as well as give a more accurate probable turnover."
|
||||
msgstr ""
|
||||
|
||||
#: ../../crm/performance/turnover.rst:40
|
||||
msgid "See the overdue or closing soon opportunities"
|
||||
msgstr ""
|
||||
|
||||
#: ../../crm/performance/turnover.rst:42
|
||||
msgid "In your pipeline, you can filter opportunities by how soon they will be closing, letting you prioritize."
|
||||
msgstr ""
|
||||
|
||||
#: ../../crm/performance/turnover.rst:48
|
||||
msgid "As a sales manager, this tool can also help you see potential ways to improve your sale process, for example a lot of opportunities in early stages but with near closing date might indicate an issue."
|
||||
msgstr ""
|
||||
|
||||
#: ../../crm/performance/turnover.rst:53
|
||||
msgid "View your total expected revenue and probable turnover"
|
||||
msgstr ""
|
||||
|
||||
#: ../../crm/performance/turnover.rst:55
|
||||
msgid "While in your Kanban view you can see the expected revenue for each of your stages. This is based on each opportunity expected revenue that you set."
|
||||
msgstr ""
|
||||
|
||||
#: ../../crm/performance/turnover.rst:62
|
||||
msgid "As a manager you can go to :menuselection:`CRM --> Reporting --> Pipeline Analysis` by default *Probable Turnover* is set as a measure. This report will take into account the revenue you set on each opportunity but also the probability they will close. This gives you a much better idea of your expected revenue allowing you to make plans and set targets."
|
||||
msgstr ""
|
||||
|
||||
#: ../../crm/performance/win_loss.rst:3
|
||||
msgid "Check your Win/Loss Ratio"
|
||||
msgstr ""
|
||||
|
||||
@ -8,7 +8,7 @@ msgid ""
|
||||
msgstr ""
|
||||
"Project-Id-Version: Odoo 13.0\n"
|
||||
"Report-Msgid-Bugs-To: \n"
|
||||
"POT-Creation-Date: 2019-11-20 10:20+0100\n"
|
||||
"POT-Creation-Date: 2020-09-22 16:26+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
|
||||
@ -160,7 +160,7 @@ msgstr ""
|
||||
msgid "Once you are ready and you have validated all your tests, you can click again on the Upgrade button and confirm by clicking on Upgrade (the button with the little rocket!) to switch your production database to the new version. Your database will then be taken offline within the next 10 minutes and will be upgraded automatically; you receive a confirmation e-mail once the process is completed."
|
||||
msgstr ""
|
||||
|
||||
#: ../../db_management/db_online.rst:139
|
||||
#: ../../db_management/db_online.rst:140
|
||||
msgid "Your database will be taken offline during the upgrade (usually between 30min up to several hours for big databases), so make sure to plan your migration during non-business hours."
|
||||
msgstr ""
|
||||
|
||||
@ -204,51 +204,51 @@ msgstr ""
|
||||
msgid "After a few seconds, you will be logged in your duplicated database. Notice that the url uses the name you chose for your duplicated database."
|
||||
msgstr ""
|
||||
|
||||
#: ../../db_management/db_online.rst:179
|
||||
#: ../../db_management/db_online.rst:180
|
||||
msgid "Duplicate databases expire automatically after 15 days."
|
||||
msgstr ""
|
||||
|
||||
#: ../../db_management/db_online.rst:187
|
||||
#: ../../db_management/db_online.rst:188
|
||||
msgid "Rename a Database"
|
||||
msgstr ""
|
||||
|
||||
#: ../../db_management/db_online.rst:189
|
||||
#: ../../db_management/db_online.rst:190
|
||||
msgid "To rename your database, make sure you are connected to the database you want to rename, access the `database management page <https://www.odoo.com/my/databases>`__ and click **Rename**. You will have to give a new name to your database, then click **Rename Database**."
|
||||
msgstr ""
|
||||
|
||||
#: ../../db_management/db_online.rst:200
|
||||
#: ../../db_management/db_online.rst:201
|
||||
msgid "Deleting a Database"
|
||||
msgstr ""
|
||||
|
||||
#: ../../db_management/db_online.rst:202
|
||||
#: ../../db_management/db_online.rst:203
|
||||
msgid "You can only delete databases of which you are the administrator."
|
||||
msgstr ""
|
||||
|
||||
#: ../../db_management/db_online.rst:204
|
||||
#: ../../db_management/db_online.rst:205
|
||||
msgid "When you delete your database all the data will be permanently lost. The deletion is instant and for all the Users. We advise you to do an instant backup of your database before deleting it, since the last automated daily backup may be several hours old at that point."
|
||||
msgstr ""
|
||||
|
||||
#: ../../db_management/db_online.rst:210
|
||||
#: ../../db_management/db_online.rst:211
|
||||
msgid "From the `database management page <https://www.odoo.com/my/databases>`__, on the line of the database you want to delete, click on the \"Delete\" button."
|
||||
msgstr ""
|
||||
|
||||
#: ../../db_management/db_online.rst:217
|
||||
#: ../../db_management/db_online.rst:218
|
||||
msgid "Read carefully the warning message that will appear and proceed only if you fully understand the implications of deleting a database:"
|
||||
msgstr ""
|
||||
|
||||
#: ../../db_management/db_online.rst:223
|
||||
#: ../../db_management/db_online.rst:224
|
||||
msgid "After a few seconds, the database will be deleted and the page will reload automatically."
|
||||
msgstr ""
|
||||
|
||||
#: ../../db_management/db_online.rst:227
|
||||
#: ../../db_management/db_online.rst:228
|
||||
msgid "If you need to re-use this database name, it will be immediately available."
|
||||
msgstr ""
|
||||
|
||||
#: ../../db_management/db_online.rst:229
|
||||
#: ../../db_management/db_online.rst:230
|
||||
msgid "It is not possible to delete a database if it is expired or linked to a Subscription. In these cases contact `Odoo Support <https://www.odoo.com/help>`__"
|
||||
msgstr ""
|
||||
|
||||
#: ../../db_management/db_online.rst:233
|
||||
#: ../../db_management/db_online.rst:234
|
||||
msgid "If you want to delete your Account, please contact `Odoo Support <https://www.odoo.com/help>`__"
|
||||
msgstr ""
|
||||
|
||||
@ -274,7 +274,7 @@ msgstr ""
|
||||
|
||||
#: ../../db_management/db_premise.rst:31
|
||||
#: ../../db_management/db_premise.rst:110
|
||||
#: ../../db_management/db_premise.rst:143
|
||||
#: ../../db_management/db_premise.rst:138
|
||||
msgid "Solutions"
|
||||
msgstr ""
|
||||
|
||||
@ -307,7 +307,7 @@ msgid "Do you have the updated version of Odoo 9?"
|
||||
msgstr ""
|
||||
|
||||
#: ../../db_management/db_premise.rst:61
|
||||
#: ../../db_management/db_premise.rst:176
|
||||
#: ../../db_management/db_premise.rst:171
|
||||
msgid "From July 2016 onward, Odoo 9 now automatically change the uuid of a duplicated database; a manual operation is no longer required."
|
||||
msgstr ""
|
||||
|
||||
@ -359,60 +359,56 @@ msgstr ""
|
||||
msgid "**Add more users** on your subscription: follow the link and Validate the upsell quotation and pay for the extra users."
|
||||
msgstr ""
|
||||
|
||||
#: ../../db_management/db_premise.rst:115
|
||||
msgid "or"
|
||||
#: ../../db_management/db_premise.rst:114
|
||||
msgid "**Deactivate users** as explained in this `documentation <documentation.html#deactivating-users>`_ and **Reject** the upsell quotation."
|
||||
msgstr ""
|
||||
|
||||
#: ../../db_management/db_premise.rst:117
|
||||
msgid "**Deactivate users** as explained in this `Documentation <https://www.odoo.com /documentation/user/13.0/db_management/documentation.html#deactivating-users>`__ and **Reject** the upsell quotation."
|
||||
msgstr ""
|
||||
|
||||
#: ../../db_management/db_premise.rst:122
|
||||
msgid "Once your database has the correct number of users, the expiration message will disappear automatically after a few days, when the next verification occurs. We understand that it can be a bit frightening to see the countdown, so you can :ref:`force an Update Notification <force_ping>` to make the message disappear right away."
|
||||
msgstr ""
|
||||
|
||||
#: ../../db_management/db_premise.rst:129
|
||||
#: ../../db_management/db_premise.rst:124
|
||||
msgid "Database expired error message"
|
||||
msgstr ""
|
||||
|
||||
#: ../../db_management/db_premise.rst:131
|
||||
#: ../../db_management/db_premise.rst:126
|
||||
msgid "If your database reaches its expiration date before your renew your subscription, you will encounter this message:"
|
||||
msgstr ""
|
||||
|
||||
#: ../../db_management/db_premise.rst:139
|
||||
#: ../../db_management/db_premise.rst:134
|
||||
msgid "This **blocking** message appears after a non-blocking message that lasts 30 days. If you fail to take action before the end of the countdown, the database is expired."
|
||||
msgstr ""
|
||||
|
||||
#: ../../db_management/db_premise.rst:147
|
||||
#: ../../db_management/db_premise.rst:142
|
||||
msgid "Renew your subscription: follow the link and renew your subscription - note that"
|
||||
msgstr ""
|
||||
|
||||
#: ../../db_management/db_premise.rst:146
|
||||
#: ../../db_management/db_premise.rst:141
|
||||
msgid "if you wish to pay by Wire Transfer, your subscription will effectively be renewed only when the payment arrives, which can take a few days. Credit card payments are processed immediately."
|
||||
msgstr ""
|
||||
|
||||
#: ../../db_management/db_premise.rst:149
|
||||
#: ../../db_management/db_premise.rst:144
|
||||
msgid "Contact our `Support <https://www.odoo.com/help>`__"
|
||||
msgstr ""
|
||||
|
||||
#: ../../db_management/db_premise.rst:151
|
||||
#: ../../db_management/db_premise.rst:146
|
||||
msgid "None of those solutions worked for you? Please contact our `Support <https://www.odoo.com/help>`__"
|
||||
msgstr ""
|
||||
|
||||
#: ../../db_management/db_premise.rst:160
|
||||
#: ../../db_management/db_premise.rst:155
|
||||
msgid "Duplicate a database"
|
||||
msgstr ""
|
||||
|
||||
#: ../../db_management/db_premise.rst:162
|
||||
#: ../../db_management/db_premise.rst:157
|
||||
msgid "You can duplicate your database by accessing the database manager on your server (<odoo-server>/web/database/manager). In this page, you can easily duplicate your database (among other things)."
|
||||
msgstr ""
|
||||
|
||||
#: ../../db_management/db_premise.rst:170
|
||||
#: ../../db_management/db_premise.rst:165
|
||||
msgid "When you duplicate a local database, it is **strongly** advised to change the duplicated database's uuid (Unniversally Unique Identifier), since this uuid is how your database identifies itself with our servers. Having two databases with the same uuid could result in invoicing problems or registration problems down the line."
|
||||
msgstr ""
|
||||
|
||||
#: ../../db_management/db_premise.rst:179
|
||||
msgid "The database uuid is currently accessible from the menu **Settings > Technical > System Parameters**, we advise you to use a `uuid generator <https://www.uuidgenerator.net>`__ or to use the unix command ``uuidgen`` to generate a new uuid. You can then simply replace it like any other record by clicking on it and using the edit button."
|
||||
#: ../../db_management/db_premise.rst:174
|
||||
msgid "The database uuid is currently accessible from the menu :menuselection:`Settings --> Technical --> System Parameters`, we advise you to use a `uuid generator <https://www.uuidtools.com>`_ or to use the unix command ``uuidgen`` to generate a new uuid. You can then simply replace it like any other record by clicking on it and using the edit button."
|
||||
msgstr ""
|
||||
|
||||
#: ../../db_management/documentation.rst:7
|
||||
|
||||
@ -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-22 16:26+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,415 +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:5
|
||||
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>`__."
|
||||
#: ../../discuss/advanced/email_servers.rst:3
|
||||
msgid "How to Use my Mail Server to Send and Receive Emails in Odoo"
|
||||
msgstr ""
|
||||
|
||||
#: ../../discuss/email_servers.rst:9
|
||||
#: ../../discuss/advanced/email_servers.rst:6
|
||||
msgid "If you are a user of Odoo Online or Odoo.sh..."
|
||||
msgstr ""
|
||||
|
||||
#: ../../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/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/advanced/email_servers.rst:16
|
||||
msgid "Scope of this documentation"
|
||||
msgstr ""
|
||||
|
||||
#: ../../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/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:15
|
||||
#: ../../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:18
|
||||
msgid "Office 365 email servers don't allow easiliy 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."
|
||||
#: ../../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:24
|
||||
#: ../../discuss/advanced/email_servers.rst:40
|
||||
msgid "How to manage outbound messages"
|
||||
msgstr ""
|
||||
|
||||
#: ../../discuss/email_servers.rst:26
|
||||
#: ../../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:31
|
||||
#: ../../discuss/advanced/email_servers.rst:46
|
||||
msgid "Here is a typical configuration for a G Suite server."
|
||||
msgstr ""
|
||||
|
||||
#: ../../discuss/email_servers.rst:36
|
||||
#: ../../discuss/advanced/email_servers.rst:51
|
||||
msgid "Then set your email domain name in the General Settings."
|
||||
msgstr ""
|
||||
|
||||
#: ../../discuss/email_servers.rst:39
|
||||
#: ../../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/advanced/email_servers.rst:58
|
||||
msgid "In addition to that, enable the IMAP setting on your Gmail account."
|
||||
msgstr ""
|
||||
|
||||
#: ../../discuss/advanced/email_servers.rst:62
|
||||
msgid "Can I use an Office 365 server"
|
||||
msgstr ""
|
||||
|
||||
#: ../../discuss/email_servers.rst:40
|
||||
#: ../../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:43
|
||||
#: ../../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:47
|
||||
#: ../../discuss/advanced/email_servers.rst:70
|
||||
msgid "How to use a G Suite server"
|
||||
msgstr ""
|
||||
|
||||
#: ../../discuss/email_servers.rst:48
|
||||
#: ../../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:55
|
||||
#: ../../discuss/advanced/email_servers.rst:78
|
||||
msgid "Be SPF-compliant"
|
||||
msgstr ""
|
||||
|
||||
#: ../../discuss/email_servers.rst:56
|
||||
#: ../../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:60
|
||||
#: ../../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:62
|
||||
#: ../../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:66
|
||||
#: ../../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:69
|
||||
#: ../../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:72
|
||||
#: ../../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:77
|
||||
#: ../../discuss/advanced/email_servers.rst:100
|
||||
msgid "Allow DKIM"
|
||||
msgstr ""
|
||||
|
||||
#: ../../discuss/email_servers.rst:78
|
||||
#: ../../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:86
|
||||
#: ../../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:88
|
||||
#: ../../discuss/advanced/email_servers.rst:115
|
||||
msgid "Odoo relies on generic email aliases to fetch incoming messages."
|
||||
msgstr ""
|
||||
|
||||
#: ../../discuss/email_servers.rst:90
|
||||
#: ../../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:94
|
||||
#: ../../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:98
|
||||
#: ../../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:101
|
||||
#: ../../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:103
|
||||
#: ../../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:105
|
||||
#: ../../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:107
|
||||
#: ../../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:109
|
||||
#: ../../discuss/advanced/email_servers.rst:136
|
||||
msgid "etc."
|
||||
msgstr ""
|
||||
|
||||
#: ../../discuss/email_servers.rst:111
|
||||
#: ../../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:115
|
||||
#: ../../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:117
|
||||
#: ../../discuss/advanced/email_servers.rst:144
|
||||
msgid "Set your domain name in the General Settings."
|
||||
msgstr ""
|
||||
|
||||
#: ../../discuss/email_servers.rst:122
|
||||
#: ../../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 provider’s 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:131
|
||||
#: ../../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:138
|
||||
msgid "All the aliases are customizable in Odoo. Object aliases can be edited from their respective configuration view. To edit catchall and bounce aliases, you first need to activate the developer mode from the Settings Dashboard."
|
||||
#: ../../discuss/advanced/email_servers.rst:168
|
||||
msgid "All the aliases are customizable in Odoo."
|
||||
msgstr ""
|
||||
|
||||
#: ../../discuss/email_servers.rst:146
|
||||
msgid "Then refresh your screen and go to :menuselection:`Settings --> Technical --> Parameters --> System Parameters` to customize the aliases (*mail.catchall.alias* & * mail.bounce.alias*)."
|
||||
#: ../../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:153
|
||||
msgid "By default inbound messages are fetched every 5 minutes in Odoo on-premise. You can change this value in developer mode. Go to :menuselection:`Settings --> Technical --> Automation --> Scheduled Actions` and look for *Mail: Fetchmail Service*."
|
||||
#: ../../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/mail_twitter.rst:3
|
||||
msgid "How to follow Twitter feed from Odoo"
|
||||
#: ../../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: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:3
|
||||
msgid "Email Templates"
|
||||
msgstr ""
|
||||
|
||||
#: ../../discuss/mail_twitter.rst:13
|
||||
msgid "Setting up the App on Twitter's side"
|
||||
#: ../../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: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:12
|
||||
msgid "Enable it and understand a few concepts"
|
||||
msgstr ""
|
||||
|
||||
#: ../../discuss/mail_twitter.rst:19
|
||||
msgid "Name: this is the name of the application on Twitter"
|
||||
#: ../../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: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: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: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: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: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: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 author’s email alias, if configured, or email address."
|
||||
msgstr ""
|
||||
|
||||
#: ../../discuss/mail_twitter.rst:33
|
||||
msgid "Getting the API key and secret"
|
||||
#: ../../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:35
|
||||
msgid "When on the App dashboard, switch to the **Keys and Access Tokens** tab."
|
||||
#: ../../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: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:37
|
||||
msgid "Writing content including placeholder expressions"
|
||||
msgstr ""
|
||||
|
||||
#: ../../discuss/mentions.rst:3
|
||||
msgid "How to grab attention of other users in my messages"
|
||||
#: ../../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: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."
|
||||
#: ../../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: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 company’s 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 task’s :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 contact’s 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 n available calendar available, 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 channel’s 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 group’s 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 ""
|
||||
|
||||
|
||||
@ -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-22 16:26+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,236 +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** and your **API Transaction Key**."
|
||||
msgstr ""
|
||||
|
||||
#: ../../ecommerce/shopper_experience/authorize.rst:39
|
||||
msgid "To get those credentials in Authorize.Net, you can rely on *API Login ID and Transaction Key* video of `Authorize.Net Video Tutorials <https://www.authorize.net/videos/>`__. Such videos give meaningful insights about how to set up your Authorize.Net account according to your needs."
|
||||
msgstr ""
|
||||
|
||||
#: ../../ecommerce/shopper_experience/authorize.rst:47
|
||||
msgid "Go live"
|
||||
msgstr ""
|
||||
|
||||
#: ../../ecommerce/shopper_experience/authorize.rst:48
|
||||
msgid "Your configuration is now ready! You can make Authorize.Net visible on your merchant interface and activate the **Production** mode."
|
||||
msgstr ""
|
||||
|
||||
#: ../../ecommerce/shopper_experience/authorize.rst:55
|
||||
msgid "Credentials provided by Authorize.net are different for both test and production mode. Don't forget to update them in Odoo when you turn on the production mode."
|
||||
msgstr ""
|
||||
|
||||
#: ../../ecommerce/shopper_experience/authorize.rst:61
|
||||
msgid "Assess Authorize.Net as payment solution"
|
||||
msgstr ""
|
||||
|
||||
#: ../../ecommerce/shopper_experience/authorize.rst:62
|
||||
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:64
|
||||
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:68
|
||||
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:71
|
||||
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:76
|
||||
msgid ":doc:`payment`"
|
||||
msgstr ""
|
||||
|
||||
#: ../../ecommerce/shopper_experience/authorize.rst:77
|
||||
#: ../../ecommerce/shopper_experience/payment.rst:111
|
||||
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 ready, make it visible in the payment interface and activate the **Production** mode."
|
||||
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 developer mode."
|
||||
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 ""
|
||||
@ -819,226 +589,26 @@ msgstr ""
|
||||
msgid "When the order is confirmed you can also have an invoice automatically issued and paid. This fully-automated made for businesses that invoice orders straight on."
|
||||
msgstr ""
|
||||
|
||||
#: ../../ecommerce/shopper_experience/payment_acquirer.rst:53
|
||||
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 `How to register credit card payments <../../accounting/receivables/customer_payments/credit_cards.html>`__)."
|
||||
#: ../../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:`../../general/payment_acquirers/payment_acquirers`)."
|
||||
msgstr ""
|
||||
|
||||
#: ../../ecommerce/shopper_experience/payment_acquirer.rst:64
|
||||
#: ../../ecommerce/shopper_experience/payment_acquirer.rst:63
|
||||
msgid "Capture the payment after the delivery"
|
||||
msgstr ""
|
||||
|
||||
#: ../../ecommerce/shopper_experience/payment_acquirer.rst:65
|
||||
#: ../../ecommerce/shopper_experience/payment_acquirer.rst:64
|
||||
msgid "With this mode, the order is confirmed but the amount is kept on hold. Once the delivery processed, you can capture the payment from Odoo. This mode is only available with Authorize.net."
|
||||
msgstr ""
|
||||
|
||||
#: ../../ecommerce/shopper_experience/payment_acquirer.rst:72
|
||||
#: ../../ecommerce/shopper_experience/payment_acquirer.rst:71
|
||||
msgid "To capture the payment, open the transaction from the order. Then click *Capture Transaction*."
|
||||
msgstr ""
|
||||
|
||||
#: ../../ecommerce/shopper_experience/payment_acquirer.rst:78
|
||||
#: ../../ecommerce/shopper_experience/payment_acquirer.rst:77
|
||||
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 doesn’t charge any subscription fee and creating an account is very easy. That’s 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 `Paypayl 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:18
|
||||
msgid "Settings in Paypal"
|
||||
msgstr ""
|
||||
|
||||
#: ../../ecommerce/shopper_experience/paypal.rst:21
|
||||
msgid "First, let’s see how to set up your Paypal account in order to build a seamless customer experience with Odoo."
|
||||
msgstr ""
|
||||
|
||||
#: ../../ecommerce/shopper_experience/paypal.rst:23
|
||||
msgid "Log in and open the settings. Go to *Products & Services > Website payments* and click *Update* on *Website preferences*."
|
||||
msgstr ""
|
||||
|
||||
#: ../../ecommerce/shopper_experience/paypal.rst:29
|
||||
msgid "Auto Return"
|
||||
msgstr ""
|
||||
|
||||
#: ../../ecommerce/shopper_experience/paypal.rst:31
|
||||
msgid "*Auto Return* automatically redirects your customers to Odoo once the payment is processed. Check *Auto Return* and enter your domain name \"/shop/confirmation\" as *Return URL* (e.g. https://yourcompany.odoo.com/shop/confirmation)."
|
||||
msgstr ""
|
||||
|
||||
#: ../../ecommerce/shopper_experience/paypal.rst:36
|
||||
msgid "This URL is requested in Paypal but not used in practice as Odoo transmits it at each transaction. Don’t worry if you manage several sales channels or Odoo databases."
|
||||
msgstr ""
|
||||
|
||||
#: ../../ecommerce/shopper_experience/paypal.rst:44
|
||||
msgid "Payment Data Transfer (PDT)"
|
||||
msgstr ""
|
||||
|
||||
#: ../../ecommerce/shopper_experience/paypal.rst:46
|
||||
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:54
|
||||
msgid "Paypal Account Optional"
|
||||
msgstr ""
|
||||
|
||||
#: ../../ecommerce/shopper_experience/paypal.rst:56
|
||||
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:63
|
||||
msgid "Instant Payment Notification (IPN)"
|
||||
msgstr ""
|
||||
|
||||
#: ../../ecommerce/shopper_experience/paypal.rst:65
|
||||
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. That’s 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:72
|
||||
msgid "To activate IPN, get back to *Website payments* menu and click *Update* in *Instant Payment Notification*."
|
||||
msgstr ""
|
||||
|
||||
#: ../../ecommerce/shopper_experience/paypal.rst:75
|
||||
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:81
|
||||
msgid "Payment Messages Format"
|
||||
msgstr ""
|
||||
|
||||
#: ../../ecommerce/shopper_experience/paypal.rst:83
|
||||
msgid "Finally make sure the encoding format of payment messages is correctly set. Go to *PayPal button language encoding*."
|
||||
msgstr ""
|
||||
|
||||
#: ../../ecommerce/shopper_experience/paypal.rst:89
|
||||
msgid "Click *More Options* and set the two default encoding formats as *UTF-8*."
|
||||
msgstr ""
|
||||
|
||||
#: ../../ecommerce/shopper_experience/paypal.rst:98
|
||||
msgid "Your Paypal account is ready!"
|
||||
msgstr ""
|
||||
|
||||
#: ../../ecommerce/shopper_experience/paypal.rst:100
|
||||
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:104
|
||||
msgid "Settings in Odoo"
|
||||
msgstr ""
|
||||
|
||||
#: ../../ecommerce/shopper_experience/paypal.rst:107
|
||||
msgid "Activation"
|
||||
msgstr ""
|
||||
|
||||
#: ../../ecommerce/shopper_experience/paypal.rst:109
|
||||
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:113
|
||||
msgid "Credentials"
|
||||
msgstr ""
|
||||
|
||||
#: ../../ecommerce/shopper_experience/paypal.rst:115
|
||||
msgid "Odoo requires three Paypal credentials:"
|
||||
msgstr ""
|
||||
|
||||
#: ../../ecommerce/shopper_experience/paypal.rst:117
|
||||
msgid "*Email ID* is your login email address in Paypal."
|
||||
msgstr ""
|
||||
|
||||
#: ../../ecommerce/shopper_experience/paypal.rst:119
|
||||
msgid "*Merchant ID* can be found in the settings of your Paypal account, in *Profile > About the business*."
|
||||
msgstr ""
|
||||
|
||||
#: ../../ecommerce/shopper_experience/paypal.rst:121
|
||||
msgid "*Paypal PDT Token* is given in *Website payments* configuration as explained here above."
|
||||
msgstr ""
|
||||
|
||||
#: ../../ecommerce/shopper_experience/paypal.rst:127
|
||||
msgid "Transaction fees"
|
||||
msgstr ""
|
||||
|
||||
#: ../../ecommerce/shopper_experience/paypal.rst:129
|
||||
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:132
|
||||
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:138
|
||||
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:141
|
||||
msgid "..note:: `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:145
|
||||
msgid "Go live!"
|
||||
msgstr ""
|
||||
|
||||
#: ../../ecommerce/shopper_experience/paypal.rst:147
|
||||
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:156
|
||||
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:165
|
||||
msgid "Test environment"
|
||||
msgstr ""
|
||||
|
||||
#: ../../ecommerce/shopper_experience/paypal.rst:167
|
||||
msgid "You can test the entire payment flow in Odoo thanks to Paypal Sandbox accounts."
|
||||
msgstr ""
|
||||
|
||||
#: ../../ecommerce/shopper_experience/paypal.rst:169
|
||||
msgid "Log in to `Paypal Developer Site <https://developer.paypal.com/>`__ with your Paypal credentials."
|
||||
msgstr ""
|
||||
|
||||
#: ../../ecommerce/shopper_experience/paypal.rst:171
|
||||
msgid "This will create two sandbox accounts:"
|
||||
msgstr ""
|
||||
|
||||
#: ../../ecommerce/shopper_experience/paypal.rst:173
|
||||
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:175
|
||||
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:177
|
||||
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:183
|
||||
msgid "Run a test transaction from Odoo using the sandbox personal account."
|
||||
msgstr ""
|
||||
|
||||
#: ../../ecommerce/shopper_experience/paypal.rst:185
|
||||
msgid "See also"
|
||||
msgstr ""
|
||||
|
||||
#: ../../ecommerce/shopper_experience/paypal.rst:187
|
||||
msgid "`How to manage orders paid with payment acquirers <https://www.odoo.com/documentation/user/13.0/ecommerce/shopper_experience/payment.html>`__"
|
||||
msgstr ""
|
||||
|
||||
#: ../../ecommerce/shopper_experience/paypal.rst:189
|
||||
msgid "`How to manage orders paid with payment acquirers <https://www.odoo.com/documentation/user/13.0/ecommerce/shopper_experience/payment_acquirer.html>`__"
|
||||
msgstr ""
|
||||
|
||||
#: ../../ecommerce/shopper_experience/portal.rst:3
|
||||
msgid "How customers can access their customer account"
|
||||
msgstr ""
|
||||
@ -1071,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 ""
|
||||
|
||||
207
locale/sources/email_marketing.pot
Normal file
207
locale/sources/email_marketing.pot
Normal file
@ -0,0 +1,207 @@
|
||||
# SOME DESCRIPTIVE TITLE.
|
||||
# Copyright (C) 2015-TODAY, Odoo S.A.
|
||||
# This file is distributed under the same license as the Odoo package.
|
||||
# FIRST AUTHOR <EMAIL@ADDRESS>, YEAR.
|
||||
#
|
||||
#, fuzzy
|
||||
msgid ""
|
||||
msgstr ""
|
||||
"Project-Id-Version: Odoo 13.0\n"
|
||||
"Report-Msgid-Bugs-To: \n"
|
||||
"POT-Creation-Date: 2020-09-22 16:26+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"
|
||||
"MIME-Version: 1.0\n"
|
||||
"Content-Type: text/plain; charset=UTF-8\n"
|
||||
"Content-Transfer-Encoding: 8bit\n"
|
||||
|
||||
#: ../../email_marketing.rst:5
|
||||
msgid "Email Marketing"
|
||||
msgstr ""
|
||||
|
||||
#: ../../email_marketing/overview.rst:3
|
||||
msgid "Overview"
|
||||
msgstr ""
|
||||
|
||||
#: ../../email_marketing/overview/mailing_lists.rst:3
|
||||
msgid "Work with Mailing Lists"
|
||||
msgstr ""
|
||||
|
||||
#: ../../email_marketing/overview/mailing_lists.rst:5
|
||||
msgid "Mailing lists can be a goldmine for your company’s marketing department as they can provide leads for sales, focus groups for testing new products, and consumers to provide feedback on satisfaction, for example."
|
||||
msgstr ""
|
||||
|
||||
#: ../../email_marketing/overview/mailing_lists.rst:10
|
||||
msgid "Create mailing lists"
|
||||
msgstr ""
|
||||
|
||||
#: ../../email_marketing/overview/mailing_lists.rst:12
|
||||
msgid "Go to :menuselection:`Mailing lists --> Mailing lists --> Create`. Enable the option *Is Public* to make the list visible for users when unsubscribing."
|
||||
msgstr ""
|
||||
|
||||
#: ../../email_marketing/overview/mailing_lists.rst:19
|
||||
msgid "Once your mailing list is created, you can manually add contacts clicking on *Create*. *Import* a list of contacts if you have it from a previous tool."
|
||||
msgstr ""
|
||||
|
||||
#: ../../email_marketing/overview/mailing_lists.rst:23
|
||||
msgid "Linking a mailing list to my website"
|
||||
msgstr ""
|
||||
|
||||
#: ../../email_marketing/overview/mailing_lists.rst:26
|
||||
msgid "Create a mailing list called Newsletter, as you use this strategy to advertise and communicate new ideas to subscribers interested in listening."
|
||||
msgstr ""
|
||||
|
||||
#: ../../email_marketing/overview/mailing_lists.rst:27
|
||||
msgid "Go to your *Website*, add a *Newsletter* block and choose the respective mailing list."
|
||||
msgstr ""
|
||||
|
||||
#: ../../email_marketing/overview/mailing_lists.rst:34
|
||||
msgid "Contacts"
|
||||
msgstr ""
|
||||
|
||||
#: ../../email_marketing/overview/mailing_lists.rst:36
|
||||
msgid "Under :menuselection:`Mailing Lists --> Mailing List Contacts` see a list of all contacts under all your mailing lists, and the ones you individually created here."
|
||||
msgstr ""
|
||||
|
||||
#: ../../email_marketing/overview/mailing_lists.rst:43
|
||||
msgid "Open a contact form to see or add different mailing lists to which the contact is or will be part of."
|
||||
msgstr ""
|
||||
|
||||
#: ../../email_marketing/overview/mailing_lists.rst:51
|
||||
#: ../../email_marketing/overview/manage_unsubscriptions.rst:46
|
||||
msgid ":doc:`send_emails`"
|
||||
msgstr ""
|
||||
|
||||
#: ../../email_marketing/overview/manage_unsubscriptions.rst:3
|
||||
msgid "Manage Unsubscriptions and Blacklist"
|
||||
msgstr ""
|
||||
|
||||
#: ../../email_marketing/overview/manage_unsubscriptions.rst:5
|
||||
msgid "It is best practice, and legally required, to allow recipients to unsubscribe from mailing lists as you do not want your audience to think that your company is using any tactics that are dishonest or spammy."
|
||||
msgstr ""
|
||||
|
||||
#: ../../email_marketing/overview/manage_unsubscriptions.rst:10
|
||||
msgid "Enable the Blacklist feature"
|
||||
msgstr ""
|
||||
|
||||
#: ../../email_marketing/overview/manage_unsubscriptions.rst:12
|
||||
msgid "Go to :menuselection:`Configuration --> Settings` and enable the option *Blacklist Option when Unsubscribing*."
|
||||
msgstr ""
|
||||
|
||||
#: ../../email_marketing/overview/manage_unsubscriptions.rst:19
|
||||
msgid "Now, once the user clicks on the *Unsubscribe* link on your email, he is redirected to the following page:"
|
||||
msgstr ""
|
||||
|
||||
#: ../../email_marketing/overview/manage_unsubscriptions.rst:28
|
||||
msgid "After clicking on the unsubscribe button when using the test feature, you are sent to an error page (*error 403 - Access Denied*). If you want to be sure the link is working properly, create your mass mail and send it only to a personal email."
|
||||
msgstr ""
|
||||
|
||||
#: ../../email_marketing/overview/manage_unsubscriptions.rst:32
|
||||
msgid "In addition to having the option of unsubscribing from specific mailing lists, the user can also blacklist himself, meaning that he will not receive *any* more emails from you."
|
||||
msgstr ""
|
||||
|
||||
#: ../../email_marketing/overview/manage_unsubscriptions.rst:36
|
||||
msgid "The mailing list has to be configured as *Public* in order to be visible for users."
|
||||
msgstr ""
|
||||
|
||||
#: ../../email_marketing/overview/manage_unsubscriptions.rst:38
|
||||
msgid "Under :menuselection:`Configuration --> Blacklist`, blacklisted email addresses are shown."
|
||||
msgstr ""
|
||||
|
||||
#: ../../email_marketing/overview/manage_unsubscriptions.rst:39
|
||||
msgid "When opening the record, as a *Log note*, a description-history is kept."
|
||||
msgstr ""
|
||||
|
||||
#: ../../email_marketing/overview/manage_unsubscriptions.rst:47
|
||||
msgid ":doc:`mailing_lists`"
|
||||
msgstr ""
|
||||
|
||||
#: ../../email_marketing/overview/send_emails.rst:3
|
||||
msgid "Send Emails Marketing and Manage Campaigns"
|
||||
msgstr ""
|
||||
|
||||
#: ../../email_marketing/overview/send_emails.rst:5
|
||||
msgid "Emails allow you to effectively, and at a low cost, reach a large number of consumers while being able to customize your message in a way that resonates with them. It is measurable, and a call-to-action oriented channel."
|
||||
msgstr ""
|
||||
|
||||
#: ../../email_marketing/overview/send_emails.rst:10
|
||||
msgid "Choose the right target and create the message"
|
||||
msgstr ""
|
||||
|
||||
#: ../../email_marketing/overview/send_emails.rst:12
|
||||
msgid "Go to :menuselection:`Mailings --> Create`."
|
||||
msgstr ""
|
||||
|
||||
#: ../../email_marketing/overview/send_emails.rst:14
|
||||
msgid "Choosing *Contacts* as *Recipients* (for example), allows you to add specifications to match just certain contacts, filtering your target."
|
||||
msgstr ""
|
||||
|
||||
#: ../../email_marketing/overview/send_emails.rst:21
|
||||
msgid "With a trial databases, you have a limit of 50 emails per day; on Odoo SH Cloud Platform the limit is 200. There is a possibility to increase these numbers by contacting Odoo Support. To contact Support, `click here <https://www.odoo.com/help>`_."
|
||||
msgstr ""
|
||||
|
||||
#: ../../email_marketing/overview/send_emails.rst:25
|
||||
msgid "Under *Mail Body*, choose a layout and make the modifications needed by dragging, dropping and double-clicking on content. Note that it is possible to start from scratch selecting the *blank* template option."
|
||||
msgstr ""
|
||||
|
||||
#: ../../email_marketing/overview/send_emails.rst:34
|
||||
msgid "Under *Settings*, you can assign someone else as the responsible sender if you do not want it to be you. To do so, change the email address used as the sender (*Send From*)."
|
||||
msgstr ""
|
||||
|
||||
#: ../../email_marketing/overview/send_emails.rst:37
|
||||
msgid "With the *Reply To* radio button, you can also choose to gather answers either on the respective recipients’ records or on a specific email address. Note that this option is not available if you target mailing contacts or contacts as recipients."
|
||||
msgstr ""
|
||||
|
||||
#: ../../email_marketing/overview/send_emails.rst:45
|
||||
msgid "Test, send or schedule a mailing"
|
||||
msgstr ""
|
||||
|
||||
#: ../../email_marketing/overview/send_emails.rst:53
|
||||
msgid "*Save*: the work is allocated in the *draft* column in the Kanban view. Modifications can be made while being in this stage. The option *Discard* deletes the email."
|
||||
msgstr ""
|
||||
|
||||
#: ../../email_marketing/overview/send_emails.rst:54
|
||||
msgid "Click on *Test* and send your message to one, or even multiple, test contacts to avoid errors."
|
||||
msgstr ""
|
||||
|
||||
#: ../../email_marketing/overview/send_emails.rst:56
|
||||
msgid "*Send* triggers the email with the next run and put the work on the *queue* column in the Kanban view."
|
||||
msgstr ""
|
||||
|
||||
#: ../../email_marketing/overview/send_emails.rst:58
|
||||
msgid "*Schedule* allows you to choose a date and time, and puts the email in the *queue* column in the Kanban view."
|
||||
msgstr ""
|
||||
|
||||
#: ../../email_marketing/overview/send_emails.rst:61
|
||||
msgid "The daily limit is applied for **all emails** sent, in other words, throughout all applications. Therefore, if at the end of the day you have remaining ones to be sent, note that they *will not* be sent automatically the next day. You need to force that by opening the email and clicking on *Retry*."
|
||||
msgstr ""
|
||||
|
||||
#: ../../email_marketing/overview/send_emails.rst:67
|
||||
msgid "Manage campaigns"
|
||||
msgstr ""
|
||||
|
||||
#: ../../email_marketing/overview/send_emails.rst:69
|
||||
msgid "Go to :menuselection:`Configuration --> Settings` and enable *Mailing Campaigns*."
|
||||
msgstr ""
|
||||
|
||||
#: ../../email_marketing/overview/send_emails.rst:71
|
||||
msgid "The campaign option is effective as it allows you to organize your marketing efforts and have a centralized view of its metrics."
|
||||
msgstr ""
|
||||
|
||||
#: ../../email_marketing/overview/send_emails.rst:72
|
||||
msgid "Go to *Campaign* and click on *Create* to start one."
|
||||
msgstr ""
|
||||
|
||||
#: ../../email_marketing/overview/send_emails.rst:80
|
||||
msgid "If you use the SMS and Social Marketing applications, as well as the Push Notification feature, you see the option to create content for those channels. You also see the *Campaign* menu within those applications. All of this is possible because the applications work integrated."
|
||||
msgstr ""
|
||||
|
||||
#: ../../email_marketing/overview/send_emails.rst:85
|
||||
msgid ":doc:`../../discuss/advanced/email_servers`"
|
||||
msgstr ""
|
||||
|
||||
#: ../../email_marketing/overview/send_emails.rst:86
|
||||
msgid ":doc:`../../social_marketing/overview/campaigns`"
|
||||
msgstr ""
|
||||
|
||||
319
locale/sources/events.pot
Normal file
319
locale/sources/events.pot
Normal file
@ -0,0 +1,319 @@
|
||||
# SOME DESCRIPTIVE TITLE.
|
||||
# Copyright (C) 2015-TODAY, Odoo S.A.
|
||||
# This file is distributed under the same license as the Odoo package.
|
||||
# FIRST AUTHOR <EMAIL@ADDRESS>, YEAR.
|
||||
#
|
||||
#, fuzzy
|
||||
msgid ""
|
||||
msgstr ""
|
||||
"Project-Id-Version: Odoo 13.0\n"
|
||||
"Report-Msgid-Bugs-To: \n"
|
||||
"POT-Creation-Date: 2020-09-22 16:26+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"
|
||||
"MIME-Version: 1.0\n"
|
||||
"Content-Type: text/plain; charset=UTF-8\n"
|
||||
"Content-Transfer-Encoding: 8bit\n"
|
||||
|
||||
#: ../../events.rst:5
|
||||
msgid "Events"
|
||||
msgstr ""
|
||||
|
||||
#: ../../events/integrations.rst:3
|
||||
msgid "Integrations"
|
||||
msgstr ""
|
||||
|
||||
#: ../../events/integrations/integration_sms.rst:3
|
||||
msgid "Communicating about my Event using SMS Text Messages"
|
||||
msgstr ""
|
||||
|
||||
#: ../../events/integrations/integration_sms.rst:5
|
||||
msgid "Using SMS as a communication strategy for your event establishes interaction between organizers, attendees, speakers and further targets. It allows your message to be heard whether the goal is to send out reminders, teasers or to advertise."
|
||||
msgstr ""
|
||||
|
||||
#: ../../events/integrations/integration_sms.rst:10
|
||||
#: ../../events/overview/tickets.rst:9
|
||||
#: ../../events/overview/track_talks.rst:9
|
||||
msgid "Configuration"
|
||||
msgstr ""
|
||||
|
||||
#: ../../events/integrations/integration_sms.rst:13
|
||||
msgid "Under *Communication* SMS is a standard feature. That means nothing needs to be enabled or installed."
|
||||
msgstr ""
|
||||
|
||||
#: ../../events/integrations/integration_sms.rst:16
|
||||
msgid "On the other hand, to contact the speakers of your event, you need the *SMS Marketing* application installed, and to enable *Schedule & Tracks* under :menuselection:`Events --> Configuration --> Settings`."
|
||||
msgstr ""
|
||||
|
||||
#: ../../events/integrations/integration_sms.rst:23
|
||||
msgid "The *Schedule & Tracks* feature allows you to manage the agenda and speakers of your event. For more details watch: `Creating an agenda for your event <https://www.odoo.com/slides/slide/create-an-agenda-for-your-event-717?fullscreen=1>`_."
|
||||
msgstr ""
|
||||
|
||||
#: ../../events/integrations/integration_sms.rst:28
|
||||
msgid "Send SMSs to attendees"
|
||||
msgstr ""
|
||||
|
||||
#: ../../events/integrations/integration_sms.rst:30
|
||||
msgid "Under *Communication*, the message’s target is the attendees of your event."
|
||||
msgstr ""
|
||||
|
||||
#: ../../events/integrations/integration_sms.rst:32
|
||||
msgid "You can choose to confirm each registration with the *Registration* template, and to send a reminder shortly before the event takes place with the *Reminder* template."
|
||||
msgstr ""
|
||||
|
||||
#: ../../events/integrations/integration_sms.rst:38
|
||||
msgid "To make changes in an existing template, click on the external link."
|
||||
msgstr ""
|
||||
|
||||
#: ../../events/integrations/integration_sms.rst:45
|
||||
msgid "Send SMSs to speakers and further targets"
|
||||
msgstr ""
|
||||
|
||||
#: ../../events/integrations/integration_sms.rst:47
|
||||
msgid "The benefit of the integration with the *SMS Marketing* application is that you can choose the target you would like your message to be delivered to. To get started, click on *Contact Track Speakers*."
|
||||
msgstr ""
|
||||
|
||||
#: ../../events/integrations/integration_sms.rst:56
|
||||
msgid "If *Event Track* is not your target (*Recipient*), choose the right one. *Filters* are eligible here."
|
||||
msgstr ""
|
||||
|
||||
#: ../../events/integrations/integration_sms.rst:58
|
||||
msgid "In the example below, the SMS would be sent to the speakers who are in the stage *Proposal* on *Event Track*."
|
||||
msgstr ""
|
||||
|
||||
#: ../../events/integrations/integration_sms.rst:65
|
||||
msgid "Credits are required to be able to send SMSs. For more information about Pricing :doc:`click here <../../sms_marketing/pricing/pricing_and_faq>`, and, about IAP Services :doc:`here <../../general/in_app_purchase/in_app_purchase>`."
|
||||
msgstr ""
|
||||
|
||||
#: ../../events/overview.rst:3
|
||||
msgid "Overview"
|
||||
msgstr ""
|
||||
|
||||
#: ../../events/overview/create_event.rst:3
|
||||
msgid "Create your First Event"
|
||||
msgstr ""
|
||||
|
||||
#: ../../events/overview/create_event.rst:5
|
||||
msgid "Some of the reasons why hosting events is essential are:"
|
||||
msgstr ""
|
||||
|
||||
#: ../../events/overview/create_event.rst:7
|
||||
msgid "To create an engaging experience with your audience;"
|
||||
msgstr ""
|
||||
|
||||
#: ../../events/overview/create_event.rst:8
|
||||
msgid "To generate word of mouth about your company;"
|
||||
msgstr ""
|
||||
|
||||
#: ../../events/overview/create_event.rst:9
|
||||
msgid "To allow networking;"
|
||||
msgstr ""
|
||||
|
||||
#: ../../events/overview/create_event.rst:10
|
||||
msgid "To provide an opportunity for sales representatives to walk their prospects through the product and even their pipeline."
|
||||
msgstr ""
|
||||
|
||||
#: ../../events/overview/create_event.rst:14
|
||||
msgid "Get started"
|
||||
msgstr ""
|
||||
|
||||
#: ../../events/overview/create_event.rst:16
|
||||
msgid "Under the menu *Events*, have a view of all existing events and some key information, such as the number of expected and confirmed attendees."
|
||||
msgstr ""
|
||||
|
||||
#: ../../events/overview/create_event.rst:23
|
||||
msgid "To start a new one, click on *Create* and fill in the form with all the needed information. Enable *Website Menu* to have the menus *Introduction*, *Location*, and *Register* being shown on your event’s website page."
|
||||
msgstr ""
|
||||
|
||||
#: ../../events/overview/create_event.rst:31
|
||||
msgid "To personalize these pages, click on *Edit* to open the `website builder <https://www.odoo.com/slides/slide/website-basics-643?fullscreen=1>`_, and edit content by dragging and dropping blocks."
|
||||
msgstr ""
|
||||
|
||||
#: ../../events/overview/create_event.rst:40
|
||||
msgid "Tab: Tickets"
|
||||
msgstr ""
|
||||
|
||||
#: ../../events/overview/create_event.rst:43
|
||||
msgid "Go to :menuselection:`Events --> Configuration --> Settings` and enable :doc:`Tickets and Online Ticketing <tickets>`."
|
||||
msgstr ""
|
||||
|
||||
#: ../../events/overview/create_event.rst:46
|
||||
msgid "Now, under the *Tickets* Tab, add lines to include the different ticket types you offer. Include the price, the start and end dates for registrations, and even the maximum number of tickets that can be sold."
|
||||
msgstr ""
|
||||
|
||||
#: ../../events/overview/create_event.rst:48
|
||||
msgid "The *Reserved Seats* and *Unconfirmed Seat Reservations* are counted as attendees are marked as :doc:`confirmed <track_attendees>` or not."
|
||||
msgstr ""
|
||||
|
||||
#: ../../events/overview/create_event.rst:55
|
||||
msgid "Tab: Communication"
|
||||
msgstr ""
|
||||
|
||||
#: ../../events/overview/create_event.rst:58
|
||||
msgid "Choose the email and/or SMS message template, as well as the frequency with which you would like to communicate with your attendees under the tab *Communication*."
|
||||
msgstr ""
|
||||
|
||||
#: ../../events/overview/create_event.rst:61
|
||||
msgid "Create a template on the fly or choose an existing one. Define the *Interval* (2, 7, 15..) for the *Unit* (days, hours, weeks, etc.), and the *Trigger* action (after registration, after the event, etc.)."
|
||||
msgstr ""
|
||||
|
||||
#: ../../events/overview/create_event.rst:68
|
||||
msgid "Tab: Questions"
|
||||
msgstr ""
|
||||
|
||||
#: ../../events/overview/create_event.rst:70
|
||||
msgid "Go to :menuselection:`Configuration --> Settings` and enable *Questions*."
|
||||
msgstr ""
|
||||
|
||||
#: ../../events/overview/create_event.rst:72
|
||||
msgid "Now, under the tab *Questions*, edit your questions and answers, choosing if you would like your questionnaire to be asked per order or per registration."
|
||||
msgstr ""
|
||||
|
||||
#: ../../events/overview/create_event.rst:75
|
||||
msgid "Example of a registration for 3 attendees: if enabling the option *Ask each attendee*, the questionnaire is shown 3 times, meaning that answers can vary for each attendee; if *Ask each attendee* is not enabled, the questionnaire is shown once, resulting in a global answer."
|
||||
msgstr ""
|
||||
|
||||
#: ../../events/overview/create_event.rst:81
|
||||
msgid "Once your event is *Confirmed*, you can manage attendees badges, and mark the event as *Finished*. Events marked as *Finished* can be *Set to draft*, putting the event back to an *Unconfirmed* stage from which it can be edited and used again."
|
||||
msgstr ""
|
||||
|
||||
#: ../../events/overview/create_event.rst:90
|
||||
msgid "Publish your event"
|
||||
msgstr ""
|
||||
|
||||
#: ../../events/overview/create_event.rst:92
|
||||
msgid "*Go to Website* and turn *Published* on."
|
||||
msgstr ""
|
||||
|
||||
#: ../../events/overview/create_event.rst:99
|
||||
msgid ":doc:`track_attendees`"
|
||||
msgstr ""
|
||||
|
||||
#: ../../events/overview/create_event.rst:100
|
||||
#: ../../events/overview/track_attendees.rst:45
|
||||
msgid ":doc:`tickets`"
|
||||
msgstr ""
|
||||
|
||||
#: ../../events/overview/create_event.rst:101
|
||||
#: ../../events/overview/track_attendees.rst:46
|
||||
msgid ":doc:`track_talks`"
|
||||
msgstr ""
|
||||
|
||||
#: ../../events/overview/tickets.rst:3
|
||||
msgid "Selling Tickets"
|
||||
msgstr ""
|
||||
|
||||
#: ../../events/overview/tickets.rst:5
|
||||
msgid "If you automate processes, you save time. If you give attendees multiple payment options to choose from, you allow flexibility and open margins for more registrations to happen."
|
||||
msgstr ""
|
||||
|
||||
#: ../../events/overview/tickets.rst:11
|
||||
msgid "Go to :menuselection:`Configuration --> Settings` and activate *Tickets* and *Online Ticketing*."
|
||||
msgstr ""
|
||||
|
||||
#: ../../events/overview/tickets.rst:13
|
||||
msgid "*Tickets* allow tickets to be sold :ref:`events/create_event/through_sales_orders`. *Online Ticketing* allows the sale of tickets to happen :ref:`events/create_event/through_the_website`."
|
||||
msgstr ""
|
||||
|
||||
#: ../../events/overview/tickets.rst:22
|
||||
msgid "Through Sales Orders"
|
||||
msgstr ""
|
||||
|
||||
#: ../../events/overview/tickets.rst:24
|
||||
msgid "On the *Sales* application, choose the event product you created and add it as a product line. A window pops-up, allowing you to choose the event for which you want to create the sales order."
|
||||
msgstr ""
|
||||
|
||||
#: ../../events/overview/tickets.rst:32
|
||||
msgid "Remember to create a product form for the event registration, under *Product*, in the *Sales* application, and to add that same product under your event’s form."
|
||||
msgstr ""
|
||||
|
||||
#: ../../events/overview/tickets.rst:43
|
||||
msgid "Through the Website"
|
||||
msgstr ""
|
||||
|
||||
#: ../../events/overview/tickets.rst:45
|
||||
msgid "On the website, once tickets are added to the cart, the user can continue the transaction choosing among the payment methods you chose to have available."
|
||||
msgstr ""
|
||||
|
||||
#: ../../events/overview/tickets.rst:53
|
||||
msgid ":doc:`../../general/payment_acquirers/payment_acquirers`"
|
||||
msgstr ""
|
||||
|
||||
#: ../../events/overview/track_attendees.rst:3
|
||||
msgid "Track your Attendees"
|
||||
msgstr ""
|
||||
|
||||
#: ../../events/overview/track_attendees.rst:5
|
||||
msgid "Attendees are at the heart of your event. Keeping track of their number and managing their registration and attendance is necessary for planning and analyzing reasons."
|
||||
msgstr ""
|
||||
|
||||
#: ../../events/overview/track_attendees.rst:9
|
||||
msgid "Attendees list and attendance"
|
||||
msgstr ""
|
||||
|
||||
#: ../../events/overview/track_attendees.rst:11
|
||||
msgid "Once attendees have registered or bought their tickets, they are added to the *Attendees* list."
|
||||
msgstr ""
|
||||
|
||||
#: ../../events/overview/track_attendees.rst:12
|
||||
msgid "Tickets sold through sales orders validate attendees as soon as the quotation is confirmed."
|
||||
msgstr ""
|
||||
|
||||
#: ../../events/overview/track_attendees.rst:18
|
||||
msgid "The check mark button is used to confirm the registration. Once a registration is confirmed, attendance can be marked."
|
||||
msgstr ""
|
||||
|
||||
#: ../../events/overview/track_attendees.rst:26
|
||||
msgid "Bagdes and cancellations"
|
||||
msgstr ""
|
||||
|
||||
#: ../../events/overview/track_attendees.rst:28
|
||||
msgid "On the attendees form, choose to send badges manually by clicking on *Send By Email*. *Cancel Registration* to have that attendee being moved to the *Cancelled* stage."
|
||||
msgstr ""
|
||||
|
||||
#: ../../events/overview/track_attendees.rst:36
|
||||
msgid "To see a list of your canceled attendees, under *Filters*, add a *Custom Filter* choosing *Status > is > Cancelled*."
|
||||
msgstr ""
|
||||
|
||||
#: ../../events/overview/track_attendees.rst:44
|
||||
#: ../../events/overview/track_talks.rst:49
|
||||
msgid ":doc:`../integrations/integration_sms`"
|
||||
msgstr ""
|
||||
|
||||
#: ../../events/overview/track_talks.rst:3
|
||||
msgid "Track and Manage Talks"
|
||||
msgstr ""
|
||||
|
||||
#: ../../events/overview/track_talks.rst:5
|
||||
msgid "Allow partners to submit talk proposals so they can share their knowledge and expertise. Good speakers and talks are what make your event great."
|
||||
msgstr ""
|
||||
|
||||
#: ../../events/overview/track_talks.rst:11
|
||||
msgid "Go to :menuselection:`Events --> Configuration --> Settings` and enable *Schedule & Tracks*."
|
||||
msgstr ""
|
||||
|
||||
#: ../../events/overview/track_talks.rst:14
|
||||
msgid "Now, in your event's form, once *Website menu* is enabled, the options *Tracks on Website* and *Track Proposals on Website* become available. Enabling them adds the menus *Talks*, *Talk Proposals*, and *Agenda* to your website."
|
||||
msgstr ""
|
||||
|
||||
#: ../../events/overview/track_talks.rst:20
|
||||
msgid "Besides having the ability to suggest their own talks, the website now allows users to see a list of the whole agenda and scheduled talks."
|
||||
msgstr ""
|
||||
|
||||
#: ../../events/overview/track_talks.rst:28
|
||||
msgid "To handle tracks internally and not have the menus *Talks*, *Talk Proposals*, and *Agenda* online, use the menu *Tracks* individually."
|
||||
msgstr ""
|
||||
|
||||
#: ../../events/overview/track_talks.rst:32
|
||||
msgid "Publishing speaker proposals"
|
||||
msgstr ""
|
||||
|
||||
#: ../../events/overview/track_talks.rst:34
|
||||
msgid "Once partners have filled in the appropriate form and submitted their proposals, a new *Proposal* is instantly created under the menu *Track*."
|
||||
msgstr ""
|
||||
|
||||
#: ../../events/overview/track_talks.rst:41
|
||||
msgid "If the proposal is accepted and can go online, simply open its form and click on *Go to Website*. From the website page, turn *Published* on."
|
||||
msgstr ""
|
||||
|
||||
@ -6,9 +6,9 @@
|
||||
#, fuzzy
|
||||
msgid ""
|
||||
msgstr ""
|
||||
"Project-Id-Version: Odoo 11.0\n"
|
||||
"Project-Id-Version: Odoo 13.0\n"
|
||||
"Report-Msgid-Bugs-To: \n"
|
||||
"POT-Creation-Date: 2018-10-19 10:03+0200\n"
|
||||
"POT-Creation-Date: 2020-09-22 16:26+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/others/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
|
||||
@ -118,7 +118,7 @@ msgid "How to submit expenses to managers"
|
||||
msgstr ""
|
||||
|
||||
#: ../../expense/expense.rst:90
|
||||
msgid "When you are ready to submit your expenses to your manager (e.g. at the end of a business trip, or once a month), go to the menu :menuselection:`My Expenses --> Expenses to Submit`. Select all expenses from the list view and click on :menuselection:`Action > Submit to Manager`. Save the newly created expense report (i.e. set of expenses), and wait for your manager to approve it."
|
||||
msgid "When you are ready to submit your expenses to your manager (e.g. at the end of a business trip, or once a month), go to the menu :menuselection:`My Expenses --> Expenses to Submit`. Select all expenses from the list view and click on :menuselection:`Action --> Submit to Manager`. Save the newly created expense report (i.e. set of expenses), and wait for your manager to approve it."
|
||||
msgstr ""
|
||||
|
||||
#: ../../expense/expense.rst:100
|
||||
|
||||
285
locale/sources/fsm.pot
Normal file
285
locale/sources/fsm.pot
Normal file
@ -0,0 +1,285 @@
|
||||
# SOME DESCRIPTIVE TITLE.
|
||||
# Copyright (C) 2015-TODAY, Odoo S.A.
|
||||
# This file is distributed under the same license as the Odoo package.
|
||||
# FIRST AUTHOR <EMAIL@ADDRESS>, YEAR.
|
||||
#
|
||||
#, fuzzy
|
||||
msgid ""
|
||||
msgstr ""
|
||||
"Project-Id-Version: Odoo 13.0\n"
|
||||
"Report-Msgid-Bugs-To: \n"
|
||||
"POT-Creation-Date: 2020-09-22 16:26+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"
|
||||
"MIME-Version: 1.0\n"
|
||||
"Content-Type: text/plain; charset=UTF-8\n"
|
||||
"Content-Transfer-Encoding: 8bit\n"
|
||||
|
||||
#: ../../fsm.rst:5
|
||||
msgid "Field Service"
|
||||
msgstr ""
|
||||
|
||||
#: ../../fsm/helpdesk.rst:3
|
||||
msgid "Helpdesk"
|
||||
msgstr ""
|
||||
|
||||
#: ../../fsm/helpdesk/plan_onsite.rst:3
|
||||
msgid "Plan Onsite Interventions from Helpdesk Tickets"
|
||||
msgstr ""
|
||||
|
||||
#: ../../fsm/helpdesk/plan_onsite.rst:4
|
||||
msgid "The integration with the Helpdesk application lets your helpdesk team manage interventions requests directly. It speeds up processes as you can plan field services tasks from tickets."
|
||||
msgstr ""
|
||||
|
||||
#: ../../fsm/helpdesk/plan_onsite.rst:8
|
||||
#: ../../fsm/sales/create_quotations.rst:8
|
||||
#: ../../fsm/sales/onsite_tasks_from_sales_orders.rst:9
|
||||
#: ../../fsm/worksheets/customize_worksheets.rst:9
|
||||
msgid "Enable the feature"
|
||||
msgstr ""
|
||||
|
||||
#: ../../fsm/helpdesk/plan_onsite.rst:9
|
||||
msgid "Go to :menuselection:`Helpdesk --> Configuration --> Helpdesk Teams --> Edit` and enable :menuselection:`Onsite Interventions --> Save`."
|
||||
msgstr ""
|
||||
|
||||
#: ../../fsm/helpdesk/plan_onsite.rst:17
|
||||
msgid "Now once your helpdesk team needs, they have the option to *Plan Intervention* from tickets."
|
||||
msgstr ""
|
||||
|
||||
#: ../../fsm/overview.rst:3
|
||||
msgid "Overview"
|
||||
msgstr ""
|
||||
|
||||
#: ../../fsm/overview/invoicing_time.rst:3
|
||||
msgid "Invoicing Time and Material to Customers"
|
||||
msgstr ""
|
||||
|
||||
#: ../../fsm/overview/invoicing_time.rst:4
|
||||
msgid "Track the exact time spent on a task and give customers the ability to sign their worksheet report onsite. Invoice customers as soon as the work is complete, leaving you, and the customer, with the confidence that they will be charged for the exact right hours and material used."
|
||||
msgstr ""
|
||||
|
||||
#: ../../fsm/overview/invoicing_time.rst:9
|
||||
msgid "Get the exact time spent on a task"
|
||||
msgstr ""
|
||||
|
||||
#: ../../fsm/overview/invoicing_time.rst:10
|
||||
msgid "Click on *Start* to launch the timer. You can *Pause* at any moment and *Resume* when you would like to continue."
|
||||
msgstr ""
|
||||
|
||||
#: ../../fsm/overview/invoicing_time.rst:17
|
||||
msgid "Click on *Stop* once the work is done to confirm the total time spent and add a description."
|
||||
msgstr ""
|
||||
|
||||
#: ../../fsm/overview/invoicing_time.rst:24
|
||||
msgid "Sign and send reports & validate stock-picking"
|
||||
msgstr ""
|
||||
|
||||
#: ../../fsm/overview/invoicing_time.rst:25
|
||||
msgid "Now, fill your *Worksheet* and add the used products clicking on *Products*."
|
||||
msgstr ""
|
||||
|
||||
#: ../../fsm/overview/invoicing_time.rst:31
|
||||
msgid "Click on *Start* if you need to record additional time for the same activity. The time recorded will be added to the already created and signed worksheet. Then, create a new invoice for the time added."
|
||||
msgstr ""
|
||||
|
||||
#: ../../fsm/overview/invoicing_time.rst:34
|
||||
msgid "*Mark as done* to close the task and to invoice your intervention. It also validates the stock-picking keeping your inventory up-to-date."
|
||||
msgstr ""
|
||||
|
||||
#: ../../fsm/overview/invoicing_time.rst:37
|
||||
msgid "*Sign Report* generates a detailed worksheet report for the customer to sign. Send it through email clicking on *Send Report*."
|
||||
msgstr ""
|
||||
|
||||
#: ../../fsm/overview/invoicing_time.rst:41
|
||||
msgid "Invoice your time and material"
|
||||
msgstr ""
|
||||
|
||||
#: ../../fsm/overview/invoicing_time.rst:42
|
||||
msgid "Under :menuselection:`All Tasks --> To Invoice`, find a list of all tasks marked as done but that have not been invoiced. Convenient feature as it allows accountants to easily access all finished tasks at once."
|
||||
msgstr ""
|
||||
|
||||
#: ../../fsm/overview/invoicing_time.rst:52
|
||||
msgid "Invoice all tasks at once selecting them all and going to :menuselection:`Action --> Create Invoice`."
|
||||
msgstr ""
|
||||
|
||||
#: ../../fsm/overview/invoicing_time.rst:60
|
||||
msgid ":doc:`../../project/advanced/feedback`"
|
||||
msgstr ""
|
||||
|
||||
#: ../../fsm/overview/keep_track.rst:3
|
||||
msgid "Keeping Track of Stock"
|
||||
msgstr ""
|
||||
|
||||
#: ../../fsm/overview/keep_track.rst:4
|
||||
msgid "The integration with the Inventory application makes possible to track the material used and automatically keep your stock up to date."
|
||||
msgstr ""
|
||||
|
||||
#: ../../fsm/overview/keep_track.rst:8
|
||||
msgid "Set up your Field Service project"
|
||||
msgstr ""
|
||||
|
||||
#: ../../fsm/overview/keep_track.rst:9
|
||||
msgid "Go to :menuselection:`Field Service --> Configuration --> Projects` and make sure the option *Products on Tasks* is enabled."
|
||||
msgstr ""
|
||||
|
||||
#: ../../fsm/overview/keep_track.rst:15
|
||||
msgid "Now, add the materials used in the intervention to the worksheet, and once the task is *Marked as done*, the stock-picking is automatically validated and the inventory evaluation is automatically updated."
|
||||
msgstr ""
|
||||
|
||||
#: ../../fsm/overview/manage_employees_schedule.rst:3
|
||||
msgid "Manage your Employees’ Schedules and Time Off"
|
||||
msgstr ""
|
||||
|
||||
#: ../../fsm/overview/manage_employees_schedule.rst:4
|
||||
msgid "The integration with the *Time off* application allows you to quickly see your employees’ availabilities. It will avoid conflicts and errors between employees schedules and interventions."
|
||||
msgstr ""
|
||||
|
||||
#: ../../fsm/overview/manage_employees_schedule.rst:8
|
||||
msgid "Effortlessly see employees’ time off"
|
||||
msgstr ""
|
||||
|
||||
#: ../../fsm/overview/manage_employees_schedule.rst:9
|
||||
msgid "No configuration needs to be done. Once the employees’ time has been validated in the *Time off* application, cells will be grayed for those days in your Gantt view."
|
||||
msgstr ""
|
||||
|
||||
#: ../../fsm/overview/manage_employees_schedule.rst:13
|
||||
msgid "It also adapts to the working calendar of the employee. Example: the employee works part-time (from Monday to Wednesday). So, Thursday and Friday will also be greyed, in addition to the weekends."
|
||||
msgstr ""
|
||||
|
||||
#: ../../fsm/overview/manage_employees_schedule.rst:20
|
||||
msgid "Easily manage employees’ schedules"
|
||||
msgstr ""
|
||||
|
||||
#: ../../fsm/overview/manage_employees_schedule.rst:21
|
||||
msgid "From the Gantt view (under *Planning by User, Project or Worksheet*), click on the plus sign to add a new task or on the magnifying glass to plan an existing one."
|
||||
msgstr ""
|
||||
|
||||
#: ../../fsm/overview/manage_employees_schedule.rst:29
|
||||
msgid "Unassigned tasks"
|
||||
msgstr ""
|
||||
|
||||
#: ../../fsm/overview/manage_employees_schedule.rst:30
|
||||
msgid "If you need to plan an intervention but you do not know yet who will take care of it, you can leave the task unassigned. It will still be shown in the Gantt view. Simply drag and drop the responsible person he can be assigned."
|
||||
msgstr ""
|
||||
|
||||
#: ../../fsm/overview/manage_employees_schedule.rst:39
|
||||
msgid "Create projects per team, or per working site, and have a more accurate and dynamic database."
|
||||
msgstr ""
|
||||
|
||||
#: ../../fsm/overview/manage_employees_schedule.rst:42
|
||||
msgid ":doc:`../../project/overview/setup`"
|
||||
msgstr ""
|
||||
|
||||
#: ../../fsm/overview/planning_itinerary.rst:3
|
||||
msgid "Planning an Itinerary"
|
||||
msgstr ""
|
||||
|
||||
#: ../../fsm/overview/planning_itinerary.rst:5
|
||||
msgid "Having an itinerary being shown based on the chronological order of the activities and on the best route to take, makes employees’ life easier and the workload more efficient."
|
||||
msgstr ""
|
||||
|
||||
#: ../../fsm/overview/planning_itinerary.rst:9
|
||||
msgid "Have an itinerary displayed directly in Odoo"
|
||||
msgstr ""
|
||||
|
||||
#: ../../fsm/overview/planning_itinerary.rst:10
|
||||
msgid "Go to *Settings* and under *Map view* click on *Get token*."
|
||||
msgstr ""
|
||||
|
||||
#: ../../fsm/overview/planning_itinerary.rst:15
|
||||
msgid "Click on :menuselection:`Start mapping for free --> fill the Username, email and password fields --> agree with their Terms of Service and Privacy Policy --> Get started`. You will be redirected to your account. Scrolling the page down you will find *Access tokens*. Copy the *Default public token*."
|
||||
msgstr ""
|
||||
|
||||
#: ../../fsm/overview/planning_itinerary.rst:24
|
||||
msgid "Back in Odoo, paste it on :menuselection:`Token --> Save`."
|
||||
msgstr ""
|
||||
|
||||
#: ../../fsm/overview/planning_itinerary.rst:29
|
||||
msgid "Now, your maps will show the itinerary based on the scheduled time and best route."
|
||||
msgstr ""
|
||||
|
||||
#: ../../fsm/overview/planning_itinerary.rst:36
|
||||
msgid "This is an optional feature, as you can still have access to a map view without a Mapbox account."
|
||||
msgstr ""
|
||||
|
||||
#: ../../fsm/sales.rst:3
|
||||
msgid "Sales"
|
||||
msgstr ""
|
||||
|
||||
#: ../../fsm/sales/create_quotations.rst:3
|
||||
msgid "Create Quotations from Tasks"
|
||||
msgstr ""
|
||||
|
||||
#: ../../fsm/sales/create_quotations.rst:4
|
||||
msgid "Allowing quotations to be created from tasks delivers a more efficient service as it allows space for preventive actions, while making the flow easy for employees."
|
||||
msgstr ""
|
||||
|
||||
#: ../../fsm/sales/create_quotations.rst:9
|
||||
msgid "First, go to :menuselection:`Field Service --> Configuration --> Settings` and enable the option *Extra Quotations*."
|
||||
msgstr ""
|
||||
|
||||
#: ../../fsm/sales/create_quotations.rst:16
|
||||
msgid "Second, go to :menuselection:`Configuration --> Projects` and enable *Extra Quotations*."
|
||||
msgstr ""
|
||||
|
||||
#: ../../fsm/sales/create_quotations.rst:23
|
||||
msgid "You can now create *New Quotations* directly from your tasks."
|
||||
msgstr ""
|
||||
|
||||
#: ../../fsm/sales/onsite_tasks_from_sales_orders.rst:3
|
||||
msgid "Create Onsite Interventions Tasks from Sales Orders"
|
||||
msgstr ""
|
||||
|
||||
#: ../../fsm/sales/onsite_tasks_from_sales_orders.rst:4
|
||||
msgid "By allowing your sales team to open onsite interventions tasks will create a seamless experience for your customers. It also allows them to first receive a quotation with the materials that will be used plus the service price to be approved before the work even starts."
|
||||
msgstr ""
|
||||
|
||||
#: ../../fsm/sales/onsite_tasks_from_sales_orders.rst:10
|
||||
msgid "Go to :menuselection:`Sales --> Products --> Create` or edit an existing one. Select: under :menuselection:`General Information --> Product Type: Service`; under :menuselection:`Sales --> Service Invoicing Policy: Timesheet on task --> Service Tracking: Create a task in an existing project --> Project --> Worksheet Template --> Save`."
|
||||
msgstr ""
|
||||
|
||||
#: ../../fsm/sales/onsite_tasks_from_sales_orders.rst:19
|
||||
msgid "Now, once you have *Confirmed* a *quotation*, a task will be created in the respective project you have chosen."
|
||||
msgstr ""
|
||||
|
||||
#: ../../fsm/sales/onsite_tasks_from_sales_orders.rst:28
|
||||
msgid "One of the greatest benefits here is that you can have different *Worksheets Templates* under the same project and product, for example."
|
||||
msgstr ""
|
||||
|
||||
#: ../../fsm/worksheets.rst:3
|
||||
msgid "Worksheets"
|
||||
msgstr ""
|
||||
|
||||
#: ../../fsm/worksheets/customize_worksheets.rst:3
|
||||
msgid "Customize Worksheet Reports"
|
||||
msgstr ""
|
||||
|
||||
#: ../../fsm/worksheets/customize_worksheets.rst:4
|
||||
msgid "Personalizing your customer reports, also called *worksheets*, allows you to have different descriptions of the work for each type of intervention. It speeds up the flow for your employees while giving customers a detailed summary, which can be reviewed and signed onsite."
|
||||
msgstr ""
|
||||
|
||||
#: ../../fsm/worksheets/customize_worksheets.rst:10
|
||||
msgid "Go to :menuselection:`Field Service --> Configuration` and enable :menuselection:`Worksheet Templates --> Save`."
|
||||
msgstr ""
|
||||
|
||||
#: ../../fsm/worksheets/customize_worksheets.rst:18
|
||||
msgid "Designing worksheets"
|
||||
msgstr ""
|
||||
|
||||
#: ../../fsm/worksheets/customize_worksheets.rst:19
|
||||
msgid "Under :menuselection:`Configuration --> Worksheet Templates`, click on *Create* and start to *Design Worksheet Template*. You will be redirected to the *Studio* application."
|
||||
msgstr ""
|
||||
|
||||
#: ../../fsm/worksheets/customize_worksheets.rst:27
|
||||
msgid "With the freedom of *Studio*, drag and drop fields to create a report tailored to your needs. Once you are done, click on *Close* and get an overview of the work done."
|
||||
msgstr ""
|
||||
|
||||
#: ../../fsm/worksheets/customize_worksheets.rst:30
|
||||
msgid "*Worksheets* is where you can see how many times the worksheet has been used/completed under a task. *Analysis* examines all the worksheets under that given template and generates a graph."
|
||||
msgstr ""
|
||||
|
||||
#: ../../fsm/worksheets/customize_worksheets.rst:38
|
||||
msgid "`Studio Basics <https://www.odoo.com/slides/slide/studio-basics-710?fullscreen=1>`_"
|
||||
msgstr ""
|
||||
|
||||
File diff suppressed because it is too large
Load Diff
@ -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-22 16:26+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,7 +25,7 @@ msgid "This document summarizes Odoo Online's services, our Success Pack impleme
|
||||
msgstr ""
|
||||
|
||||
#: ../../getting_started/documentation.rst:12
|
||||
msgid "1. The SPoC (*Single Point of Contact*) and the Consultant"
|
||||
msgid "The SPoC (*Single Point of Contact*) and the Consultant"
|
||||
msgstr ""
|
||||
|
||||
#: ../../getting_started/documentation.rst:14
|
||||
@ -45,178 +45,178 @@ msgid "**Meetings optimization**: The Odoo consultant is not involved in the pro
|
||||
msgstr ""
|
||||
|
||||
#: ../../getting_started/documentation.rst:39
|
||||
msgid "**Train the Trainer approach**: The Odoo consultant provides functional training to the SPoC so that he can pass on this knowledge to his collaborators. In order for this approach to be successful, it is necessary that the SPoC is also involved in its own rise in skills through self-learning via the `Odoo documentation <http://www.odoo.com/documentation/user/10.0/index.html>`__, `The elearning platform <https://odoo.thinkific.com/courses/odoo-functional>`__ and the testing of functionalities."
|
||||
msgstr ""
|
||||
|
||||
#: ../../getting_started/documentation.rst:47
|
||||
msgid "2. Project Scope"
|
||||
msgid "**Train the Trainer approach**: The Odoo consultant provides functional training to the SPoC so that he can pass on this knowledge to his collaborators. In order for this approach to be successful, it is necessary that the SPoC is also involved in its own rise in skills through self-learning via the :doc:`Odoo documentation <../index>`, `The elearning platform <https://odoo.com/learn>`_ and the testing of functionalities."
|
||||
msgstr ""
|
||||
|
||||
#: ../../getting_started/documentation.rst:49
|
||||
msgid "Project Scope"
|
||||
msgstr ""
|
||||
|
||||
#: ../../getting_started/documentation.rst:51
|
||||
msgid "To make sure all the stakeholders involved are always aligned, it is necessary to define and to make the project scope evolve as long as the project implementation is pursuing."
|
||||
msgstr ""
|
||||
|
||||
#: ../../getting_started/documentation.rst:53
|
||||
#: ../../getting_started/documentation.rst:55
|
||||
msgid "**A clear definition of the initial project scope**: A clear definition of the initial needs is crucial to ensure the project is running smoothly. Indeed, when all the stakeholders share the same vision, the evolution of the needs and the resulting decision-making process are more simple and more clear."
|
||||
msgstr ""
|
||||
|
||||
#: ../../getting_started/documentation.rst:59
|
||||
#: ../../getting_started/documentation.rst:61
|
||||
msgid "**Phasing the project**: Favoring an implementation in several coherent phases allowing regular production releases and an evolving takeover of Odoo by the end users have demonstrated its effectiveness over time. This approach also helps to identify gaps and apply corrective actions early in the implementation."
|
||||
msgstr ""
|
||||
|
||||
#: ../../getting_started/documentation.rst:66
|
||||
#: ../../getting_started/documentation.rst:68
|
||||
msgid "**Adopting standard features as a priority**: Odoo offers a great environment to implement slight improvements (customizations) or more important ones (developments). Nevertheless, adoption of the standard solution will be preferred as often as possible in order to optimize project delivery times and provide the user with a long-term stability and fluid scalability of his new tool. Ideally, if an improvement of the software should still be realized, its implementation will be carried out after an experiment of the standard in production."
|
||||
msgstr ""
|
||||
|
||||
#: ../../getting_started/documentation.rst:80
|
||||
msgid "3. Managing expectations"
|
||||
#: ../../getting_started/documentation.rst:82
|
||||
msgid "Managing expectations"
|
||||
msgstr ""
|
||||
|
||||
#: ../../getting_started/documentation.rst:82
|
||||
#: ../../getting_started/documentation.rst:84
|
||||
msgid "The gap between the reality of an implementation and the expectations of future users is a crucial factor. Three important aspects must be taken into account from the beginning of the project:"
|
||||
msgstr ""
|
||||
|
||||
#: ../../getting_started/documentation.rst:86
|
||||
#: ../../getting_started/documentation.rst:88
|
||||
msgid "**Align with the project approach**: Both a clear division of roles and responsibilities and a clear description of the operating modes (validation, problem-solving, etc.) are crucial to the success of an Odoo implementation. It is therefore strongly advised to take the necessary time at the beginning of the project to align with these topics and regularly check that this is still the case."
|
||||
msgstr ""
|
||||
|
||||
#: ../../getting_started/documentation.rst:94
|
||||
#: ../../getting_started/documentation.rst:96
|
||||
msgid "**Focus on the project success, not on the ideal solution**: The main goal of the SPoC and the Consultant is to carry out the project entrusted to them in order to provide the most effective solution to meet the needs expressed. This goal can sometimes conflict with the end user's vision of an ideal solution. In that case, the SPoC and the consultant will apply the 80-20 rule: focus on 80% of the expressed needs and take out the remaining 20% of the most disadvantageous objectives in terms of cost/benefit ratio (those proportions can of course change over time). Therefore, it will be considered acceptable to integrate a more time-consuming manipulation if a global relief is noted. Changes in business processes may also be proposed to pursue this same objective."
|
||||
msgstr ""
|
||||
|
||||
#: ../../getting_started/documentation.rst:108
|
||||
#: ../../getting_started/documentation.rst:110
|
||||
msgid "**Specifications are always EXPLICIT**: Gaps between what is expected and what is delivered are often a source of conflict in a project. In order to avoid being in this delicate situation, we recommend using several types of tools\\* :"
|
||||
msgstr ""
|
||||
|
||||
#: ../../getting_started/documentation.rst:113
|
||||
#: ../../getting_started/documentation.rst:115
|
||||
msgid "**The GAP Analysis**: The comparison of the request with the standard features proposed by Odoo will make it possible to identify the gap to be filled by developments/customizations or changes in business processes."
|
||||
msgstr ""
|
||||
|
||||
#: ../../getting_started/documentation.rst:118
|
||||
#: ../../getting_started/documentation.rst:120
|
||||
msgid "**The User Story**: This technique clearly separates the responsibilities between the SPoC, responsible for explaining the WHAT, the WHY and the WHO, and the Consultant who will provide a response to the HOW."
|
||||
msgstr ""
|
||||
|
||||
#: ../../getting_started/documentation.rst:126
|
||||
#: ../../getting_started/documentation.rst:128
|
||||
msgid "`The Proof of Concept <https://en.wikipedia.org/wiki/Proof_of_concept>`__ A simplified version, a prototype of what is expected to agree on the main lines of expected changes."
|
||||
msgstr ""
|
||||
|
||||
#: ../../getting_started/documentation.rst:130
|
||||
#: ../../getting_started/documentation.rst:132
|
||||
msgid "**The Mockup**: In the same idea as the Proof of Concept, it will align with the changes related to the interface."
|
||||
msgstr ""
|
||||
|
||||
#: ../../getting_started/documentation.rst:133
|
||||
#: ../../getting_started/documentation.rst:135
|
||||
msgid "To these tools will be added complete transparency on the possibilities and limitations of the software and/or its environment so that all project stakeholders have a clear idea of what can be expected/achieved in the project. We will, therefore, avoid basing our work on hypotheses without verifying its veracity beforehand."
|
||||
msgstr ""
|
||||
|
||||
#: ../../getting_started/documentation.rst:139
|
||||
#: ../../getting_started/documentation.rst:141
|
||||
msgid "*This list can, of course, be completed by other tools that would more adequately meet the realities and needs of your project*"
|
||||
msgstr ""
|
||||
|
||||
#: ../../getting_started/documentation.rst:143
|
||||
msgid "4. Communication Strategy"
|
||||
#: ../../getting_started/documentation.rst:145
|
||||
msgid "Communication Strategy"
|
||||
msgstr ""
|
||||
|
||||
#: ../../getting_started/documentation.rst:145
|
||||
#: ../../getting_started/documentation.rst:147
|
||||
msgid "The purpose of the QuickStart methodology is to ensure quick ownership of the tool for end users. Effective communication is therefore crucial to the success of this approach. Its optimization will, therefore, lead us to follow those principles:"
|
||||
msgstr ""
|
||||
|
||||
#: ../../getting_started/documentation.rst:150
|
||||
#: ../../getting_started/documentation.rst:152
|
||||
msgid "**Sharing the project management documentation**: The best way to ensure that all stakeholders in a project have the same level of knowledge is to provide direct access to the project's tracking document (Project Organizer). This document will contain at least a list of tasks to be performed as part of the implementation for which the priority level and the manager are clearly defined."
|
||||
msgstr ""
|
||||
|
||||
#: ../../getting_started/documentation.rst:158
|
||||
#: ../../getting_started/documentation.rst:160
|
||||
msgid "The Project Organizer is a shared project tracking tool that allows both detailed tracking of ongoing tasks and the overall progress of the project."
|
||||
msgstr ""
|
||||
|
||||
#: ../../getting_started/documentation.rst:162
|
||||
#: ../../getting_started/documentation.rst:164
|
||||
msgid "**Report essential information**: In order to minimize the documentation time to the essentials, we will follow the following good practices:"
|
||||
msgstr ""
|
||||
|
||||
#: ../../getting_started/documentation.rst:166
|
||||
#: ../../getting_started/documentation.rst:168
|
||||
msgid "Meeting minutes will be limited to decisions and validations;"
|
||||
msgstr ""
|
||||
|
||||
#: ../../getting_started/documentation.rst:168
|
||||
#: ../../getting_started/documentation.rst:170
|
||||
msgid "Project statuses will only be established when an important milestone is reached;"
|
||||
msgstr ""
|
||||
|
||||
#: ../../getting_started/documentation.rst:171
|
||||
#: ../../getting_started/documentation.rst:173
|
||||
msgid "Training sessions on the standard or customized solution will be organized."
|
||||
msgstr ""
|
||||
|
||||
#: ../../getting_started/documentation.rst:175
|
||||
msgid "5. Customizations and Development"
|
||||
#: ../../getting_started/documentation.rst:177
|
||||
msgid "Customizations and Development"
|
||||
msgstr ""
|
||||
|
||||
#: ../../getting_started/documentation.rst:177
|
||||
#: ../../getting_started/documentation.rst:179
|
||||
msgid "Odoo is a software known for its flexibility and its important evolution capacity. However, a significant amount of development contradicts a fast and sustainable implementation. This is the reason why it is recommended to:"
|
||||
msgstr ""
|
||||
|
||||
#: ../../getting_started/documentation.rst:182
|
||||
#: ../../getting_started/documentation.rst:184
|
||||
msgid "**Develop only for a good reason**: The decision to develop must always be taken when the cost-benefit ratio is positive (saving time on a daily basis, etc.). For example, it will be preferable to realize a significant development in order to reduce the time of a daily operation, rather than an operation to be performed only once a quarter. It is generally accepted that the closer the solution is to the standard, the lighter and more fluid the migration process, and the lower the maintenance costs for both parties. In addition, experience has shown us that 60% of initial development requests are dropped after a few weeks of using standard Odoo (see \"Adopting the standard as a priority\")."
|
||||
msgstr ""
|
||||
|
||||
#: ../../getting_started/documentation.rst:194
|
||||
#: ../../getting_started/documentation.rst:196
|
||||
msgid "**Replace, without replicate**: There is a good reason for the decision to change the management software has been made. In this context, the moment of implementation is THE right moment to accept and even be a change initiator both in terms of how the software will be used and at the level of the business processes of the company."
|
||||
msgstr ""
|
||||
|
||||
#: ../../getting_started/documentation.rst:202
|
||||
msgid "6. Testing and Validation principles"
|
||||
#: ../../getting_started/documentation.rst:204
|
||||
msgid "Testing and Validation principles"
|
||||
msgstr ""
|
||||
|
||||
#: ../../getting_started/documentation.rst:204
|
||||
#: ../../getting_started/documentation.rst:206
|
||||
msgid "Whether developments are made or not in the implementation, it is crucial to test and validate the correspondence of the solution with the operational needs of the company."
|
||||
msgstr ""
|
||||
|
||||
#: ../../getting_started/documentation.rst:208
|
||||
#: ../../getting_started/documentation.rst:210
|
||||
msgid "**Role distribution**: In this context, the Consultant will be responsible for delivering a solution corresponding to the defined specifications; the SPoC will have to test and validate that the solution delivered meets the requirements of the operational reality."
|
||||
msgstr ""
|
||||
|
||||
#: ../../getting_started/documentation.rst:214
|
||||
#: ../../getting_started/documentation.rst:216
|
||||
msgid "**Change management**: When a change needs to be made to the solution, the noted gap is caused by:"
|
||||
msgstr ""
|
||||
|
||||
#: ../../getting_started/documentation.rst:218
|
||||
#: ../../getting_started/documentation.rst:220
|
||||
msgid "A difference between the specification and the delivered solution - This is a correction for which the Consultant is responsible"
|
||||
msgstr ""
|
||||
|
||||
#: ../../getting_started/documentation.rst:220
|
||||
#: ../../getting_started/documentation.rst:223
|
||||
msgid "**or**"
|
||||
msgstr ""
|
||||
|
||||
#: ../../getting_started/documentation.rst:222
|
||||
#: ../../getting_started/documentation.rst:225
|
||||
msgid "A difference between the specification and the imperatives of operational reality - This is a change that is the responsibility of SPoC."
|
||||
msgstr ""
|
||||
|
||||
#: ../../getting_started/documentation.rst:226
|
||||
msgid "7. Data Imports"
|
||||
#: ../../getting_started/documentation.rst:229
|
||||
msgid "Data Imports"
|
||||
msgstr ""
|
||||
|
||||
#: ../../getting_started/documentation.rst:228
|
||||
#: ../../getting_started/documentation.rst:231
|
||||
msgid "Importing the history of transactional data is an important issue and must be answered appropriately to allow the project running smoothly. Indeed, this task can be time-consuming and, if its priority is not well defined, prevent production from happening in time. To do this as soon as possible, it will be decided :"
|
||||
msgstr ""
|
||||
|
||||
#: ../../getting_started/documentation.rst:234
|
||||
#: ../../getting_started/documentation.rst:237
|
||||
msgid "**Not to import anything**: It often happens that after reflection, importing data history is not considered necessary, these data being, moreover, kept outside Odoo and consolidated for later reporting."
|
||||
msgstr ""
|
||||
|
||||
#: ../../getting_started/documentation.rst:239
|
||||
#: ../../getting_started/documentation.rst:242
|
||||
msgid "**To import a limited amount of data before going into production**: When the data history relates to information being processed (purchase orders, invoices, open projects, for example), the need to have this information available from the first day of use in production is real. In this case, the import will be made before the production launch."
|
||||
msgstr ""
|
||||
|
||||
#: ../../getting_started/documentation.rst:246
|
||||
#: ../../getting_started/documentation.rst:249
|
||||
msgid "**To import after production launch**: When the data history needs to be integrated with Odoo mainly for reporting purposes, it is clear that these can be integrated into the software retrospectively. In this case, the production launch of the solution will precede the required imports."
|
||||
msgstr ""
|
||||
|
||||
#: ../../getting_started/documentation.rst:253
|
||||
msgid "8. Support"
|
||||
msgstr ""
|
||||
|
||||
#: ../../getting_started/documentation.rst:255
|
||||
msgid "When your project is put in production, our support teams take care of your questions or technical issues."
|
||||
#: ../../getting_started/documentation.rst:256
|
||||
msgid "Support"
|
||||
msgstr ""
|
||||
|
||||
#: ../../getting_started/documentation.rst:258
|
||||
msgid "When your project is put in production, our support teams take care of your questions or technical issues."
|
||||
msgstr ""
|
||||
|
||||
#: ../../getting_started/documentation.rst:261
|
||||
msgid "See :ref:`support-expectations`."
|
||||
msgstr ""
|
||||
|
||||
|
||||
@ -8,7 +8,7 @@ msgid ""
|
||||
msgstr ""
|
||||
"Project-Id-Version: Odoo 13.0\n"
|
||||
"Report-Msgid-Bugs-To: \n"
|
||||
"POT-Creation-Date: 2019-11-20 10:20+0100\n"
|
||||
"POT-Creation-Date: 2020-09-22 16:26+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,339 +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:4
|
||||
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. Odoo’s Helpdesk app allows me to generate credit notes, return products, grant coupons, do repairs and plan onsite interventions from a ticket’s page."
|
||||
#: ../../helpdesk/advanced/after_sales.rst:3
|
||||
msgid "After Sales Features"
|
||||
msgstr ""
|
||||
|
||||
#: ../../helpdesk/after_sales.rst:7
|
||||
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. Odoo’s Helpdesk application allows you to generate credit notes, manage returns, products, repairs, grant coupons, and even plan onsite interventions from a ticket’s page."
|
||||
msgstr ""
|
||||
|
||||
#: ../../helpdesk/after_sales.rst:8
|
||||
msgid "Go to *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:14
|
||||
#: ../../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:15
|
||||
msgid "I can use a credit note to refund a customer or adjust the amount due. For that, I’ll 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:22
|
||||
#: ../../helpdesk/advanced/after_sales.rst:30
|
||||
msgid "Allow product returns from tickets"
|
||||
msgstr ""
|
||||
|
||||
#: ../../helpdesk/after_sales.rst:23
|
||||
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:29
|
||||
#: ../../helpdesk/advanced/after_sales.rst:39
|
||||
msgid "Grant coupons from tickets"
|
||||
msgstr ""
|
||||
|
||||
#: ../../helpdesk/after_sales.rst:30
|
||||
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 *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:37
|
||||
#: ../../helpdesk/advanced/after_sales.rst:48
|
||||
msgid "Repairs from tickets"
|
||||
msgstr ""
|
||||
|
||||
#: ../../helpdesk/after_sales.rst:38
|
||||
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:44
|
||||
#: ../../helpdesk/advanced/after_sales.rst:57
|
||||
msgid "Plan onsite interventions from tickets"
|
||||
msgstr ""
|
||||
|
||||
#: ../../helpdesk/after_sales.rst:45
|
||||
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:52
|
||||
#: ../../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:53
|
||||
msgid ":doc:`../manufacturing/repair/repair`"
|
||||
#: ../../helpdesk/advanced/after_sales.rst:69
|
||||
msgid ":doc:`../../manufacturing/repair/repair`"
|
||||
msgstr ""
|
||||
|
||||
#: ../../helpdesk/getting_started.rst:3
|
||||
msgid "Get started with Odoo Helpdesk"
|
||||
#: ../../helpdesk/advanced/close_tickets.rst:3
|
||||
msgid "Allow Customers to Close their Tickets"
|
||||
msgstr ""
|
||||
|
||||
#: ../../helpdesk/getting_started.rst:6
|
||||
#: ../../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/advanced/close_tickets.rst:9
|
||||
msgid "Configure the feature"
|
||||
msgstr ""
|
||||
|
||||
#: ../../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/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/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/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/advanced/close_tickets.rst:36
|
||||
msgid "The Costumer Portal"
|
||||
msgstr ""
|
||||
|
||||
#: ../../helpdesk/advanced/close_tickets.rst:38
|
||||
msgid "Now, once the user logs into his Portal, the option *Close this ticket* is available."
|
||||
msgstr ""
|
||||
|
||||
#: ../../helpdesk/advanced/close_tickets.rst:45
|
||||
msgid "Get reports on tickets closed by costumers"
|
||||
msgstr ""
|
||||
|
||||
#: ../../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/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 developer mode. To do this go to your settings module, and select the link for \"Activate the developer mode\" on the lower right-hand side."
|
||||
#: ../../helpdesk/overview/forum_and_elearning.rst:45
|
||||
msgid "eLearning"
|
||||
msgstr ""
|
||||
|
||||
#: ../../helpdesk/getting_started.rst:47
|
||||
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:53
|
||||
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:56
|
||||
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:58
|
||||
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:64
|
||||
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:71
|
||||
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:78
|
||||
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:86
|
||||
msgid "The final option to submit tickets is thru 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:91
|
||||
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:93
|
||||
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 "Team’s productivity and visibility"
|
||||
msgstr ""
|
||||
|
||||
#: ../../helpdesk/getting_started.rst:101
|
||||
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:104
|
||||
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:108
|
||||
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:110
|
||||
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:117
|
||||
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:123
|
||||
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 team’s tickets. Therefore, ticket’s 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:125
|
||||
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:132
|
||||
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:134
|
||||
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:137
|
||||
msgid "Grey - Normal State"
|
||||
#: ../../helpdesk/overview/getting_started.rst:64
|
||||
msgid ":doc:`../../general/odoo_basics/add_user`"
|
||||
msgstr ""
|
||||
|
||||
#: ../../helpdesk/getting_started.rst:139
|
||||
msgid "Red - Blocked"
|
||||
#: ../../helpdesk/overview/ratings.rst:3
|
||||
msgid "Ratings"
|
||||
msgstr ""
|
||||
|
||||
#: ../../helpdesk/getting_started.rst:141
|
||||
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 customer’s decision and open space for feedback that can help you improve the quality of your services."
|
||||
msgstr ""
|
||||
|
||||
#: ../../helpdesk/getting_started.rst:143
|
||||
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:150
|
||||
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:152
|
||||
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:159
|
||||
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:165
|
||||
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:169
|
||||
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 team’s name on their ticket, customers can see its ratings."
|
||||
msgstr ""
|
||||
|
||||
#: ../../helpdesk/getting_started.rst:171
|
||||
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:176
|
||||
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 customer’s 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/overview/reports.rst:14
|
||||
msgid "The number of tickets *grouped by* team and ticket type."
|
||||
msgstr ""
|
||||
|
||||
#: ../../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 team’s 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 ticket’s creation date, and a deadline is set on the ticket’s 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/timesheet_and_invoice/reinvoice_from_project.rst:10
|
||||
msgid "Configuration"
|
||||
msgstr ""
|
||||
|
||||
#: ../../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/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/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/timesheet_and_invoice/reinvoice_from_project.rst:31
|
||||
msgid "*Create Sales Order* and proceed to create the invoice."
|
||||
msgstr ""
|
||||
|
||||
|
||||
@ -6,9 +6,9 @@
|
||||
#, fuzzy
|
||||
msgid ""
|
||||
msgstr ""
|
||||
"Project-Id-Version: Odoo 11.0\n"
|
||||
"Project-Id-Version: Odoo 13.0\n"
|
||||
"Report-Msgid-Bugs-To: \n"
|
||||
"POT-Creation-Date: 2018-10-19 10:03+0200\n"
|
||||
"POT-Creation-Date: 2020-09-22 16:26+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"
|
||||
|
||||
File diff suppressed because it is too large
Load Diff
@ -8,7 +8,7 @@ msgid ""
|
||||
msgstr ""
|
||||
"Project-Id-Version: Odoo 13.0\n"
|
||||
"Report-Msgid-Bugs-To: \n"
|
||||
"POT-Creation-Date: 2019-11-20 10:20+0100\n"
|
||||
"POT-Creation-Date: 2020-09-22 16:26+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 ""
|
||||
|
||||
@ -105,7 +113,7 @@ msgid "Updating your SD Card with Etcher"
|
||||
msgstr ""
|
||||
|
||||
#: ../../iot/config/flash_sdcard.rst:11
|
||||
msgid "Go to Balena’s website and download `Etcher <http://wwww.balena.org>`__, It’s a free and open-source utility used for burning image files. Install and launch it."
|
||||
msgid "Go to Balena’s website and download `Etcher <https://www.balena.io/>`__, It’s a free and open-source utility used for burning image files. Install and launch it."
|
||||
msgstr ""
|
||||
|
||||
#: ../../iot/config/flash_sdcard.rst:15
|
||||
@ -137,11 +145,11 @@ 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:23
|
||||
msgid "You can find the documentation about SD card flashing here (`here <https://docs.google.com/document/d/1bqKsZhWqMqI4mhv4ltF61M_QPiBCHygYjjvkhsCTdaY/edit>`__)."
|
||||
#: ../../iot/config/iot_notfound.rst:24
|
||||
msgid ":doc:`flash_sdcard`"
|
||||
msgstr ""
|
||||
|
||||
#: ../../iot/config/pos.rst:3
|
||||
@ -197,7 +205,7 @@ msgid "Set Up"
|
||||
msgstr ""
|
||||
|
||||
#: ../../iot/config/pos.rst:37
|
||||
msgid "To connect hardware to the PoS, the first step is to connect an IoT Box to your database. For this, follow this `documentation <https://docs.google.com/document/d/1vhWrSSlSdJcRYe4tjPpXKYVMTD47lVK3ysyYc7tJDlA/edit#>`__."
|
||||
msgid "To connect hardware to the PoS, the first step is to connect an IoT Box to your database. For this, follow this :doc:`documentation <connect>`."
|
||||
msgstr ""
|
||||
|
||||
#: ../../iot/config/pos.rst:44
|
||||
@ -233,7 +241,7 @@ msgid "**Wi-Fi**: The current version of the IoT Box has Wi-Fi built in. Make su
|
||||
msgstr ""
|
||||
|
||||
#: ../../iot/config/pos.rst:73
|
||||
msgid "Once it's done, you can connect the IoT Box to your PoS. For this, go in Point of Sale > Configuration > PoS, tick the box \"IoT Box\" and select the IoT Box you want to connect with. Save the changes."
|
||||
msgid "Once it's done, you can connect the IoT Box to your PoS. For this, go in :menuselection:`Point of Sale --> Configuration --> PoS`, tick the box \"IoT Box\" and select the IoT Box you want to connect with. Save the changes."
|
||||
msgstr ""
|
||||
|
||||
#: ../../iot/config/pos.rst:77
|
||||
|
||||
@ -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-22 16:26+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 terminal’s 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 ""
|
||||
|
||||
|
||||
@ -8,7 +8,7 @@ msgid ""
|
||||
msgstr ""
|
||||
"Project-Id-Version: Odoo 13.0\n"
|
||||
"Report-Msgid-Bugs-To: \n"
|
||||
"POT-Creation-Date: 2019-11-20 10:20+0100\n"
|
||||
"POT-Creation-Date: 2020-09-22 16:26+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"
|
||||
@ -101,54 +101,54 @@ msgid "You can use BoMs without routings. You will use this if you choose to man
|
||||
msgstr ""
|
||||
|
||||
#: ../../manufacturing/management/bill_configuration.rst:24
|
||||
msgid "Before creating your *BoM*, you have to create the product using the *BoM* and, at least, one of the components. Go to the *Master Data* menu > *Products* and create both the finished product and the component."
|
||||
msgid "Before creating your *BoM*, you have to create the product using the *BoM* and, at least, one of the components. Go to the :menuselection:`Master Data menu --> Products` and create both the finished product and the component."
|
||||
msgstr ""
|
||||
|
||||
#: ../../manufacturing/management/bill_configuration.rst:29
|
||||
#: ../../manufacturing/management/bill_configuration.rst:28
|
||||
msgid "Once done, go to the *Bills of Materials* menu under *Master Data*. Now, create it. Choose the product from the dropdown menu and add your components and the quantity. In this case, keep the default *BoM* type, which is *Manufacture this Product*."
|
||||
msgstr ""
|
||||
|
||||
#: ../../manufacturing/management/bill_configuration.rst:38
|
||||
#: ../../manufacturing/management/bill_configuration.rst:37
|
||||
msgid "Using the same BoM to describe Variants"
|
||||
msgstr ""
|
||||
|
||||
#: ../../manufacturing/management/bill_configuration.rst:40
|
||||
#: ../../manufacturing/management/bill_configuration.rst:39
|
||||
msgid "As said above, you can use *BoM* for *Product Variants*. It is basically the same as for the standard product."
|
||||
msgstr ""
|
||||
|
||||
#: ../../manufacturing/management/bill_configuration.rst:43
|
||||
#: ../../manufacturing/management/bill_configuration.rst:42
|
||||
msgid "If your *BoM* is for one variant only, then specify which one in the *Product Variant* field. If not, specify the variant it is consumed for on each component line. You can add several variants for each component."
|
||||
msgstr ""
|
||||
|
||||
#: ../../manufacturing/management/bill_configuration.rst:52
|
||||
#: ../../manufacturing/management/bill_configuration.rst:51
|
||||
msgid "Adding a routing"
|
||||
msgstr ""
|
||||
|
||||
#: ../../manufacturing/management/bill_configuration.rst:54
|
||||
#: ../../manufacturing/management/bill_configuration.rst:53
|
||||
msgid "You can add routing to your *BoM*. You will do this if you need to define a series of operations required by your manufacturing process. To use it, enable the *Work Orders* feature in the *Manufacturing* app settings."
|
||||
msgstr ""
|
||||
|
||||
#: ../../manufacturing/management/bill_configuration.rst:63
|
||||
#: ../../manufacturing/management/bill_configuration.rst:62
|
||||
msgid "Each *BoM* can have only one routing while each routing can be used multiple times."
|
||||
msgstr ""
|
||||
|
||||
#: ../../manufacturing/management/bill_configuration.rst:66
|
||||
#: ../../manufacturing/management/bill_configuration.rst:65
|
||||
msgid "Now that you have created your routing, add it to your *BoM*. You can select when, in the work operations, your components are consumed with the dropdown menu."
|
||||
msgstr ""
|
||||
|
||||
#: ../../manufacturing/management/bill_configuration.rst:74
|
||||
#: ../../manufacturing/management/bill_configuration.rst:73
|
||||
msgid "Adding By-Products"
|
||||
msgstr ""
|
||||
|
||||
#: ../../manufacturing/management/bill_configuration.rst:76
|
||||
#: ../../manufacturing/management/bill_configuration.rst:75
|
||||
msgid "In Odoo, a *by-product* is any product produced by a *BoM* in addition to the primary product."
|
||||
msgstr ""
|
||||
|
||||
#: ../../manufacturing/management/bill_configuration.rst:79
|
||||
#: ../../manufacturing/management/bill_configuration.rst:78
|
||||
msgid "To add *by-products* to a *BoM*, you will first need to enable them from the *Manufacturing* app settings."
|
||||
msgstr ""
|
||||
|
||||
#: ../../manufacturing/management/bill_configuration.rst:85
|
||||
#: ../../manufacturing/management/bill_configuration.rst:84
|
||||
msgid "Once the feature is enabled, you can add your *By-Products* to your *BoMs*. You can add as many *By-Products* as you want. Just keep in mind that you need to register during which operation your by-product is produced."
|
||||
msgstr ""
|
||||
|
||||
@ -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 some finished products through subcontractors. This can be easily managed through Odoo."
|
||||
msgid "Outsourcing a portion of some or all your company’s 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 *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 *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*."
|
||||
#: ../../manufacturing/management/subcontracting.rst:13
|
||||
msgid "Control incoming goods quality;"
|
||||
msgstr ""
|
||||
|
||||
#: ../../manufacturing/management/subcontracting.rst:22
|
||||
msgid "You can also define subcontractors on the BoM."
|
||||
#: ../../manufacturing/management/subcontracting.rst:14
|
||||
msgid "Control subcontractors bills."
|
||||
msgstr ""
|
||||
|
||||
#: ../../manufacturing/management/subcontracting.rst:24
|
||||
msgid "If no subcontractor is set, the BoM can be used by any subcontractor"
|
||||
#: ../../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:26
|
||||
msgid "If some are set, the BoM can only be used for those subcontractors"
|
||||
#: ../../manufacturing/management/subcontracting.rst:23
|
||||
msgid "With its subcontracting feature, Odoo helps you handle this flow easily."
|
||||
msgstr ""
|
||||
|
||||
#: ../../manufacturing/management/subcontracting.rst:32
|
||||
msgid "Receive or buy a subcontracted product"
|
||||
#: ../../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:34
|
||||
msgid "You have two options to trigger the subcontracting of a product:"
|
||||
msgstr ""
|
||||
|
||||
#: ../../manufacturing/management/subcontracting.rst:36
|
||||
msgid "**Option A**: You can buy the subcontracted product from your subcontractor"
|
||||
#: ../../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 "Let’s 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, it’s 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 subcontractor’s 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 subcontractor’s location (4);"
|
||||
msgstr ""
|
||||
|
||||
#: ../../manufacturing/management/subcontracting.rst:62
|
||||
msgid "From Subcontracting to Stock"
|
||||
#: ../../manufacturing/management/subcontracting.rst:71
|
||||
msgid "Move products from the subcontractor’s 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 subcontractor’s warehouse. It is configured as an internal location, the components that are sent to the subcontractor are still valued in your stock."
|
||||
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."
|
||||
msgstr ""
|
||||
|
||||
#: ../../manufacturing/management/subcontracting.rst:73
|
||||
msgid "Resupply the subcontractor with the components"
|
||||
msgstr ""
|
||||
|
||||
#: ../../manufacturing/management/subcontracting.rst:75
|
||||
msgid "There are 3 ways to manage the resupply of your subcontractor with the components:"
|
||||
msgstr ""
|
||||
|
||||
#: ../../manufacturing/management/subcontracting.rst:80
|
||||
msgid "**Manually**: You create a delivery order in which you set the"
|
||||
#: ../../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:79
|
||||
msgid "subcontractor as a partner and you choose the components to deliver."
|
||||
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:85
|
||||
msgid "Inventory Valuation"
|
||||
msgstr ""
|
||||
|
||||
#: ../../manufacturing/management/subcontracting.rst:87
|
||||
msgid "The cost of the manufactured product “C” is defined as:"
|
||||
msgstr ""
|
||||
|
||||
#: ../../manufacturing/management/subcontracting.rst:89
|
||||
msgid "**With reordering rules**: You can define a *reordering rule*"
|
||||
msgid "**C = A + B + s**"
|
||||
msgstr ""
|
||||
|
||||
#: ../../manufacturing/management/subcontracting.rst:86
|
||||
msgid "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."
|
||||
#: ../../manufacturing/management/subcontracting.rst:91
|
||||
msgid "With:"
|
||||
msgstr ""
|
||||
|
||||
#: ../../manufacturing/management/subcontracting.rst:97
|
||||
msgid "**On order**: You can also deliver the components to your"
|
||||
#: ../../manufacturing/management/subcontracting.rst:93
|
||||
msgid "**A**: Cost of raw materials coming from YourCompany;"
|
||||
msgstr ""
|
||||
|
||||
#: ../../manufacturing/management/subcontracting.rst:95
|
||||
msgid "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:96
|
||||
msgid "**B**: Cost of raw materials sourced directly from the"
|
||||
msgstr ""
|
||||
|
||||
#: ../../manufacturing/management/subcontracting.rst:96
|
||||
msgid "subcontractor;"
|
||||
msgstr ""
|
||||
|
||||
#: ../../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 "If managing the replenishment of raw materials **B** at your subcontractor’s location is not needed, simply include the cost of **B** in the subcontractor’s price **s** and remove the products *B* from the *BoM*."
|
||||
msgstr ""
|
||||
|
||||
#: ../../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
|
||||
@ -661,7 +765,7 @@ msgid "The Master Production Schedule (MPS) is a valuable tool to plan your prod
|
||||
msgstr ""
|
||||
|
||||
#: ../../manufacturing/management/use_mps.rst:11
|
||||
msgid "Go to the *Manufacturing app > Configuration > Settings* and activate the Master Production Schedule feature before hitting save."
|
||||
msgid "Go to the :menuselection:`Manufacturing app --> Configuration --> Settings` and activate the Master Production Schedule feature before hitting save."
|
||||
msgstr ""
|
||||
|
||||
#: ../../manufacturing/management/use_mps.rst:18
|
||||
@ -669,7 +773,7 @@ msgid "In the manufacturing settings, you can define the time range of your MPS
|
||||
msgstr ""
|
||||
|
||||
#: ../../manufacturing/management/use_mps.rst:20
|
||||
msgid "Now, go in *Planning > Master Production Schedule* and click on add a product. You can now define your safety stock target (= the stock you want to have on hand at the end of the period) and the minimum and maximum quantities to replenish."
|
||||
msgid "Now, go in :menuselection:`Planning --> Master Production Schedule` and click on add a product. You can now define your safety stock target (= the stock you want to have on hand at the end of the period) and the minimum and maximum quantities to replenish."
|
||||
msgstr ""
|
||||
|
||||
#: ../../manufacturing/management/use_mps.rst:29
|
||||
@ -760,35 +864,35 @@ msgstr ""
|
||||
msgid "Repair Management"
|
||||
msgstr ""
|
||||
|
||||
#: ../../manufacturing/repair/repair.rst:3
|
||||
#: ../../manufacturing/repair/repair.rst:5
|
||||
msgid "Repair products"
|
||||
msgstr ""
|
||||
|
||||
#: ../../manufacturing/repair/repair.rst:5
|
||||
#: ../../manufacturing/repair/repair.rst:7
|
||||
msgid "The Odoo *Repair* app allows you to manage a complete after sales process but also to simply repair products you have manufactured, if they present a defect."
|
||||
msgstr ""
|
||||
|
||||
#: ../../manufacturing/repair/repair.rst:10
|
||||
#: ../../manufacturing/repair/repair.rst:12
|
||||
msgid "Create a Repair Order"
|
||||
msgstr ""
|
||||
|
||||
#: ../../manufacturing/repair/repair.rst:12
|
||||
#: ../../manufacturing/repair/repair.rst:14
|
||||
msgid "Once in the app, you can access your existing *Repair Orders* and create a new one."
|
||||
msgstr ""
|
||||
|
||||
#: ../../manufacturing/repair/repair.rst:19
|
||||
#: ../../manufacturing/repair/repair.rst:21
|
||||
msgid "Manage a repair"
|
||||
msgstr ""
|
||||
|
||||
#: ../../manufacturing/repair/repair.rst:21
|
||||
#: ../../manufacturing/repair/repair.rst:23
|
||||
msgid "When a customer sends you a product for repair, create a new *Repair Order*. Fill it in with all the information you may need such as the product, the customer, if it has to be invoiced after or before the repair, the parts you might need, etc."
|
||||
msgstr ""
|
||||
|
||||
#: ../../manufacturing/repair/repair.rst:29
|
||||
#: ../../manufacturing/repair/repair.rst:31
|
||||
msgid "Once everything is done, you can then send the repair quotation to your customer. If it is approved, you can confirm the repair. You will then be able to start & end the repair when it is completed."
|
||||
msgstr ""
|
||||
|
||||
#: ../../manufacturing/repair/repair.rst:36
|
||||
#: ../../manufacturing/repair/repair.rst:38
|
||||
msgid "You can now invoice the repair."
|
||||
msgstr ""
|
||||
|
||||
|
||||
284
locale/sources/marketing_automation.pot
Normal file
284
locale/sources/marketing_automation.pot
Normal file
@ -0,0 +1,284 @@
|
||||
# SOME DESCRIPTIVE TITLE.
|
||||
# Copyright (C) 2015-TODAY, Odoo S.A.
|
||||
# This file is distributed under the same license as the Odoo package.
|
||||
# FIRST AUTHOR <EMAIL@ADDRESS>, YEAR.
|
||||
#
|
||||
#, fuzzy
|
||||
msgid ""
|
||||
msgstr ""
|
||||
"Project-Id-Version: Odoo 13.0\n"
|
||||
"Report-Msgid-Bugs-To: \n"
|
||||
"POT-Creation-Date: 2020-09-22 16:26+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"
|
||||
"MIME-Version: 1.0\n"
|
||||
"Content-Type: text/plain; charset=UTF-8\n"
|
||||
"Content-Transfer-Encoding: 8bit\n"
|
||||
|
||||
#: ../../marketing_automation.rst:5
|
||||
msgid "Marketing Automation"
|
||||
msgstr ""
|
||||
|
||||
#: ../../marketing_automation/advanced.rst:3
|
||||
msgid "Advanced"
|
||||
msgstr ""
|
||||
|
||||
#: ../../marketing_automation/advanced/understanding_metrics.rst:3
|
||||
msgid "Understanding Metrics"
|
||||
msgstr ""
|
||||
|
||||
#: ../../marketing_automation/advanced/understanding_metrics.rst:4
|
||||
msgid "Metrics are values that help you measure progress and can be a powerful way of linking your employees to goals."
|
||||
msgstr ""
|
||||
|
||||
#: ../../marketing_automation/advanced/understanding_metrics.rst:9
|
||||
msgid "When you create a workflow in Odoo, its visual content already shows metrics in a graph form and in numbers."
|
||||
msgstr ""
|
||||
|
||||
#: ../../marketing_automation/advanced/understanding_metrics.rst:10
|
||||
msgid "Let’s consider the example below:"
|
||||
msgstr ""
|
||||
|
||||
#: ../../marketing_automation/advanced/understanding_metrics.rst:19
|
||||
msgid "The *Target* - business object - is *Lead/Opportunity* and was narrowed down to the ones whose *Tag Name* contain the description “Product”, and have an email address set."
|
||||
msgstr ""
|
||||
|
||||
#: ../../marketing_automation/advanced/understanding_metrics.rst:20
|
||||
msgid "A total number of 20 records match the criteria."
|
||||
msgstr ""
|
||||
|
||||
#: ../../marketing_automation/advanced/understanding_metrics.rst:28
|
||||
msgid "Out of those 20 records, 25 have become participants, in other words, they have matched the criteria."
|
||||
msgstr ""
|
||||
|
||||
#: ../../marketing_automation/advanced/understanding_metrics.rst:36
|
||||
msgid "Every time the system runs, updating numbers and triggering actions, it will look at the *Target* model and check if new records have been added or modified, keeping the flow up-to-date."
|
||||
msgstr ""
|
||||
|
||||
#: ../../marketing_automation/advanced/understanding_metrics.rst:41
|
||||
msgid "The filter here is applied to *all* activities. Leads that lose the tag in the meantime will be excluded from later activities."
|
||||
msgstr ""
|
||||
|
||||
#: ../../marketing_automation/advanced/understanding_metrics.rst:45
|
||||
msgid "*Records* is a real-time number, therefore while the workflow is running, changes in opportunity records can be made - delete, add, adjustment - updating the number of records, but not changing the number of participants, as the metric *will not* exclude opportunities that have been set as participants before. It will just add new ones. For this reason, the number of *Records* can be different from the number of *Participants*."
|
||||
msgstr ""
|
||||
|
||||
#: ../../marketing_automation/advanced/understanding_metrics.rst:0
|
||||
msgid "You can also have filters applied to activities individually, under *Domain*. A useful feature to specify an individual filter that will only be performed if the records satisfied both filters, the activity and its domain one."
|
||||
msgstr ""
|
||||
|
||||
#: ../../marketing_automation/advanced/understanding_metrics.rst:0
|
||||
msgid "Example: for an activity sending an SMS, you could make sure a phone number is set to avoid triggering a SMS that would never be sent and crash."
|
||||
msgstr ""
|
||||
|
||||
#: ../../marketing_automation/advanced/understanding_metrics.rst:64
|
||||
msgid "*Success* is the number of times the searching for participants - that match the filter(s) of that activity - was performed successfully in relation to the total number of participants."
|
||||
msgstr ""
|
||||
|
||||
#: ../../marketing_automation/advanced/understanding_metrics.rst:65
|
||||
msgid "If a participant does not match the conditions, it will be added to *Rejected*."
|
||||
msgstr ""
|
||||
|
||||
#: ../../marketing_automation/advanced/understanding_metrics.rst:71
|
||||
msgid "Hovering over the graph, you can see the number of successful and rejected participants, per day, for the last 15 days."
|
||||
msgstr ""
|
||||
|
||||
#: ../../marketing_automation/advanced/understanding_metrics.rst:75
|
||||
msgid "Every time a new record is added to the *Target* model, it will be automatically added to the workflow, and, it will start the workflow from the beginning (parent action)."
|
||||
msgstr ""
|
||||
|
||||
#: ../../marketing_automation/advanced/understanding_metrics.rst:79
|
||||
msgid ":doc:`../overview/automate_actions`"
|
||||
msgstr ""
|
||||
|
||||
#: ../../marketing_automation/advanced/understanding_metrics.rst:80
|
||||
msgid ":doc:`../overview/segment`"
|
||||
msgstr ""
|
||||
|
||||
#: ../../marketing_automation/advanced/understanding_metrics.rst:81
|
||||
msgid ":doc:`../overview/test`"
|
||||
msgstr ""
|
||||
|
||||
#: ../../marketing_automation/overview.rst:3
|
||||
msgid "Overview"
|
||||
msgstr ""
|
||||
|
||||
#: ../../marketing_automation/overview/automate_actions.rst:3
|
||||
msgid "Automate Actions and Create a Workflow"
|
||||
msgstr ""
|
||||
|
||||
#: ../../marketing_automation/overview/automate_actions.rst:4
|
||||
msgid "Automated workflows are a sign that you are building intelligent, data-driven, multifaceted campaigns to enable the delivery of the right message, to the right prospects, at the right time. It also speeds up processes and creates a seamless experience for employees."
|
||||
msgstr ""
|
||||
|
||||
#: ../../marketing_automation/overview/automate_actions.rst:9
|
||||
msgid "Segment and create a campaign"
|
||||
msgstr ""
|
||||
|
||||
#: ../../marketing_automation/overview/automate_actions.rst:10
|
||||
msgid "Go to :menuselection:`Campaigns --> Create`."
|
||||
msgstr ""
|
||||
|
||||
#: ../../marketing_automation/overview/automate_actions.rst:12
|
||||
msgid "In the example below, the *Marketing Automation* application is fully integrated with *Contacts*."
|
||||
msgstr ""
|
||||
|
||||
#: ../../marketing_automation/overview/automate_actions.rst:14
|
||||
msgid "But it can also be integrated with other apps like CRM, as long as they are installed in your database."
|
||||
msgstr ""
|
||||
|
||||
#: ../../marketing_automation/overview/automate_actions.rst:23
|
||||
msgid "Depending on the criteria, the *target model updates itself* while the campaign is running. That means that every new record that meets the criteria will be added to the workflow."
|
||||
msgstr ""
|
||||
|
||||
#: ../../marketing_automation/overview/automate_actions.rst:25
|
||||
msgid "Example: a campaign starts for leads that have no salesman assigned. If at some point, those leads get to have a salesman assigned to it, the campaign will stop running."
|
||||
msgstr ""
|
||||
|
||||
#: ../../marketing_automation/overview/automate_actions.rst:29
|
||||
msgid "Create a parent activity and start to build a workflow"
|
||||
msgstr ""
|
||||
|
||||
#: ../../marketing_automation/overview/automate_actions.rst:30
|
||||
msgid "Click on *Add new activity*."
|
||||
msgstr ""
|
||||
|
||||
#: ../../marketing_automation/overview/automate_actions.rst:37
|
||||
msgid "*Trigger* is the field to set for the activity to start to de deployed."
|
||||
msgstr ""
|
||||
|
||||
#: ../../marketing_automation/overview/automate_actions.rst:39
|
||||
msgid "Adopt an *Expiry Duration* if you would like to stop actions from being executed after a certain amount of time and in subsequence to the trigger."
|
||||
msgstr ""
|
||||
|
||||
#: ../../marketing_automation/overview/automate_actions.rst:42
|
||||
msgid "Under *Domain* you can narrow down your target, even more, applying filters for this specific activity."
|
||||
msgstr ""
|
||||
|
||||
#: ../../marketing_automation/overview/automate_actions.rst:47
|
||||
msgid "Add Child Activities"
|
||||
msgstr ""
|
||||
|
||||
#: ../../marketing_automation/overview/automate_actions.rst:48
|
||||
msgid "A *child activity* is an action that will take place based on a condition."
|
||||
msgstr ""
|
||||
|
||||
#: ../../marketing_automation/overview/automate_actions.rst:50
|
||||
msgid "You can either create or add a child activity if on the previous one: the email was opened or not, the email was replied or not, the link was clicked or not, the email bounced back."
|
||||
msgstr ""
|
||||
|
||||
#: ../../marketing_automation/overview/automate_actions.rst:59
|
||||
#: ../../marketing_automation/overview/test.rst:53
|
||||
msgid ":doc:`segment`"
|
||||
msgstr ""
|
||||
|
||||
#: ../../marketing_automation/overview/segment.rst:3
|
||||
msgid "Segment the Database with Filters"
|
||||
msgstr ""
|
||||
|
||||
#: ../../marketing_automation/overview/segment.rst:4
|
||||
msgid "Filters let you reach a granular level of detail in your records."
|
||||
msgstr ""
|
||||
|
||||
#: ../../marketing_automation/overview/segment.rst:7
|
||||
msgid "How to work with filters"
|
||||
msgstr ""
|
||||
|
||||
#: ../../marketing_automation/overview/segment.rst:8
|
||||
msgid "When working with filters, you will see that some of the rules have an arrow button next to it, informing you that the parameter has more variables within it."
|
||||
msgstr ""
|
||||
|
||||
#: ../../marketing_automation/overview/segment.rst:18
|
||||
msgid "More than one parameter line - *node* (+) - can be added under what is called a *branch* (...)."
|
||||
msgstr ""
|
||||
|
||||
#: ../../marketing_automation/overview/segment.rst:19
|
||||
msgid "To exclude a *node* or a *branch*, click on *Delete node* (x)."
|
||||
msgstr ""
|
||||
|
||||
#: ../../marketing_automation/overview/segment.rst:27
|
||||
msgid "Every time a new branch is created, you can choose if you would like the records to match *all* criteria of the upcoming rules, or *any*, meaning one rule or the other."
|
||||
msgstr ""
|
||||
|
||||
#: ../../marketing_automation/overview/segment.rst:32
|
||||
msgid "Use cases"
|
||||
msgstr ""
|
||||
|
||||
#: ../../marketing_automation/overview/segment.rst:34
|
||||
msgid "**Scenario**: narrow the target down to new opportunities in the pipeline."
|
||||
msgstr ""
|
||||
|
||||
#: ../../marketing_automation/overview/segment.rst:39
|
||||
msgid "**Scenario**: narrow the target down to suppliers."
|
||||
msgstr ""
|
||||
|
||||
#: ../../marketing_automation/overview/segment.rst:44
|
||||
msgid "**Scenario**: narrow the leads down to the ones that contain a certain tag name."
|
||||
msgstr ""
|
||||
|
||||
#: ../../marketing_automation/overview/segment.rst:49
|
||||
msgid "**Scenario**: narrow the target down to the attendees of a specific event that purchase a specific category of ticket."
|
||||
msgstr ""
|
||||
|
||||
#: ../../marketing_automation/overview/segment.rst:55
|
||||
msgid "**Scenario**: narrow the target down to the employees who have kids."
|
||||
msgstr ""
|
||||
|
||||
#: ../../marketing_automation/overview/segment.rst:60
|
||||
msgid "**Scenario**: narrow the target down to records with a helpdesk ticket solved."
|
||||
msgstr ""
|
||||
|
||||
#: ../../marketing_automation/overview/segment.rst:66
|
||||
#: ../../marketing_automation/overview/test.rst:52
|
||||
msgid ":doc:`automate_actions`"
|
||||
msgstr ""
|
||||
|
||||
#: ../../marketing_automation/overview/segment.rst:67
|
||||
msgid ":doc:`../../general/tags/take_tags`"
|
||||
msgstr ""
|
||||
|
||||
#: ../../marketing_automation/overview/test.rst:3
|
||||
msgid "Launch a Test and Start a Campaign"
|
||||
msgstr ""
|
||||
|
||||
#: ../../marketing_automation/overview/test.rst:4
|
||||
msgid "Before starting a campaign, launching a test allows you to run the workflow on a test contact and view the sequence of events in action, avoiding mistakes."
|
||||
msgstr ""
|
||||
|
||||
#: ../../marketing_automation/overview/test.rst:8
|
||||
msgid "Launch a test"
|
||||
msgstr ""
|
||||
|
||||
#: ../../marketing_automation/overview/test.rst:9
|
||||
msgid "Click on *Launch a test*."
|
||||
msgstr ""
|
||||
|
||||
#: ../../marketing_automation/overview/test.rst:12
|
||||
msgid "Once you have selected the test contact, *Run* the parent activity and the subsequent ones as needed. *Run* and *Stop* activities individually. To stop the whole workflow click on *Stop*."
|
||||
msgstr ""
|
||||
|
||||
#: ../../marketing_automation/overview/test.rst:22
|
||||
msgid "Launching a test does not add data to your metrics with the purpose of not introducing wrong inputs to reports."
|
||||
msgstr ""
|
||||
|
||||
#: ../../marketing_automation/overview/test.rst:27
|
||||
msgid "Start and stop a workflow"
|
||||
msgstr ""
|
||||
|
||||
#: ../../marketing_automation/overview/test.rst:28
|
||||
msgid "Click on *Start* to run the workflow, and on *Stop* to interrupt it. The interruption and new start can happen at any moment. The current status will be shown on the status bar."
|
||||
msgstr ""
|
||||
|
||||
#: ../../marketing_automation/overview/test.rst:38
|
||||
msgid "Participants and their specific workflow"
|
||||
msgstr ""
|
||||
|
||||
#: ../../marketing_automation/overview/test.rst:39
|
||||
msgid "*Participants* are all the records that have ever been involved in the campaign."
|
||||
msgstr ""
|
||||
|
||||
#: ../../marketing_automation/overview/test.rst:47
|
||||
msgid "If you click on *Participants* and open a record, you will find the specific activities the record went/are/will go through, as well as when the workflow was triggered to him. If you wish to cancel an activity click on *Cancel*."
|
||||
msgstr ""
|
||||
|
||||
@ -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-22 16:26+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"
|
||||
@ -29,6 +29,6 @@ msgid "As of Odoo 12.0, 13.0 or above, there is no more complex configuration to
|
||||
msgstr ""
|
||||
|
||||
#: ../../mobile/firebase.rst:13
|
||||
msgid "Simply go to *Settings* > *General Settings* > *Odoo Cloud Notification (OCN)* and make sure that **Push Notifications** is checked."
|
||||
msgid "Simply go to :menuselection:`Settings --> General Settings --> Odoo Cloud Notification (OCN)` and make sure that **Push Notifications** is checked."
|
||||
msgstr ""
|
||||
|
||||
|
||||
118
locale/sources/planning.pot
Normal file
118
locale/sources/planning.pot
Normal file
@ -0,0 +1,118 @@
|
||||
# SOME DESCRIPTIVE TITLE.
|
||||
# Copyright (C) 2015-TODAY, Odoo S.A.
|
||||
# This file is distributed under the same license as the Odoo package.
|
||||
# FIRST AUTHOR <EMAIL@ADDRESS>, YEAR.
|
||||
#
|
||||
#, fuzzy
|
||||
msgid ""
|
||||
msgstr ""
|
||||
"Project-Id-Version: Odoo 13.0\n"
|
||||
"Report-Msgid-Bugs-To: \n"
|
||||
"POT-Creation-Date: 2020-09-22 16:26+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"
|
||||
"MIME-Version: 1.0\n"
|
||||
"Content-Type: text/plain; charset=UTF-8\n"
|
||||
"Content-Transfer-Encoding: 8bit\n"
|
||||
|
||||
#: ../../planning.rst:5
|
||||
msgid "Planning"
|
||||
msgstr ""
|
||||
|
||||
#: ../../planning/overview.rst:3
|
||||
msgid "Overview"
|
||||
msgstr ""
|
||||
|
||||
#: ../../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/overview/duplicate_a_planning.rst:9
|
||||
msgid "Organize your team by roles"
|
||||
msgstr ""
|
||||
|
||||
#: ../../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/overview/duplicate_a_planning.rst:20
|
||||
msgid "Make shifts recurrent"
|
||||
msgstr ""
|
||||
|
||||
#: ../../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/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/overview/duplicate_a_planning.rst:38
|
||||
msgid "To duplicate a shift in the Gantt view, press CTRL + drag and drop."
|
||||
msgstr ""
|
||||
|
||||
#: ../../planning/overview/duplicate_a_planning.rst:41
|
||||
msgid "Save shifts as templates"
|
||||
msgstr ""
|
||||
|
||||
#: ../../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/overview/duplicate_a_planning.rst:51
|
||||
msgid "To create a template in advance, go to :menuselection:`Configuration --> Shifts Templates --> Create`."
|
||||
msgstr ""
|
||||
|
||||
#: ../../planning/overview/duplicate_a_planning.rst:55
|
||||
msgid "Duplicate a planning from the previous week"
|
||||
msgstr ""
|
||||
|
||||
#: ../../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/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/overview/send_planned_shifts.rst:3
|
||||
msgid "Send Planned Shifts and Give Employees Autonomy Over Shifts"
|
||||
msgstr ""
|
||||
|
||||
#: ../../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/overview/send_planned_shifts.rst:10
|
||||
msgid "Publish and send the planned week by email"
|
||||
msgstr ""
|
||||
|
||||
#: ../../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/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/overview/send_planned_shifts.rst:26
|
||||
msgid "Employees will not be able to see shifts until they have been published."
|
||||
msgstr ""
|
||||
|
||||
#: ../../planning/overview/send_planned_shifts.rst:29
|
||||
msgid "Let employees unassign themselves from shifts"
|
||||
msgstr ""
|
||||
|
||||
#: ../../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/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
@ -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-22 16:26+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"
|
||||
@ -24,8 +24,8 @@ msgstr ""
|
||||
msgid "In this section of the portal, you will find all the communications between you and Odoo: documents such as quotations, sales orders, invoices and subscriptions."
|
||||
msgstr ""
|
||||
|
||||
#: ../../portal/my_odoo_portal.rst:11
|
||||
msgid "To access this section, you have to log with your username and password to `Odoo <https://www.odoo.com/my/home>`__ . If you are already logged in, just click on your name on the top-right corner and select \"My Account\"."
|
||||
#: ../../portal/my_odoo_portal.rst:12
|
||||
msgid "To access this section, you have to log with your username and password to `Odoo <https://www.odoo.com/my/home>`_. If you are already logged in, just click on your name on the top-right corner and select \"My Account\"."
|
||||
msgstr ""
|
||||
|
||||
#: ../../portal/my_odoo_portal.rst:20
|
||||
@ -96,8 +96,8 @@ msgstr ""
|
||||
msgid "If you want to remove the credit cards that are saved, you can do so by clicking on \"Manage your payment methods\" at the bottom of the page. Click \"Delete\" to delete the payment method."
|
||||
msgstr ""
|
||||
|
||||
#: ../../portal/my_odoo_portal.rst:101
|
||||
msgid "At the date of the next invoice, if there is no payment information provided or if your credit card has expired, the status of your subscription will change to \"To Renew\". You will then have 7 days to provide a valid method of payment. After this delay, the subscription will be closed, and you will no longer be able to access the database."
|
||||
#: ../../portal/my_odoo_portal.rst:102
|
||||
msgid "At the date of the next invoice, if there is no payment information provided or if your credit card has expired, the status of your subscription will change to \"To Renew\". You will then have 7 days to provide a valid method of payment. After this delay, the subscription will be closed, and you will no longer be able to access the database."
|
||||
msgstr ""
|
||||
|
||||
#: ../../portal/my_odoo_portal.rst:108
|
||||
|
||||
@ -6,9 +6,9 @@
|
||||
#, fuzzy
|
||||
msgid ""
|
||||
msgstr ""
|
||||
"Project-Id-Version: Odoo 11.0\n"
|
||||
"Project-Id-Version: Odoo 13.0\n"
|
||||
"Report-Msgid-Bugs-To: \n"
|
||||
"POT-Creation-Date: 2018-10-19 10:03+0200\n"
|
||||
"POT-Creation-Date: 2020-09-22 16:26+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"
|
||||
|
||||
File diff suppressed because it is too large
Load Diff
@ -8,7 +8,7 @@ msgid ""
|
||||
msgstr ""
|
||||
"Project-Id-Version: Odoo 13.0\n"
|
||||
"Report-Msgid-Bugs-To: \n"
|
||||
"POT-Creation-Date: 2019-11-20 10:20+0100\n"
|
||||
"POT-Creation-Date: 2020-09-22 16:26+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"
|
||||
@ -77,7 +77,7 @@ msgid "See below a template of the columns used."
|
||||
msgstr ""
|
||||
|
||||
#: ../../purchase/purchases/master/import.rst:33
|
||||
msgid "`Template download <https://docs.google.com/spreadsheets/d/1N8c_eejLV_8NhYMGCfZau_oGCnRkUIT9nwdX7n0shhY/edit#gid=964193981>`__"
|
||||
msgid ":download:`Click here to download the template <../../../_static/example_files/vendor_pricelists_template.csv>`"
|
||||
msgstr ""
|
||||
|
||||
#: ../../purchase/purchases/master/suppliers.rst:3
|
||||
@ -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
|
||||
@ -529,99 +529,23 @@ msgstr ""
|
||||
msgid "Select your supplier in the **Vendor** menu, or create it on-the-fly by clicking on **Create and Edit**. In the **Order Date** field, select the date to which you wish to proceed to the actual order."
|
||||
msgstr ""
|
||||
|
||||
#: ../../purchase/purchases/rfq/create.rst:0
|
||||
msgid "Receipt"
|
||||
msgstr ""
|
||||
|
||||
#: ../../purchase/purchases/rfq/create.rst:0
|
||||
msgid "Incoming Shipments"
|
||||
msgstr ""
|
||||
|
||||
#: ../../purchase/purchases/rfq/create.rst:0
|
||||
msgid "Vendor"
|
||||
msgstr ""
|
||||
|
||||
#: ../../purchase/purchases/rfq/create.rst:0
|
||||
msgid "You can find a vendor by its Name, TIN, Email or Internal Reference."
|
||||
msgstr ""
|
||||
|
||||
#: ../../purchase/purchases/rfq/create.rst:0
|
||||
msgid "Vendor Reference"
|
||||
msgstr ""
|
||||
|
||||
#: ../../purchase/purchases/rfq/create.rst:0
|
||||
msgid "Reference of the sales order or bid sent by the vendor. It's used to do the matching when you receive the products as this reference is usually written on the delivery order sent by your vendor."
|
||||
msgstr ""
|
||||
|
||||
#: ../../purchase/purchases/rfq/create.rst:0
|
||||
msgid "Order Date"
|
||||
msgstr ""
|
||||
|
||||
#: ../../purchase/purchases/rfq/create.rst:0
|
||||
msgid "Depicts the date where the Quotation should be validated and converted into a purchase order."
|
||||
msgstr ""
|
||||
|
||||
#: ../../purchase/purchases/rfq/create.rst:0
|
||||
msgid "Source Document"
|
||||
msgstr ""
|
||||
|
||||
#: ../../purchase/purchases/rfq/create.rst:0
|
||||
msgid "Reference of the document that generated this purchase order request (e.g. a sales order)"
|
||||
msgstr ""
|
||||
|
||||
#: ../../purchase/purchases/rfq/create.rst:0
|
||||
msgid "Deliver To"
|
||||
msgstr ""
|
||||
|
||||
#: ../../purchase/purchases/rfq/create.rst:0
|
||||
msgid "This will determine operation type of incoming shipment"
|
||||
msgstr ""
|
||||
|
||||
#: ../../purchase/purchases/rfq/create.rst:0
|
||||
msgid "Drop Ship Address"
|
||||
msgstr ""
|
||||
|
||||
#: ../../purchase/purchases/rfq/create.rst:0
|
||||
msgid "Put an address if you want to deliver directly from the vendor to the customer. Otherwise, keep empty to deliver to your own company."
|
||||
msgstr ""
|
||||
|
||||
#: ../../purchase/purchases/rfq/create.rst:0
|
||||
msgid "Destination Location Type"
|
||||
msgstr ""
|
||||
|
||||
#: ../../purchase/purchases/rfq/create.rst:0
|
||||
msgid "Technical field used to display the Drop Ship Address"
|
||||
msgstr ""
|
||||
|
||||
#: ../../purchase/purchases/rfq/create.rst:0
|
||||
msgid "Incoterm"
|
||||
msgstr ""
|
||||
|
||||
#: ../../purchase/purchases/rfq/create.rst:0
|
||||
msgid "International Commercial Terms are a series of predefined commercial terms used in international transactions."
|
||||
msgstr ""
|
||||
|
||||
#: ../../purchase/purchases/rfq/create.rst:32
|
||||
msgid "View *Request for Quotation* in our Online Demonstration"
|
||||
msgstr ""
|
||||
|
||||
#: ../../purchase/purchases/rfq/create.rst:34
|
||||
#: ../../purchase/purchases/rfq/create.rst:28
|
||||
msgid "In **Products**, click on Add an item. Select the product you wish to order in the **Product** menu. Specify the **Quantity** by inserting the number and selecting the unit of measure. In the **Unit Price** field, specify the price you would like to be offered (you can also leave the field blank if you don't know what the price should be) , and add the expected delivery date in the Scheduled Date field. Click on **Save**, then **Print Rfq** or **Send Rfq by email** (make sure an email address is specified for this supplier or enter a new one)."
|
||||
msgstr ""
|
||||
|
||||
#: ../../purchase/purchases/rfq/create.rst:48
|
||||
#: ../../purchase/purchases/rfq/create.rst:40
|
||||
msgid "After having clicked on **Send**, you will notice that the RFQ's status will switch from **Draft** to **RFQ Sent**."
|
||||
msgstr ""
|
||||
|
||||
#: ../../purchase/purchases/rfq/create.rst:54
|
||||
#: ../../purchase/purchases/rfq/create.rst:46
|
||||
msgid "Once your supplier has replied with an offer, update the RfQ by clicking on **Edit** to fit the quotation (prices, taxes, expected delivery lead time, payment terms, etc.), then click on **Save** to issue a Purchase Order."
|
||||
msgstr ""
|
||||
|
||||
#: ../../purchase/purchases/rfq/create.rst:59
|
||||
#: ../../purchase/purchases/rfq/create.rst:51
|
||||
msgid "To proceed with the order, click on **Confirm Order** to send the order to the supplier. The RfQ's status will switch to **Purchase Order**."
|
||||
msgstr ""
|
||||
|
||||
#: ../../purchase/purchases/rfq/create.rst:65
|
||||
#: ../../purchase/purchases/rfq/create.rst:57
|
||||
msgid "The status of the RfQ will change to PURCHASE ORDER. Tabs in the upper right corner of the order will show 1 Shipment and 0 Invoice."
|
||||
msgstr ""
|
||||
|
||||
|
||||
@ -8,7 +8,7 @@ msgid ""
|
||||
msgstr ""
|
||||
"Project-Id-Version: Odoo 13.0\n"
|
||||
"Report-Msgid-Bugs-To: \n"
|
||||
"POT-Creation-Date: 2019-11-20 10:20+0100\n"
|
||||
"POT-Creation-Date: 2020-09-22 16:26+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"
|
||||
@ -124,7 +124,7 @@ msgid "Create the Quality Control Point"
|
||||
msgstr ""
|
||||
|
||||
#: ../../quality/checks/quality_mo.rst:18
|
||||
msgid "To create a quality control point, open the quality app and go to *Control > Control Points*. There, hit create. Make sure to select *Manufacturing* as operation and choose the type of quality check you want to perform."
|
||||
msgid "To create a quality control point, open the quality app and go to :menuselection:`Control --> Control Points`. There, hit create. Make sure to select *Manufacturing* as operation and choose the type of quality check you want to perform."
|
||||
msgstr ""
|
||||
|
||||
#: ../../quality/checks/quality_mo.rst:27
|
||||
@ -146,7 +146,7 @@ msgid "If you want to access all your quality checks, you can do this by opening
|
||||
msgstr ""
|
||||
|
||||
#: ../../quality/checks/quality_mo.rst:55
|
||||
msgid "If you want to create a *Quality Control Point*, open the *Quality* app and go to *Control > Control Points*. Then, click on create. Make sure to select *Manufacturing* as operation and select the work order operation on which the quality check should be performed."
|
||||
msgid "If you want to create a *Quality Control Point*, open the *Quality* app and go to :menuselection:`Control --> Control Points`. Then, click on create. Make sure to select *Manufacturing* as operation and select the work order operation on which the quality check should be performed."
|
||||
msgstr ""
|
||||
|
||||
#: ../../quality/checks/quality_mo.rst:64
|
||||
@ -166,7 +166,7 @@ msgid "Perform Quality Checks on Transfers"
|
||||
msgstr ""
|
||||
|
||||
#: ../../quality/checks/quality_transfers.rst:8
|
||||
msgid "To create a *Quality Control Point*, open the *Quality* application. Then, go to *Quality Control > Control Points > Create*. Now, you can define the quality control point you want to apply to a specific product. Don’t forget to select a transfer operation type."
|
||||
msgid "To create a *Quality Control Point*, open the *Quality* application. Then, go to :menuselection:`Quality Control --> Control Points --> Create`. Now, you can define the quality control point you want to apply to a specific product. Don’t forget to select a transfer operation type."
|
||||
msgstr ""
|
||||
|
||||
#: ../../quality/checks/quality_transfers.rst:19
|
||||
@ -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 *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 product’s 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 product’s 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 product’s 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 component’s 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
@ -8,7 +8,7 @@ msgid ""
|
||||
msgstr ""
|
||||
"Project-Id-Version: Odoo 13.0\n"
|
||||
"Report-Msgid-Bugs-To: \n"
|
||||
"POT-Creation-Date: 2019-11-20 10:20+0100\n"
|
||||
"POT-Creation-Date: 2020-09-22 16:26+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,355 +20,399 @@ msgstr ""
|
||||
msgid "SMS Marketing"
|
||||
msgstr ""
|
||||
|
||||
#: ../../sms_marketing/SMS_mkt_build_send-and_get_reports_from_a_SMS_mailing.rst:3
|
||||
msgid "Build, send and get reports from a SMS mailing"
|
||||
#: ../../sms_marketing/overview.rst:3
|
||||
msgid "Overview"
|
||||
msgstr ""
|
||||
|
||||
#: ../../sms_marketing/SMS_mkt_build_send-and_get_reports_from_a_SMS_mailing.rst:5
|
||||
msgid "Why to use SMS? Using SMS Marketing as part of my communication strategies can empower me to expand my markets, considering that in some countries emails are not very used or used at all. It also helps to boost my conversion rate, as this strategy has a high open-rate percentage among people who use smartphones - people usually don’t keep unread SMSs!"
|
||||
#: ../../sms_marketing/overview/contact_lists_and_blacklist.rst:3
|
||||
msgid "Contact Lists and Blacklist"
|
||||
msgstr ""
|
||||
|
||||
#: ../../sms_marketing/SMS_mkt_build_send-and_get_reports_from_a_SMS_mailing.rst:8
|
||||
msgid "With Odoo’s SMS Marketing app you can plan, organize, schedule and keep track of your mailings with its easy to use interface."
|
||||
#: ../../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/SMS_mkt_build_send-and_get_reports_from_a_SMS_mailing.rst:12
|
||||
msgid "Install the app"
|
||||
msgstr ""
|
||||
|
||||
#: ../../sms_marketing/SMS_mkt_build_send-and_get_reports_from_a_SMS_mailing.rst:14
|
||||
msgid "Go to *Apps*, search for *SMS Marketing* and click on *Install*."
|
||||
msgstr ""
|
||||
|
||||
#: ../../sms_marketing/SMS_mkt_build_send-and_get_reports_from_a_SMS_mailing.rst:17
|
||||
msgid "Build an SMS mailing"
|
||||
msgstr ""
|
||||
|
||||
#: ../../sms_marketing/SMS_mkt_build_send-and_get_reports_from_a_SMS_mailing.rst:19
|
||||
msgid "Go to *SMS Marketing > Create*."
|
||||
msgstr ""
|
||||
|
||||
#: ../../sms_marketing/SMS_mkt_build_send-and_get_reports_from_a_SMS_mailing.rst:24
|
||||
msgid "First, I’ll be able to specify a *subject* name that will help me to remember what the mailing is about. Under *recipients*, I’ll choose to whom I’d like the SMS to be sent. If I choose *Contact*, all my Odoo contacts (vendor, customers, etc.) will receive my SMS. From there, I can refine my recipient list with the *add filter* option. In the example below, I choose to send it to my contacts living in Belgium."
|
||||
msgstr ""
|
||||
|
||||
#: ../../sms_marketing/SMS_mkt_build_send-and_get_reports_from_a_SMS_mailing.rst:31
|
||||
msgid "The *Mailing list* option, on the other hand, allows me to choose mailing lists I’ve created with specific contacts or people who have subscribed to my Newsletters, or both! I’m allowed to select more than one *Mailing list*."
|
||||
msgstr ""
|
||||
|
||||
#: ../../sms_marketing/SMS_mkt_build_send-and_get_reports_from_a_SMS_mailing.rst:36
|
||||
msgid "Under the *SMS Content* tab, links can be included and Odoo will automatically generate *link trackers*. Thank to those, I’ll be able to get data about those links."
|
||||
msgstr ""
|
||||
|
||||
#: ../../sms_marketing/SMS_mkt_build_send-and_get_reports_from_a_SMS_mailing.rst:38
|
||||
msgid "On *Settings* I have the option *include opt-out link* available. If activated, the contact will be able to unsubscribe from the mailing list he’s not interested in anymore."
|
||||
msgstr ""
|
||||
|
||||
#: ../../sms_marketing/SMS_mkt_build_send-and_get_reports_from_a_SMS_mailing.rst:43
|
||||
msgid "in the *Link Tracker* menu under *Configuration*, I can see the history of my sent links, access them and look at statistics."
|
||||
msgstr ""
|
||||
|
||||
#: ../../sms_marketing/SMS_mkt_build_send-and_get_reports_from_a_SMS_mailing.rst:48
|
||||
msgid "Double-check that you have the phone number of your contacts saved!"
|
||||
msgstr ""
|
||||
|
||||
#: ../../sms_marketing/SMS_mkt_build_send-and_get_reports_from_a_SMS_mailing.rst:52
|
||||
msgid "Sending my mailing"
|
||||
msgstr ""
|
||||
|
||||
#: ../../sms_marketing/SMS_mkt_build_send-and_get_reports_from_a_SMS_mailing.rst:56
|
||||
msgid "Once I have my mailing created, I must choose when I would like it to be delivered:"
|
||||
msgstr ""
|
||||
|
||||
#: ../../sms_marketing/SMS_mkt_build_send-and_get_reports_from_a_SMS_mailing.rst:58
|
||||
msgid "**Put in queue**: the mailing will be triggered with the next automatic run. Interesting option if I don’t mind when the triggering will happen."
|
||||
msgstr ""
|
||||
|
||||
#: ../../sms_marketing/SMS_mkt_build_send-and_get_reports_from_a_SMS_mailing.rst:59
|
||||
msgid "**Send now**: sends the message immediately. Advised to use this option if there are not that many recipients."
|
||||
msgstr ""
|
||||
|
||||
#: ../../sms_marketing/SMS_mkt_build_send-and_get_reports_from_a_SMS_mailing.rst:60
|
||||
msgid "**Schedule**: allows me to choose a day and time. Best option for mailings that I would like to send during a specific event, to promote an offer while it is active or to simply plan my content strategy in advance."
|
||||
msgstr ""
|
||||
|
||||
#: ../../sms_marketing/SMS_mkt_build_send-and_get_reports_from_a_SMS_mailing.rst:61
|
||||
msgid "**Test**: allows me 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, I must remember to use a comma between them."
|
||||
msgstr ""
|
||||
|
||||
#: ../../sms_marketing/SMS_mkt_build_send-and_get_reports_from_a_SMS_mailing.rst:65
|
||||
msgid "Visualize reports"
|
||||
msgstr ""
|
||||
|
||||
#: ../../sms_marketing/SMS_mkt_build_send-and_get_reports_from_a_SMS_mailing.rst:66
|
||||
msgid "On the *Reporting* menu, with just a few clicks, I am capable of applying filters, measures and adopt different layouts to do an analysis of the performance of my SMS mailings."
|
||||
msgstr ""
|
||||
|
||||
#: ../../sms_marketing/SMS_mkt_build_send-and_get_reports_from_a_SMS_mailing.rst:71
|
||||
msgid "I can also check the price to send an SMS on your country when clicking on the *information* icon when creating a new SMS."
|
||||
msgstr ""
|
||||
|
||||
#: ../../sms_marketing/SMS_mkt_build_send-and_get_reports_from_a_SMS_mailing.rst:76
|
||||
msgid "**Buy Credits!** In order to take advantage of the app and its features, make sure you’ve purchased credits. For more information on that access: :doc:`../sms_marketing/fqapricing`"
|
||||
msgstr ""
|
||||
|
||||
#: ../../sms_marketing/SMS_mkt_contact_lists_and_blacklist.rst:3
|
||||
msgid "Contact lists and Blacklist"
|
||||
msgstr ""
|
||||
|
||||
#: ../../sms_marketing/SMS_mkt_contact_lists_and_blacklist.rst:6
|
||||
#: ../../sms_marketing/overview/contact_lists_and_blacklist.rst:11
|
||||
msgid "Contact lists"
|
||||
msgstr ""
|
||||
|
||||
#: ../../sms_marketing/SMS_mkt_contact_lists_and_blacklist.rst:7
|
||||
msgid "Creating my own list of contacts, or importing it, is useful when I want to create specific groups of people, such as the subscribers of my newsletter. It is also the best way to get started if I am 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:13
|
||||
msgid "Go to :menuselection:`Contacts lists --> Contacts lists --> Create`."
|
||||
msgstr ""
|
||||
|
||||
#: ../../sms_marketing/SMS_mkt_contact_lists_and_blacklist.rst:9
|
||||
msgid "Go to *Contacts lists > Contacts lists > Create*. I’ll choose a name for my *Mailing list*, and activate the option *Public* if I would like to make the mailing list accessible to my recipients in the unsubscription page to allow them to update their subscription preferences."
|
||||
#: ../../sms_marketing/overview/contact_lists_and_blacklist.rst:16
|
||||
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/SMS_mkt_contact_lists_and_blacklist.rst:12
|
||||
msgid "Once inside the list, I can again *Create* or *Import* contacts for that specific list."
|
||||
msgstr ""
|
||||
|
||||
#: ../../sms_marketing/SMS_mkt_contact_lists_and_blacklist.rst:18
|
||||
#: ../../sms_marketing/overview/contact_lists_and_blacklist.rst:22
|
||||
msgid "History with the Log Notes"
|
||||
msgstr ""
|
||||
|
||||
#: ../../sms_marketing/SMS_mkt_contact_lists_and_blacklist.rst:19
|
||||
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/SMS_mkt_contact_lists_and_blacklist.rst:24
|
||||
msgid "This is important as I and my team can easily keep track and see a history of interactions with my contacts or prospects, granting me the ability to better understand them. Example: my sales representative can easily find out which SMS mailing promotions a customer has received or not."
|
||||
#: ../../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/SMS_mkt_contact_lists_and_blacklist.rst:29
|
||||
#: ../../sms_marketing/overview/contact_lists_and_blacklist.rst:35
|
||||
msgid "Blacklist"
|
||||
msgstr ""
|
||||
|
||||
#: ../../sms_marketing/SMS_mkt_contact_lists_and_blacklist.rst:30
|
||||
msgid "If I’m coming from another software and have a list of clients who have already asked to be blacklisted from my news, I can import those entries in my database. For that, I’ll go to *Configuration > Phone Blacklist > Import*."
|
||||
#: ../../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/SMS_mkt_integrations_and_template.rst:3
|
||||
#: ../../sms_marketing/overview/contact_lists_and_blacklist.rst:39
|
||||
msgid "For that, go to :menuselection:`Configuration --> Phone Blacklist --> Import`."
|
||||
msgstr ""
|
||||
|
||||
#: ../../sms_marketing/overview/integrations_and_template.rst:3
|
||||
msgid "Integrations and Templates"
|
||||
msgstr ""
|
||||
|
||||
#: ../../sms_marketing/SMS_mkt_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. As you know, one of the biggest benefits of using Odoo is the capability of the apps to be integrated. With the SMS Marketing app isn’t different!"
|
||||
#: ../../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/SMS_mkt_integrations_and_template.rst:9
|
||||
msgid "Organize Email Marketing and SMS campaigns"
|
||||
#: ../../sms_marketing/overview/integrations_and_template.rst:9
|
||||
msgid "Campaigns"
|
||||
msgstr ""
|
||||
|
||||
#: ../../sms_marketing/SMS_mkt_integrations_and_template.rst:10
|
||||
msgid "First, make sure to have the necessary feature activated. Go to the *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/SMS_mkt_integrations_and_template.rst:15
|
||||
msgid "Now, I’ll also have the menu *Campaigns* included in my *SMS Marketing* page, allowing me to have an overview of my SMS mailings and my 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/SMS_mkt_integrations_and_template.rst:20
|
||||
msgid "This feature is especially useful if I have aggregated campaigns, as I have a global reporting view. In addition to that, I can create stages in my 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/SMS_mkt_integrations_and_template.rst:26
|
||||
#: ../../sms_marketing/overview/integrations_and_template.rst:31
|
||||
msgid "Sending SMSs through the Contacts app"
|
||||
msgstr ""
|
||||
|
||||
#: ../../sms_marketing/SMS_mkt_integrations_and_template.rst:27
|
||||
msgid "Sending SMSs through the contact’s form is available by default in Odoo. It makes my work easier if I need to send an SMS to a specific contact, for example. For that, I’ll go to the *Contacts* app, select the contact and click on the *SMS* icon next to the phone number."
|
||||
#: ../../sms_marketing/overview/integrations_and_template.rst:34
|
||||
msgid "Sending SMSs through the contact’s 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/SMS_mkt_integrations_and_template.rst:33
|
||||
msgid "If I’d like to send a message in a batch here, I could go to *List View > select all the contacts > Action > Send SMS*."
|
||||
#: ../../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/SMS_mkt_integrations_and_template.rst:39
|
||||
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/SMS_mkt_integrations_and_template.rst:40
|
||||
msgid "To set up *SMS Templates*, I’ll go to the *Settings* app and activate the *developer mode*. Now, back to *Settings* app, I’ll go to *Technical > Phone/SMS section > SMS Templates* and create the content I need."
|
||||
#: ../../sms_marketing/overview/integrations_and_template.rst:48
|
||||
msgid "Set up SMS templates"
|
||||
msgstr ""
|
||||
|
||||
#: ../../sms_marketing/SMS_mkt_integrations_and_template.rst:48
|
||||
#: ../../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/SMS_mkt_integrations_and_template.rst:52
|
||||
msgid "SMS Text Messaging is available throughout Odoo! Here are some of our extra notable integrations:"
|
||||
#: ../../sms_marketing/overview/integrations_and_template.rst:63
|
||||
msgid "SMS Text Messaging is available throughout Odoo:"
|
||||
msgstr ""
|
||||
|
||||
#: ../../sms_marketing/SMS_mkt_integrations_and_template.rst:54
|
||||
#: ../../sms_marketing/overview/integrations_and_template.rst:65
|
||||
msgid "*CRM*: send SMSs to your leads and opportunities."
|
||||
msgstr ""
|
||||
|
||||
#: ../../sms_marketing/SMS_mkt_integrations_and_template.rst:55
|
||||
#: ../../sms_marketing/overview/integrations_and_template.rst:66
|
||||
msgid "*Subscription*: alert customers about their subscription."
|
||||
msgstr ""
|
||||
|
||||
#: ../../sms_marketing/SMS_mkt_integrations_and_template.rst:56
|
||||
#: ../../sms_marketing/overview/integrations_and_template.rst:67
|
||||
msgid "*Accounting*: send payment reminders."
|
||||
msgstr ""
|
||||
|
||||
#: ../../sms_marketing/SMS_mkt_integrations_and_template.rst:57
|
||||
#: ../../sms_marketing/overview/integrations_and_template.rst:68
|
||||
msgid "*Marketing Automation*: automate your SMS marketing campaigns."
|
||||
msgstr ""
|
||||
|
||||
#: ../../sms_marketing/SMS_mkt_integrations_and_template.rst:58
|
||||
#: ../../sms_marketing/overview/integrations_and_template.rst:69
|
||||
msgid "*Inventory*: send an automatic confirmation when a delivery order is done."
|
||||
msgstr ""
|
||||
|
||||
#: ../../sms_marketing/SMS_mkt_integrations_and_template.rst:59
|
||||
#: ../../sms_marketing/overview/integrations_and_template.rst:70
|
||||
msgid "*Sign*: receive a validation code to verify your identity before signing a document online."
|
||||
msgstr ""
|
||||
|
||||
#: ../../sms_marketing/SMS_mkt_integrations_and_template.rst:60
|
||||
#: ../../sms_marketing/overview/integrations_and_template.rst:71
|
||||
msgid "*SEPA debit payment provider*: send a verification code to your customers."
|
||||
msgstr ""
|
||||
|
||||
#: ../../sms_marketing/SMS_mkt_integrations_and_template.rst:61
|
||||
#: ../../sms_marketing/overview/integrations_and_template.rst:72
|
||||
msgid "*Studio*: send an SMS according to your needs by using automated actions."
|
||||
msgstr ""
|
||||
|
||||
#: ../../sms_marketing/SMS_mkt_integrations_and_template.rst:63
|
||||
msgid "For more information about SMS integrations in Odoo and a list of frequently asked questions, go to `Pricing and FQA <fqapricing.html>`__."
|
||||
#: ../../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/fqapricing.rst:3
|
||||
#: ../../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: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 "Get started"
|
||||
msgstr ""
|
||||
|
||||
#: ../../sms_marketing/overview/sms_mailing_reports.rst:13
|
||||
msgid "Go to :menuselection:`SMS Marketing --> Create`."
|
||||
msgstr ""
|
||||
|
||||
#: ../../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: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: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 "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: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: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:50
|
||||
msgid "Double-check that you have the phone number of your contacts saved."
|
||||
msgstr ""
|
||||
|
||||
#: ../../sms_marketing/overview/sms_mailing_reports.rst:53
|
||||
msgid "Send a mailing"
|
||||
msgstr ""
|
||||
|
||||
#: ../../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: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: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: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: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:70
|
||||
msgid "Visualize reports"
|
||||
msgstr ""
|
||||
|
||||
#: ../../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: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: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
|
||||
msgid "Pricing and FAQ"
|
||||
msgstr ""
|
||||
|
||||
#: ../../sms_marketing/pricing/pricing_and_faq.rst:3
|
||||
msgid "SMS Pricing and FAQ"
|
||||
msgstr ""
|
||||
|
||||
#: ../../sms_marketing/fqapricing.rst:6
|
||||
msgid "Pricing"
|
||||
#: ../../sms_marketing/pricing/pricing_and_faq.rst:6
|
||||
msgid "What do I need to send SMSs?"
|
||||
msgstr ""
|
||||
|
||||
#: ../../sms_marketing/fqapricing.rst:7
|
||||
msgid "SMS Text Messaging is an In-App Purchase (IAP) service which requires prepaid credits to work. The price of an SMS depends on the destination and the length of the message. With 1 credit, I can send up to 92 SMSs."
|
||||
#: ../../sms_marketing/pricing/pricing_and_faq.rst:7
|
||||
msgid "SMS Text Messaging is an In-App Purchase (IAP) service that *requires prepaid credits* to work."
|
||||
msgstr ""
|
||||
|
||||
#: ../../sms_marketing/fqapricing.rst:9
|
||||
msgid "**For more information, please consult our FAQ page**: `Odoo SMS - FAQ <https://iap-services.odoo.com/iap/sms/pricing#sms_faq_01>`_"
|
||||
#: ../../sms_marketing/pricing/pricing_and_faq.rst:11
|
||||
msgid "How many types of SMSs are there?"
|
||||
msgstr ""
|
||||
|
||||
#: ../../sms_marketing/fqapricing.rst:11
|
||||
msgid "To buy credits I will go to *Settings > Buy Credits* (under *Send SMS*); or go to *Settings > View my Services* (under *Odoo IAP*)."
|
||||
#: ../../sms_marketing/pricing/pricing_and_faq.rst:12
|
||||
msgid "There are 2 types: GSM7 and UNICODE."
|
||||
msgstr ""
|
||||
|
||||
#: ../../sms_marketing/fqapricing.rst:18
|
||||
#: ../../sms_marketing/pricing/pricing_and_faq.rst:14
|
||||
msgid "**GSM7** is the standard format, with a limit of 160 characters per message, that includes the following characters:"
|
||||
msgstr ""
|
||||
|
||||
#: ../../sms_marketing/pricing/pricing_and_faq.rst:23
|
||||
msgid "**UNICODE** is the format applied if a special character, that *is not* in the GSM7 list, is used. Limit per SMS: 70 characters."
|
||||
msgstr ""
|
||||
|
||||
#: ../../sms_marketing/pricing/pricing_and_faq.rst:27
|
||||
msgid "For GSM7 SMS the size limit is 160 characters, and for Unicode is 70. *Above these limits, the content is divided into a multi-part message* and the limit of characters is lowered to 153 for GSM7 and to 67 for Unicode. The system will inform you in real-time about the number of SMS your message represents."
|
||||
msgstr ""
|
||||
|
||||
#: ../../sms_marketing/pricing/pricing_and_faq.rst:34
|
||||
msgid "How much does it cost to send an SMS?"
|
||||
msgstr ""
|
||||
|
||||
#: ../../sms_marketing/pricing/pricing_and_faq.rst:35
|
||||
msgid "The price of an SMS depends on the destination and the length (number of characters) of the message."
|
||||
msgstr ""
|
||||
|
||||
#: ../../sms_marketing/pricing/pricing_and_faq.rst:37
|
||||
msgid "To see the **price per country, please consult**: `Odoo SMS - FAQ <https://iap-services.odoo.com/iap/sms/pricing#sms_faq_01>`_."
|
||||
msgstr ""
|
||||
|
||||
#: ../../sms_marketing/pricing/pricing_and_faq.rst:39
|
||||
msgid "The number of SMSs a message represents will be always available to you in your database."
|
||||
msgstr ""
|
||||
|
||||
#: ../../sms_marketing/pricing/pricing_and_faq.rst:49
|
||||
msgid "How do I buy credits?"
|
||||
msgstr ""
|
||||
|
||||
#: ../../sms_marketing/pricing/pricing_and_faq.rst:50
|
||||
msgid "Go to :menuselection:`Settings --> Buy Credits`."
|
||||
msgstr ""
|
||||
|
||||
#: ../../sms_marketing/pricing/pricing_and_faq.rst:57
|
||||
msgid "Or go to :menuselection:`Settings --> View my Services`."
|
||||
msgstr ""
|
||||
|
||||
#: ../../sms_marketing/pricing/pricing_and_faq.rst:65
|
||||
msgid "If you are on Odoo Online (SAAS) and have the Enterprise version, you benefit from free trial credits to test the feature."
|
||||
msgstr ""
|
||||
|
||||
#: ../../sms_marketing/fqapricing.rst:21
|
||||
msgid "FAQ"
|
||||
#: ../../sms_marketing/pricing/pricing_and_faq.rst:70
|
||||
msgid "More common questions"
|
||||
msgstr ""
|
||||
|
||||
#: ../../sms_marketing/fqapricing.rst:22
|
||||
#: ../../sms_marketing/pricing/pricing_and_faq.rst:72
|
||||
msgid "**Is there an expiration time for my credits?**"
|
||||
msgstr ""
|
||||
|
||||
#: ../../sms_marketing/fqapricing.rst:24
|
||||
msgid "No, your credits won’t expire."
|
||||
#: ../../sms_marketing/pricing/pricing_and_faq.rst:74
|
||||
msgid "No, credits do not expire."
|
||||
msgstr ""
|
||||
|
||||
#: ../../sms_marketing/fqapricing.rst:26
|
||||
#: ../../sms_marketing/pricing/pricing_and_faq.rst:77
|
||||
msgid "**Can I send an SMS to a phone number (which is not a mobile phone) because I see the icon in front of the field “phone”?**"
|
||||
msgstr ""
|
||||
|
||||
#: ../../sms_marketing/fqapricing.rst:28
|
||||
#: ../../sms_marketing/pricing/pricing_and_faq.rst:80
|
||||
msgid "Only if that phone number supports SMS (e.g. SIP phones)."
|
||||
msgstr ""
|
||||
|
||||
#: ../../sms_marketing/fqapricing.rst:30
|
||||
#: ../../sms_marketing/pricing/pricing_and_faq.rst:83
|
||||
msgid "**Do I receive an invoice to buy my credits?**"
|
||||
msgstr ""
|
||||
|
||||
#: ../../sms_marketing/fqapricing.rst:32
|
||||
#: ../../sms_marketing/pricing/pricing_and_faq.rst:85
|
||||
msgid "Yes."
|
||||
msgstr ""
|
||||
|
||||
#: ../../sms_marketing/fqapricing.rst:34
|
||||
#: ../../sms_marketing/pricing/pricing_and_faq.rst:88
|
||||
msgid "**Can the recipient answer to me?**"
|
||||
msgstr ""
|
||||
|
||||
#: ../../sms_marketing/fqapricing.rst:36
|
||||
#: ../../sms_marketing/pricing/pricing_and_faq.rst:90
|
||||
msgid "No, it is not possible to reply to the SMS."
|
||||
msgstr ""
|
||||
|
||||
#: ../../sms_marketing/fqapricing.rst:38
|
||||
#: ../../sms_marketing/pricing/pricing_and_faq.rst:93
|
||||
msgid "**What happens if I send multiple SMS but I do not have enough credits to send them all?**"
|
||||
msgstr ""
|
||||
|
||||
#: ../../sms_marketing/fqapricing.rst:40
|
||||
#: ../../sms_marketing/pricing/pricing_and_faq.rst:95
|
||||
msgid "The whole transaction is counted as a single one, so no SMS will be sent until you have enough credits to send them all."
|
||||
msgstr ""
|
||||
|
||||
#: ../../sms_marketing/fqapricing.rst:42
|
||||
#: ../../sms_marketing/pricing/pricing_and_faq.rst:99
|
||||
msgid "**Do I have a history of the sent SMSs?**"
|
||||
msgstr ""
|
||||
|
||||
#: ../../sms_marketing/fqapricing.rst:44
|
||||
msgid "Yes, the SMS is logged as a note under the chatter of the corresponding record, and a complete history of SMS sent is available under Settings> Activate the developer mode > Technical > SMS."
|
||||
#: ../../sms_marketing/pricing/pricing_and_faq.rst:101
|
||||
msgid "Yes, the SMS is logged as a note under the chatter of the corresponding record, and a complete history of the SMSs sent is available on :doc:`Developer mode <../../general/developer_mode/activate>` under :menuselection:`Technical --> SMS`."
|
||||
msgstr ""
|
||||
|
||||
#: ../../sms_marketing/fqapricing.rst:46
|
||||
#: ../../sms_marketing/pricing/pricing_and_faq.rst:107
|
||||
msgid "**Can I send as many SMSs I want at once?**"
|
||||
msgstr ""
|
||||
|
||||
#: ../../sms_marketing/fqapricing.rst:48
|
||||
#: ../../sms_marketing/pricing/pricing_and_faq.rst:109
|
||||
msgid "Yes, if you have enough credits."
|
||||
msgstr ""
|
||||
|
||||
#: ../../sms_marketing/fqapricing.rst:50
|
||||
#: ../../sms_marketing/pricing/pricing_and_faq.rst:112
|
||||
msgid "**If I have a number that does not exist in the list of recipients, will I lose credits?**"
|
||||
msgstr ""
|
||||
|
||||
#: ../../sms_marketing/fqapricing.rst:52
|
||||
#: ../../sms_marketing/pricing/pricing_and_faq.rst:114
|
||||
msgid "Not if the phone number is in the wrong format (e.g. too many digits). Otherwise, if the SMS is sent to the wrong person or to a fake number, the credit will be lost."
|
||||
msgstr ""
|
||||
|
||||
#: ../../sms_marketing/fqapricing.rst:54
|
||||
#: ../../sms_marketing/pricing/pricing_and_faq.rst:118
|
||||
msgid "**What happens if I send my SMS to a paying number (e.g.: a contest to win a ticket for a festival)?**"
|
||||
msgstr ""
|
||||
|
||||
#: ../../sms_marketing/fqapricing.rst:56
|
||||
#: ../../sms_marketing/pricing/pricing_and_faq.rst:120
|
||||
msgid "The SMS will not be delivered to that kind of number, so you won’t be charged."
|
||||
msgstr ""
|
||||
|
||||
#: ../../sms_marketing/fqapricing.rst:58
|
||||
#: ../../sms_marketing/pricing/pricing_and_faq.rst:123
|
||||
msgid "**Can I identify the numbers that do not exist when I send several SMSs?**"
|
||||
msgstr ""
|
||||
|
||||
#: ../../sms_marketing/fqapricing.rst:60
|
||||
#: ../../sms_marketing/pricing/pricing_and_faq.rst:125
|
||||
msgid "Only the ones that have an invalid format."
|
||||
msgstr ""
|
||||
|
||||
#: ../../sms_marketing/fqapricing.rst:62
|
||||
#: ../../sms_marketing/pricing/pricing_and_faq.rst:128
|
||||
msgid "**How does the GDPR regulation affect this service?**"
|
||||
msgstr ""
|
||||
|
||||
#: ../../sms_marketing/fqapricing.rst:64
|
||||
msgid "Please find our Privacy Policy here: `Odoo IPA Purchase Privacy Policy <https://iap.odoo.com/privacy#sms>`__"
|
||||
msgstr ""
|
||||
|
||||
#: ../../sms_marketing/fqapricing.rst:66
|
||||
msgid "**How many types of SMS exist and how many characters make 1 SMS?**"
|
||||
msgstr ""
|
||||
|
||||
#: ../../sms_marketing/fqapricing.rst:68
|
||||
msgid "There are 2 types of SMS message:"
|
||||
msgstr ""
|
||||
|
||||
#: ../../sms_marketing/fqapricing.rst:70
|
||||
msgid "*Standard* (GSM-7): contains only characters from the GSM-7 set, which can be seen in the following picture."
|
||||
msgstr ""
|
||||
|
||||
#: ../../sms_marketing/fqapricing.rst:75
|
||||
msgid "*Unicode*: contains at least one character that is not in the previous table. For Standard SMS the size limit is 160 characters, and for Unicode is 70. Above these limits, the content is divided into a multi-part message. The system will inform you in real-time about the number of SMS your message represents."
|
||||
#: ../../sms_marketing/pricing/pricing_and_faq.rst:130
|
||||
msgid "Please find our `Privacy Policy here <https://iap.odoo.com/privacy#sms>`__."
|
||||
msgstr ""
|
||||
|
||||
|
||||
@ -8,7 +8,7 @@ msgid ""
|
||||
msgstr ""
|
||||
"Project-Id-Version: Odoo 13.0\n"
|
||||
"Report-Msgid-Bugs-To: \n"
|
||||
"POT-Creation-Date: 2019-11-20 10:20+0100\n"
|
||||
"POT-Creation-Date: 2020-09-22 16:26+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"
|
||||
@ -17,99 +17,257 @@ msgstr ""
|
||||
"Content-Transfer-Encoding: 8bit\n"
|
||||
|
||||
#: ../../social_marketing.rst:5
|
||||
#: ../../social_marketing/social_marketing/social_marketing.rst:2
|
||||
msgid "Social Marketing"
|
||||
msgstr ""
|
||||
|
||||
#: ../../social_marketing/social_marketing.rst:3
|
||||
msgid "Advanced Topics"
|
||||
#: ../../social_marketing/overview.rst:3
|
||||
msgid "Overview"
|
||||
msgstr ""
|
||||
|
||||
#: ../../social_marketing/social_marketing/social_marketing.rst:4
|
||||
msgid "One of the biggest challenges of a company is to engage efficiently with their community. Odoo Social helps you to meet your audience with the help of several supports: social media, push notifications, or live chat request."
|
||||
#: ../../social_marketing/overview/campaigns.rst:3
|
||||
msgid "Connecting to my Marketplace with Campaigns"
|
||||
msgstr ""
|
||||
|
||||
#: ../../social_marketing/social_marketing/social_marketing.rst:10
|
||||
msgid "Add your social media and create your feed"
|
||||
#: ../../social_marketing/overview/campaigns.rst:5
|
||||
msgid "Whether your goal is to sell a new product, explain the value of your services or advertise your event, a campaign helps you to connect with your marketplace. They normally involve multiple channels, so it is fundamental to have a solution with which you can plan, execute, track, and analyze your content."
|
||||
msgstr ""
|
||||
|
||||
#: ../../social_marketing/social_marketing/social_marketing.rst:12
|
||||
msgid "You first need to add your social media accounts. To do that, add a Stream and choose your social media account. You’ll need to grant permissions to Odoo Social Marketing application."
|
||||
#: ../../social_marketing/overview/campaigns.rst:10
|
||||
msgid "Go to :menuselection:`Social Marketing --> Campaigns --> Create`."
|
||||
msgstr ""
|
||||
|
||||
#: ../../social_marketing/social_marketing/social_marketing.rst:19
|
||||
msgid "Once it’s done, you’ll be redirected to your Feed and a column will be automatically added with the publications of your freshly added account. You can then add new streams to your Feed and customize your Kanban view as you like."
|
||||
#: ../../social_marketing/overview/campaigns.rst:16
|
||||
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/social_marketing/social_marketing.rst:28
|
||||
msgid "Adding social media accounts to your Feed will also add some KPIs on it:"
|
||||
#: ../../social_marketing/overview/campaigns.rst:19
|
||||
msgid "*Revenue*: number of users who, from a link in your content, finished a transaction (paid)."
|
||||
msgstr ""
|
||||
|
||||
#: ../../social_marketing/social_marketing/social_marketing.rst:30
|
||||
msgid "Audience: Number of followers of your channel"
|
||||
#: ../../social_marketing/overview/campaigns.rst:20
|
||||
msgid "*Quotations*: number of users who, from a link in your content, have started but not finished a transaction (did not pay)."
|
||||
msgstr ""
|
||||
|
||||
#: ../../social_marketing/social_marketing/social_marketing.rst:32
|
||||
msgid "Engagement: Number of times people have engaged with your posts"
|
||||
#: ../../social_marketing/overview/campaigns.rst:22
|
||||
msgid "*Leads*: users who have filled out your contact form, from a link in your content."
|
||||
msgstr ""
|
||||
|
||||
#: ../../social_marketing/social_marketing/social_marketing.rst:35
|
||||
msgid "Stories: Number of times people who have engaged with your channel"
|
||||
#: ../../social_marketing/overview/campaigns.rst:25
|
||||
msgid "To be able to *Send New Mailing*, make sure the feature is enabled in the *Email Marketing* application, under :menuselection:`Email Marketing --> Configuration --> Settings`. To be able to *Send SMS*, the *SMS Marketing* application must be installed on your database."
|
||||
msgstr ""
|
||||
|
||||
#: ../../social_marketing/social_marketing/social_marketing.rst:35
|
||||
msgid "have created stories on their friend’s or follower’s feed (Shares, Retweet,..)"
|
||||
#: ../../social_marketing/overview/campaigns.rst:30
|
||||
msgid "*Social Marketing* works integrated with other applications such as *Sales*, *Invoicing*, *CRM* and *Website*."
|
||||
msgstr ""
|
||||
|
||||
#: ../../social_marketing/social_marketing/social_marketing.rst:37
|
||||
msgid "You can access more information by clicking on the “Insights” link: this will lead you to statistics of the selected social medium."
|
||||
#: ../../social_marketing/overview/campaigns.rst:34
|
||||
#: ../../social_marketing/overview/manage_social.rst:77
|
||||
msgid ":doc:`./push_notifications`"
|
||||
msgstr ""
|
||||
|
||||
#: ../../social_marketing/social_marketing/social_marketing.rst:41
|
||||
#: ../../social_marketing/overview/campaigns.rst:35
|
||||
#: ../../social_marketing/overview/push_notifications.rst:66
|
||||
msgid ":doc:`./manage_social`"
|
||||
msgstr ""
|
||||
|
||||
#: ../../social_marketing/overview/livechat.rst:3
|
||||
msgid "Interact with Customers and Visitors with Live Chat"
|
||||
msgstr ""
|
||||
|
||||
#: ../../social_marketing/overview/livechat.rst:5
|
||||
msgid "One of the ways you can build stronger relationships with your customers is by making yourself available through live chat. Live chats can have a big impact not just on your customer service, but also on sales performance, as it gives users a chance of having real-time, fast, and effective interaction."
|
||||
msgstr ""
|
||||
|
||||
#: ../../social_marketing/overview/livechat.rst:11
|
||||
msgid "Configuration"
|
||||
msgstr ""
|
||||
|
||||
#: ../../social_marketing/overview/livechat.rst:13
|
||||
msgid "Go to :menuselection:`Website --> Configuration --> Settings --> Live Chat` select the appropriate channel, and set it up."
|
||||
msgstr ""
|
||||
|
||||
#: ../../social_marketing/overview/livechat.rst:20
|
||||
msgid "Under *Channel Rules*, choose when the chat pop-up appears, and an action for a given URL and/or country. Note that to take the country into account, GeoIP must be installed on your server."
|
||||
msgstr ""
|
||||
|
||||
#: ../../social_marketing/overview/livechat.rst:24
|
||||
msgid "The *Live Chat* application must be installed on your database."
|
||||
msgstr ""
|
||||
|
||||
#: ../../social_marketing/overview/livechat.rst:27
|
||||
msgid "Monitor your visitors"
|
||||
msgstr ""
|
||||
|
||||
#: ../../social_marketing/overview/livechat.rst:29
|
||||
msgid "Under the *Visitors* menu, see the visitors that landed on one of your :ref:`social_marketing/website_tracked_pages` online or offline."
|
||||
msgstr ""
|
||||
|
||||
#: ../../social_marketing/overview/livechat.rst:34
|
||||
msgid "You can send emails (if an email address has been saved), send SMSs (if a phone number has been saved), send a push notification (if the user has subscribed to it), and even send a live chat request that will be received by the user once they move to a tracked page."
|
||||
msgstr ""
|
||||
|
||||
#: ../../social_marketing/overview/livechat.rst:36
|
||||
msgid "Open a record to see details including the visited pages, and the first and last date and time the user was connected."
|
||||
msgstr ""
|
||||
|
||||
#: ../../social_marketing/overview/livechat.rst:43
|
||||
msgid "Your online visitors will be authenticated if they are linked to a lead or an existing partner."
|
||||
msgstr ""
|
||||
|
||||
#: ../../social_marketing/overview/livechat.rst:44
|
||||
msgid "If you do not use the *Website* app, you can add a live chat widget to your own website."
|
||||
msgstr ""
|
||||
|
||||
#: ../../social_marketing/overview/livechat.rst:49
|
||||
msgid "Website’s tracked pages"
|
||||
msgstr ""
|
||||
|
||||
#: ../../social_marketing/overview/livechat.rst:51
|
||||
msgid "To define which pages are tracked, on the *Website* application, go to :menuselection:`Website --> Configuration --> Pages` and enable the option *Track*, on the respective pages."
|
||||
msgstr ""
|
||||
|
||||
#: ../../social_marketing/overview/livechat.rst:60
|
||||
msgid ":doc:`../../livechat/overview/get_started`"
|
||||
msgstr ""
|
||||
|
||||
#: ../../social_marketing/overview/manage_social.rst:3
|
||||
msgid "Manage Social Media Pages and Create Content"
|
||||
msgstr ""
|
||||
|
||||
#: ../../social_marketing/overview/manage_social.rst:5
|
||||
msgid "Once you are present on social media platforms, it is important to keep them up-to-date. However, that might feel like a full-time job. Having a solution that allows you to create, schedule, keep track, engage with your audience and measure results saves you time and helps you to successfully execute your online strategy, from posts to results."
|
||||
msgstr ""
|
||||
|
||||
#: ../../social_marketing/overview/manage_social.rst:12
|
||||
msgid "Add accounts and create your feed"
|
||||
msgstr ""
|
||||
|
||||
#: ../../social_marketing/overview/manage_social.rst:14
|
||||
msgid "Click on *Add Stream* and grant the required permissions to add your accounts."
|
||||
msgstr ""
|
||||
|
||||
#: ../../social_marketing/overview/manage_social.rst:21
|
||||
msgid "You can link a Facebook page for which you are the admin."
|
||||
msgstr ""
|
||||
|
||||
#: ../../social_marketing/overview/manage_social.rst:23
|
||||
msgid "You are then redirected to your *Feed* and a column with the publications is automatically added."
|
||||
msgstr ""
|
||||
|
||||
#: ../../social_marketing/overview/manage_social.rst:25
|
||||
msgid "You can then add new accounts and/or streams, such as Facebook mentions, and customize your Kanban view."
|
||||
msgstr ""
|
||||
|
||||
#: ../../social_marketing/overview/manage_social.rst:31
|
||||
msgid "Adding social media accounts to your feed will also link KPIs. To get redirected to the statistics page of the social account, click on *Insights*."
|
||||
msgstr ""
|
||||
|
||||
#: ../../social_marketing/overview/manage_social.rst:39
|
||||
msgid "Link a LinkedIn account"
|
||||
msgstr ""
|
||||
|
||||
#: ../../social_marketing/overview/manage_social.rst:41
|
||||
msgid "Go to :menuselection:`Social Marketing --> Configuration --> Social Media`."
|
||||
msgstr ""
|
||||
|
||||
#: ../../social_marketing/overview/manage_social.rst:48
|
||||
msgid "LinkedIn is in Beta Version, therefore, the feed is not available. Only the creation of content."
|
||||
msgstr ""
|
||||
|
||||
#: ../../social_marketing/overview/manage_social.rst:51
|
||||
msgid "Publish content"
|
||||
msgstr ""
|
||||
|
||||
#: ../../social_marketing/social_marketing/social_marketing.rst:43
|
||||
msgid "To publish content on your social media accounts or send a push notification to your subscribed users, either go to your Feed and click on New Post, or use the “Posts” menu and create it from there. Select all the accounts where you want to post your content, write your post and get an instant preview of how it will look when published."
|
||||
#: ../../social_marketing/overview/manage_social.rst:53
|
||||
msgid "Click on :menuselection:`Social Marketing --> Feed --> New Post`, or go to :menuselection:`Social Marketing --> Posts → Create`."
|
||||
msgstr ""
|
||||
|
||||
#: ../../social_marketing/social_marketing/social_marketing.rst:49
|
||||
msgid "If you select the push notifications, you’ll get some additional fields on the form that will allow you to complete the push notifications configuration and choose your segment between all your subscribed users. You can also send push notifications via the Visitors menu, as explained in the previous paragraph."
|
||||
#: ../../social_marketing/overview/manage_social.rst:60
|
||||
msgid "Choose to upload your post right away or to schedule it."
|
||||
msgstr ""
|
||||
|
||||
#: ../../social_marketing/social_marketing/social_marketing.rst:56
|
||||
msgid "Enable push notifications on your website"
|
||||
#: ../../social_marketing/overview/manage_social.rst:61
|
||||
msgid "Saving your post will apply a draft status to it."
|
||||
msgstr ""
|
||||
|
||||
#: ../../social_marketing/social_marketing/social_marketing.rst:58
|
||||
msgid "The push notifications system uses a Firebase account, configured by default. This feature allows you to send push notifications to your website’s visitors after they subscribed to it. To enable push notifications on your website, go to the Website application Settings, and configure the notifications permission request."
|
||||
#: ../../social_marketing/overview/manage_social.rst:64
|
||||
msgid "Overview and plan your posts with a calendar view"
|
||||
msgstr ""
|
||||
|
||||
#: ../../social_marketing/social_marketing/social_marketing.rst:67
|
||||
msgid "Once it’s done, a popup will appear to your website’s visitors, asking them to allow push notifications. As soon as they subscribe to it, you can start sending them push notifications through the Visitors menu. You can either send it individually or target a bigger segment by selecting multiple visitors in the list view (e.g. all the visitors that visited your Homepage)."
|
||||
#: ../../social_marketing/overview/manage_social.rst:67
|
||||
msgid "Through the calendar view, besides having an overview of your planned day, week or month, also see your drafted, scheduled and published posts."
|
||||
msgstr ""
|
||||
|
||||
#: ../../social_marketing/social_marketing/social_marketing.rst:75
|
||||
msgid "Interact with your online visitors"
|
||||
#: ../../social_marketing/overview/manage_social.rst:68
|
||||
msgid "Drag and drop (scheduled posts) to change their scheduled date."
|
||||
msgstr ""
|
||||
|
||||
#: ../../social_marketing/social_marketing/social_marketing.rst:77
|
||||
msgid "You can monitor your online visits via the Visitors menu. You’ll see every visitors that landed on one of your tracked pages (you can configure your tracked pages in the Website application), online or offline. Your online visitors will be authenticated if they’re linked to a lead or an existing partner. You will be able to contact them with an email, a message sms, a push notification (if they have subscribed to it), or even send them a live chat request that they will receive on their next move on one of your tracked pages (if you installed the Live Chat application)."
|
||||
#: ../../social_marketing/overview/manage_social.rst:70
|
||||
msgid "Double-click on a date to create a post directly from the *Calendar view*, and click on an existing one to edit it."
|
||||
msgstr ""
|
||||
|
||||
#: ../../social_marketing/social_marketing/social_marketing.rst:91
|
||||
msgid "Configure your own Facebook and Twitter developer accounts"
|
||||
#: ../../social_marketing/overview/manage_social.rst:78
|
||||
#: ../../social_marketing/overview/push_notifications.rst:67
|
||||
msgid ":doc:`./campaigns`"
|
||||
msgstr ""
|
||||
|
||||
#: ../../social_marketing/social_marketing/social_marketing.rst:93
|
||||
msgid "By default, the Social application is already configured with a Facebook and Twitter developer accounts but you can use your own if necessary. Activate the developer mode, go to Configuration > Settings and enter your own API keys."
|
||||
#: ../../social_marketing/overview/manage_social.rst:79
|
||||
msgid ":doc:`./livechat`"
|
||||
msgstr ""
|
||||
|
||||
#: ../../social_marketing/social_marketing/social_marketing.rst:102
|
||||
msgid "Configure your own Firebase API"
|
||||
#: ../../social_marketing/overview/push_notifications.rst:3
|
||||
msgid "Use Web Push Notifications"
|
||||
msgstr ""
|
||||
|
||||
#: ../../social_marketing/social_marketing/social_marketing.rst:104
|
||||
msgid "By default, a Firebase project is running on your database so there’s no need to configure it. If you have multiple websites, every website will be linked to a different Firebase project. If you need to configure your own Firebase project, please go to :menuselection:`Website --> Configuration --> Settings` Web Push Notifications section."
|
||||
#: ../../social_marketing/overview/push_notifications.rst:5
|
||||
msgid "Web Push Notifications deliver messages to your user’s device without the need to be on your website, or for them to give personal information. They can be used to inform your users about news, articles and content posted, practical messages like traffic and weather updates, flight information, sales alerts, coupons, and product updates."
|
||||
msgstr ""
|
||||
|
||||
#: ../../social_marketing/overview/push_notifications.rst:11
|
||||
msgid "Ask users for permission"
|
||||
msgstr ""
|
||||
|
||||
#: ../../social_marketing/overview/push_notifications.rst:13
|
||||
msgid "In the *Website* application go to :menuselection:`Website --> Configuration --> Settings` and enable *Web Push Notifications*."
|
||||
msgstr ""
|
||||
|
||||
#: ../../social_marketing/overview/push_notifications.rst:20
|
||||
msgid "Choose your message, icon, and delay time (which is the wait time for the permission request to be shown once the user lands on your page)."
|
||||
msgstr ""
|
||||
|
||||
#: ../../social_marketing/overview/push_notifications.rst:28
|
||||
msgid "Send notifications"
|
||||
msgstr ""
|
||||
|
||||
#: ../../social_marketing/overview/push_notifications.rst:31
|
||||
msgid "Individually"
|
||||
msgstr ""
|
||||
|
||||
#: ../../social_marketing/overview/push_notifications.rst:33
|
||||
msgid "You can send individual messages through the menu *Visitors*."
|
||||
msgstr ""
|
||||
|
||||
#: ../../social_marketing/overview/push_notifications.rst:40
|
||||
msgid "To a group"
|
||||
msgstr ""
|
||||
|
||||
#: ../../social_marketing/overview/push_notifications.rst:42
|
||||
msgid "Target a bigger segment by selecting multiple visitors in the *View List* (e.g.: all visitors that visited your Homepage)."
|
||||
msgstr ""
|
||||
|
||||
#: ../../social_marketing/overview/push_notifications.rst:50
|
||||
msgid "Visitors records are kept under *Visitors* for a week, before getting archived."
|
||||
msgstr ""
|
||||
|
||||
#: ../../social_marketing/overview/push_notifications.rst:53
|
||||
msgid "By rules"
|
||||
msgstr ""
|
||||
|
||||
#: ../../social_marketing/overview/push_notifications.rst:55
|
||||
msgid "Or go to :menuselection:`Social Marketing --> Posts --> Create`. Under *Web Notification options*, apply filters to send your message to the records that match the rules you set."
|
||||
msgstr ""
|
||||
|
||||
#: ../../social_marketing/overview/push_notifications.rst:63
|
||||
msgid "The feature only works with Odoo Website application."
|
||||
msgstr ""
|
||||
|
||||
|
||||
658
locale/sources/studio.pot
Normal file
658
locale/sources/studio.pot
Normal file
@ -0,0 +1,658 @@
|
||||
# SOME DESCRIPTIVE TITLE.
|
||||
# Copyright (C) 2015-TODAY, Odoo S.A.
|
||||
# This file is distributed under the same license as the Odoo package.
|
||||
# FIRST AUTHOR <EMAIL@ADDRESS>, YEAR.
|
||||
#
|
||||
#, fuzzy
|
||||
msgid ""
|
||||
msgstr ""
|
||||
"Project-Id-Version: Odoo 13.0\n"
|
||||
"Report-Msgid-Bugs-To: \n"
|
||||
"POT-Creation-Date: 2020-09-22 16:26+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"
|
||||
"MIME-Version: 1.0\n"
|
||||
"Content-Type: text/plain; charset=UTF-8\n"
|
||||
"Content-Transfer-Encoding: 8bit\n"
|
||||
|
||||
#: ../../studio.rst:5
|
||||
msgid "Studio"
|
||||
msgstr ""
|
||||
|
||||
#: ../../studio/concepts.rst:3
|
||||
msgid "Concepts"
|
||||
msgstr ""
|
||||
|
||||
#: ../../studio/concepts/understanding_automated_actions.rst:3
|
||||
msgid "Understanding Automated Actions"
|
||||
msgstr ""
|
||||
|
||||
#: ../../studio/concepts/understanding_automated_actions.rst:6
|
||||
msgid "Automated actions are used to trigger actions. They are based on conditions and happen on top of Odoo’s default business logic."
|
||||
msgstr ""
|
||||
|
||||
#: ../../studio/concepts/understanding_automated_actions.rst:9
|
||||
msgid "Examples of automated actions include: creating a next activity upon a quote's confirmation; adding a user as a follower of a confirmed invoice if its total is higher than a certain amount; or preventing a lead from changing stage if a field is not filled in."
|
||||
msgstr ""
|
||||
|
||||
#: ../../studio/concepts/understanding_automated_actions.rst:16
|
||||
msgid "Let's understand how to properly define *when* an automated action runs and *how* to create one:"
|
||||
msgstr ""
|
||||
|
||||
#: ../../studio/concepts/understanding_automated_actions.rst:18
|
||||
msgid "The first step is to choose the :doc:`Model <understanding_general>` on which the action is applied."
|
||||
msgstr ""
|
||||
|
||||
#: ../../studio/concepts/understanding_automated_actions.rst:19
|
||||
msgid "The **Trigger** field defines the event that causes the automated action to happen:"
|
||||
msgstr ""
|
||||
|
||||
#: ../../studio/concepts/understanding_automated_actions.rst:21
|
||||
msgid "*On Creation*: when a new record is created. Note that the record is created once saved for the first time."
|
||||
msgstr ""
|
||||
|
||||
#: ../../studio/concepts/understanding_automated_actions.rst:23
|
||||
msgid "*On Update*: when the record is updated. Note that the update happens once the record is saved."
|
||||
msgstr ""
|
||||
|
||||
#: ../../studio/concepts/understanding_automated_actions.rst:24
|
||||
msgid "*On Creation & Update*: on the creation and/or on the update of a record once the form is saved."
|
||||
msgstr ""
|
||||
|
||||
#: ../../studio/concepts/understanding_automated_actions.rst:25
|
||||
msgid "*On Deletion*: on the removal of a record under the condition set."
|
||||
msgstr ""
|
||||
|
||||
#: ../../studio/concepts/understanding_automated_actions.rst:26
|
||||
msgid "*Based on Form Modification*: when the value of the specified *Trigger* field is changed in the interface (user sees the changes before saving the record). Note that this action can only be used with the *Execute Python Code* action type."
|
||||
msgstr ""
|
||||
|
||||
#: ../../studio/concepts/understanding_automated_actions.rst:29
|
||||
msgid "*Based on Timed Condition*: a delay happens after a specific date/time. Set a *Delay after trigger date* if you need a delay to happen before the *Trigger Date*. Example: to send a reminder 15min before a meeting. If the date/time is not set on the form of the model chosen, the date/time considered is the one of the creation/update of the record."
|
||||
msgstr ""
|
||||
|
||||
#: ../../studio/concepts/understanding_automated_actions.rst:34
|
||||
msgid "For every Trigger option, **conditions** can be applied, such as:"
|
||||
msgstr ""
|
||||
|
||||
#: ../../studio/concepts/understanding_automated_actions.rst:36
|
||||
msgid "*Before Update Domain*: if designated, this condition must be satisfied before the record is updated."
|
||||
msgstr ""
|
||||
|
||||
#: ../../studio/concepts/understanding_automated_actions.rst:38
|
||||
msgid "*Apply on*: if designated, this condition must be satisfied before executing the action rule (*Action To Do*), and after the update."
|
||||
msgstr ""
|
||||
|
||||
#: ../../studio/concepts/understanding_automated_actions.rst:41
|
||||
msgid "The **Active** option is to be turned off when the rule should be hidden and not executed."
|
||||
msgstr ""
|
||||
|
||||
#: ../../studio/concepts/understanding_automated_actions.rst:43
|
||||
msgid "Under **Action To Do** choose the type of server action that must be executed once records meet the *Trigger* conditions:"
|
||||
msgstr ""
|
||||
|
||||
#: ../../studio/concepts/understanding_automated_actions.rst:45
|
||||
msgid "*Execute Python Code*: a block of code is executed. A *Help* tab with the variables that can be used is available."
|
||||
msgstr ""
|
||||
|
||||
#: ../../studio/concepts/understanding_automated_actions.rst:47
|
||||
msgid "*Create New Record*: a new record with new values is created."
|
||||
msgstr ""
|
||||
|
||||
#: ../../studio/concepts/understanding_automated_actions.rst:48
|
||||
msgid "*Update a Record*: updates the record that triggered the action."
|
||||
msgstr ""
|
||||
|
||||
#: ../../studio/concepts/understanding_automated_actions.rst:49
|
||||
msgid "*Execute several actions*: defines an action that triggers other server actions."
|
||||
msgstr ""
|
||||
|
||||
#: ../../studio/concepts/understanding_automated_actions.rst:50
|
||||
msgid "*Send Email*: an automatic :doc:`email <../../discuss/advanced/email_template>` is sent."
|
||||
msgstr ""
|
||||
|
||||
#: ../../studio/concepts/understanding_automated_actions.rst:51
|
||||
msgid "*Add Followers*: :doc:`followers <../../project/tasks/collaborate>` are notified of changes in the task."
|
||||
msgstr ""
|
||||
|
||||
#: ../../studio/concepts/understanding_automated_actions.rst:53
|
||||
msgid "*Create Next Activity*: creates an activity such as: *Call*, *Email*, *Reminder*."
|
||||
msgstr ""
|
||||
|
||||
#: ../../studio/concepts/understanding_automated_actions.rst:54
|
||||
msgid "*Send SMS Text Message*: sends an :doc:`SMS <../../sms_marketing/pricing/pricing_and_faq>`."
|
||||
msgstr ""
|
||||
|
||||
#: ../../studio/concepts/understanding_automated_actions.rst:57
|
||||
msgid "Example"
|
||||
msgstr ""
|
||||
|
||||
#: ../../studio/concepts/understanding_automated_actions.rst:59
|
||||
msgid "This is the process of which the update of the *Email* field on the Lead/Opportunity *Model*, with a *Trigger Condition* set to *On Update*, goes through:"
|
||||
msgstr ""
|
||||
|
||||
#: ../../studio/concepts/understanding_automated_actions.rst:66
|
||||
msgid "The user creates the record without an email address set."
|
||||
msgstr ""
|
||||
|
||||
#: ../../studio/concepts/understanding_automated_actions.rst:67
|
||||
msgid "The user updates the record defining an email address."
|
||||
msgstr ""
|
||||
|
||||
#: ../../studio/concepts/understanding_automated_actions.rst:68
|
||||
msgid "Once the change is saved, the automation checks if any of the *Watched Fields* are being updated (for the example: field name *email_from* (Email)."
|
||||
msgstr ""
|
||||
|
||||
#: ../../studio/concepts/understanding_automated_actions.rst:70
|
||||
msgid "If true, it checks if the record matches the *Before Update Domain* (for the example: *email is not set*)."
|
||||
msgstr ""
|
||||
|
||||
#: ../../studio/concepts/understanding_automated_actions.rst:72
|
||||
msgid "If true, it checks (*after the update*) whether the record matches the *Apply on* domain (for the example: *email is set*)."
|
||||
msgstr ""
|
||||
|
||||
#: ../../studio/concepts/understanding_automated_actions.rst:74
|
||||
msgid "If true, the chosen *Action To Do* is performed on the record."
|
||||
msgstr ""
|
||||
|
||||
#: ../../studio/concepts/understanding_automated_actions.rst:77
|
||||
msgid ":doc:`understanding_general`"
|
||||
msgstr ""
|
||||
|
||||
#: ../../studio/concepts/understanding_automated_actions.rst:78
|
||||
msgid ":doc:`../use_cases/automated_actions`"
|
||||
msgstr ""
|
||||
|
||||
#: ../../studio/concepts/understanding_general.rst:3
|
||||
msgid "Understanding General Concepts"
|
||||
msgstr ""
|
||||
|
||||
#: ../../studio/concepts/understanding_general.rst:7
|
||||
msgid "Odoo Studio is a toolbox that allows you to add models or adapt functionalities on top of Odoo’s standard behavior without coding knowledge. You can also create custom views and modify existing ones without having to get into the XML code."
|
||||
msgstr ""
|
||||
|
||||
#: ../../studio/concepts/understanding_general.rst:11
|
||||
msgid "Even for experienced developers, typing out code requires time. By using Odoo Studio, you can quickly get your models up and going and focus on the crucial parts of your application. The result is a user-friendly solution that makes customizations and designing new applications easy with or without programming skills."
|
||||
msgstr ""
|
||||
|
||||
#: ../../studio/concepts/understanding_general.rst:15
|
||||
msgid "Getting started"
|
||||
msgstr ""
|
||||
|
||||
#: ../../studio/concepts/understanding_general.rst:17
|
||||
msgid "One you start using Odoo Studio, you automatically create a new *module* that contains all your modifications. These modifications can be done on existing screens (*views*), by adding new *fields* in existing applications, or by creating an entirely new *model*."
|
||||
msgstr ""
|
||||
|
||||
#: ../../studio/concepts/understanding_general.rst:22
|
||||
msgid "What is a Module?"
|
||||
msgstr ""
|
||||
|
||||
#: ../../studio/concepts/understanding_general.rst:25
|
||||
msgid "An Odoo **Module** can contain a number of elements, such as: business objects (models), object views, data files, web controllers, and static web data. An application is a collection of modules."
|
||||
msgstr ""
|
||||
|
||||
#: ../../studio/concepts/understanding_general.rst:29
|
||||
msgid "In object-oriented programming, models usually represent a concept from the real world. Example: Odoo has models for Sales Orders, Users, Countries, etc. If you were to build an application to manage Real Estate sales, a model that represents the Properties for sale would probably be your first step."
|
||||
msgstr ""
|
||||
|
||||
#: ../../studio/concepts/understanding_general.rst:38
|
||||
msgid "What is a Model (also called Object)?"
|
||||
msgstr ""
|
||||
|
||||
#: ../../studio/concepts/understanding_general.rst:40
|
||||
msgid "A **Model** determines the logical structure of a database and fundamentally determines in which manner data can be stored, organized, and manipulated. In other words, a model is a table of information that can be bridged with other tables."
|
||||
msgstr ""
|
||||
|
||||
#: ../../studio/concepts/understanding_general.rst:45
|
||||
msgid "What are Fields?"
|
||||
msgstr ""
|
||||
|
||||
#: ../../studio/concepts/understanding_general.rst:47
|
||||
msgid "**Fields** compose models. It is where a record (a piece of data) is registered."
|
||||
msgstr ""
|
||||
|
||||
#: ../../studio/concepts/understanding_general.rst:49
|
||||
msgid "Example: on the Real Estate application, fields on the Properties model would include the price, address, a picture, a link to the current owner, etc."
|
||||
msgstr ""
|
||||
|
||||
#: ../../studio/concepts/understanding_general.rst:50
|
||||
msgid "There are 2 main types of fields in Odoo: *basic (or scalar) fields* and *relational fields*."
|
||||
msgstr ""
|
||||
|
||||
#: ../../studio/concepts/understanding_general.rst:53
|
||||
msgid "Basic fields represent simple values, like numbers or text. Relational fields represent relations between models. So, if you have a model for *Customers* and another one for *Properties*, you would use a relational field to link each Property to its Customer."
|
||||
msgstr ""
|
||||
|
||||
#: ../../studio/concepts/understanding_general.rst:56
|
||||
msgid "Relational Fields in detail"
|
||||
msgstr ""
|
||||
|
||||
#: ../../studio/concepts/understanding_general.rst:59
|
||||
msgid "**Relational Fields** provide the option to link the data of one model with the data of another model."
|
||||
msgstr ""
|
||||
|
||||
#: ../../studio/concepts/understanding_general.rst:60
|
||||
msgid "In Odoo, relational field types are: *One2many*, *Many2one*, *Many2many*."
|
||||
msgstr ""
|
||||
|
||||
#: ../../studio/concepts/understanding_general.rst:66
|
||||
msgid "An **One2many** field is a *one-way* direction of selecting *multiple* records from a table."
|
||||
msgstr ""
|
||||
|
||||
#: ../../studio/concepts/understanding_general.rst:68
|
||||
msgid "Example: a Sales Order can contain multiple Sales Order Lines, which also contain multiple fields of information."
|
||||
msgstr ""
|
||||
|
||||
#: ../../studio/concepts/understanding_general.rst:69
|
||||
msgid "A **Many2one** field is a *one-way* direction of selecting *one* record from a table."
|
||||
msgstr ""
|
||||
|
||||
#: ../../studio/concepts/understanding_general.rst:70
|
||||
msgid "Example: you can have many product categories, but each product can only belong to one category."
|
||||
msgstr ""
|
||||
|
||||
#: ../../studio/concepts/understanding_general.rst:71
|
||||
msgid "A **Many2many** field is a *two-way* direction of selecting records from a table."
|
||||
msgstr ""
|
||||
|
||||
#: ../../studio/concepts/understanding_general.rst:72
|
||||
msgid "Example: multiple tags can be added to a lead’s form."
|
||||
msgstr ""
|
||||
|
||||
#: ../../studio/concepts/understanding_general.rst:75
|
||||
msgid "An *One2many* field must have a *Many2one* related to it."
|
||||
msgstr ""
|
||||
|
||||
#: ../../studio/concepts/understanding_general.rst:78
|
||||
msgid "What are Views?"
|
||||
msgstr ""
|
||||
|
||||
#: ../../studio/concepts/understanding_general.rst:80
|
||||
msgid "**Views** define how records are displayed. They are specified in XML which means that they can be edited independently from the models that they represent. There are various types of views in Odoo, and each of them represents a mode of visualization. Some examples are: *form*, *list*, *kanban*."
|
||||
msgstr ""
|
||||
|
||||
#: ../../studio/concepts/understanding_general.rst:85
|
||||
msgid "What is a Menu?"
|
||||
msgstr ""
|
||||
|
||||
#: ../../studio/concepts/understanding_general.rst:87
|
||||
msgid "A **Menu** is a button that executes and action. In Odoo Studio, to create menus (models) and rearrange their hierarchy, click on *Edit Menu*."
|
||||
msgstr ""
|
||||
|
||||
#: ../../studio/concepts/understanding_general.rst:95
|
||||
msgid "`Studio Basics <https://www.odoo.com/fr_FR/slides/studio-31>`_"
|
||||
msgstr ""
|
||||
|
||||
#: ../../studio/how_to.rst:3
|
||||
msgid "How To"
|
||||
msgstr ""
|
||||
|
||||
#: ../../studio/how_to/export_import.rst:3
|
||||
msgid "Export and Import Modules"
|
||||
msgstr ""
|
||||
|
||||
#: ../../studio/how_to/export_import.rst:5
|
||||
msgid "When you do customizations in Odoo Studio, a new module is created in your database, making it easy to use Studio for prototyping."
|
||||
msgstr ""
|
||||
|
||||
#: ../../studio/how_to/export_import.rst:8
|
||||
msgid "To export these customizations, activate Studio on the main dashboard and, under the menu *Customizations*, click on *Export*. The default filename is *customizations.zip*."
|
||||
msgstr ""
|
||||
|
||||
#: ../../studio/how_to/export_import.rst:16
|
||||
msgid "The module created contains the definition of custom models and fields, as well as the UI elements of any customization in an XML format."
|
||||
msgstr ""
|
||||
|
||||
#: ../../studio/how_to/export_import.rst:18
|
||||
msgid "To import and install the customizations in another instance, connect to the destination database, activate Studio and, under *Customizations*, click on *Import*."
|
||||
msgstr ""
|
||||
|
||||
#: ../../studio/how_to/export_import.rst:25
|
||||
msgid "Studio does not know which apps are customized (because the same view can be modified on different apps), therefore, it *does not* add the underlying modules as dependencies of the exported module. In other words, the applications installed on the source database should be installed on the destination database."
|
||||
msgstr ""
|
||||
|
||||
#: ../../studio/how_to/rainbow_man.rst:3
|
||||
msgid "Customizing the Rainbow Man"
|
||||
msgstr ""
|
||||
|
||||
#: ../../studio/how_to/rainbow_man.rst:5
|
||||
msgid "The Rainbow Man in Odoo is an animation shown once the user completes certain tasks and clicks on certain buttons. It is a way to make the software fun to use, and rewarding, for employees."
|
||||
msgstr ""
|
||||
|
||||
#: ../../studio/how_to/rainbow_man.rst:13
|
||||
msgid "On most buttons in Odoo, such as *Send by Email*, *Confirm* or *Cancel*, once they are selected in Studio, under their *Properties*, the *Rainbow Man* effect can be applied."
|
||||
msgstr ""
|
||||
|
||||
#: ../../studio/how_to/rainbow_man.rst:14
|
||||
msgid "By default, the feature is active:"
|
||||
msgstr ""
|
||||
|
||||
#: ../../studio/how_to/rainbow_man.rst:16
|
||||
msgid "when opportunities are marked as won;"
|
||||
msgstr ""
|
||||
|
||||
#: ../../studio/how_to/rainbow_man.rst:17
|
||||
msgid "when users empty their inboxes;"
|
||||
msgstr ""
|
||||
|
||||
#: ../../studio/how_to/rainbow_man.rst:18
|
||||
msgid "when the user finishes a tour;"
|
||||
msgstr ""
|
||||
|
||||
#: ../../studio/how_to/rainbow_man.rst:19
|
||||
msgid "when the user finishes doing reconciliations."
|
||||
msgstr ""
|
||||
|
||||
#: ../../studio/how_to/reports.rst:3
|
||||
msgid "Customizing Reports"
|
||||
msgstr ""
|
||||
|
||||
#: ../../studio/how_to/reports.rst:9
|
||||
msgid "Odoo uses HTML and CSS technologies to create reports. HTML is a markup language that uses tags, also called elements. It is the core of any webpage because it provides its basic structure. CSS interacts with HTML elements to add style to the page, establishing how the HTML is shown to the user. Odoo’s reports also use Bootstrap’s grid layout, which is the containers, rows, and columns to align content, and support Odoo's website themes."
|
||||
msgstr ""
|
||||
|
||||
#: ../../studio/how_to/reports.rst:11
|
||||
msgid "When creating a new report, choose the purpose of it and if you would like the report to include header and footer (company logo, name, address, phone, email address, etc.)."
|
||||
msgstr ""
|
||||
|
||||
#: ../../studio/how_to/reports.rst:17
|
||||
msgid "Under the tab **Add**, you find the fields to be dragged and dropped to the view. *Fields*, *Data tables*, *Subtotal & Total*, and *Address Book* are dynamic elements (meaning that they need a :doc:`one2many or a many2many <../concepts/understanding_general>` related object). *Text*, *Title Block*, *Image*, and *Text in Cell* are static elements."
|
||||
msgstr ""
|
||||
|
||||
#: ../../studio/how_to/reports.rst:26
|
||||
msgid "Once the element is added to the view, select it to see its **Options**. The first section shows the hierarchy of the selected object and its properties, allowing you to individually edit them. Fields with related objects have their directives shown on *Field Expression*."
|
||||
msgstr ""
|
||||
|
||||
#: ../../studio/how_to/reports.rst:34
|
||||
msgid "Under **Visible if**, define the rule(s) to set visibility conditions to fields."
|
||||
msgstr ""
|
||||
|
||||
#: ../../studio/how_to/reports.rst:36
|
||||
msgid "Example: if choosing to display a product image, you could set a visibility rule to only display the ones that are *set* in the product form, avoiding having a plain icon when they are not set."
|
||||
msgstr ""
|
||||
|
||||
#: ../../studio/how_to/reports.rst:40
|
||||
msgid "**Visible for** is used to set which :doc:`groups <../../general/odoo_basics/add_user>` can have access to specific elements in the report. **Limit visibility to groups**, under *Report*, sets the visibility of the report to specifics groups, meaning that users belonging to other groups do not see the same final document."
|
||||
msgstr ""
|
||||
|
||||
#: ../../studio/how_to/reports.rst:46
|
||||
msgid "Under the **Report** tab, name your report, choose the paper format, and if the report should be added to the *Print* menu list on its respective document form."
|
||||
msgstr ""
|
||||
|
||||
#: ../../studio/how_to/reports.rst:53
|
||||
msgid "If activating the :doc:`Developer mode <../../general/developer_mode/activate>`, additional fields such as *Class* under *Options*, and *Reload from attachment* under *Report*, become visible."
|
||||
msgstr ""
|
||||
|
||||
#: ../../studio/how_to/reports.rst:56
|
||||
msgid "*Class*: add custom CSS classes to the selected element (e.g. Bootstrap classes such as *text-danger*)."
|
||||
msgstr ""
|
||||
|
||||
#: ../../studio/how_to/reports.rst:59
|
||||
msgid "*Reload from attachment*: saves the report as an attachment of the document when printed. When the report is reprinted, it re-downloads that attachment instead of re-printing it. This means that if the underlying record (e.g. Invoice) changes when compared to the first impression, the report does not reflect the changes because they were done after the attachment was created. This is typically useful for reports linked to documents that should not change, such as Invoices."
|
||||
msgstr ""
|
||||
|
||||
#: ../../studio/how_to/reports.rst:67
|
||||
msgid "Actions in Odoo Studio can be undone until you *Close* the toolbox. Once you have closed Studio, changes can not be undone anymore."
|
||||
msgstr ""
|
||||
|
||||
#: ../../studio/use_cases.rst:3
|
||||
msgid "Use Cases"
|
||||
msgstr ""
|
||||
|
||||
#: ../../studio/use_cases/automated_actions.rst:3
|
||||
msgid "Advanced Use Cases: Automated Actions"
|
||||
msgstr ""
|
||||
|
||||
#: ../../studio/use_cases/automated_actions.rst:5
|
||||
msgid "**Case scenario 1: when a Belgian lead is created, a 3-stars priority should be automatically applied.**"
|
||||
msgstr ""
|
||||
|
||||
#: ../../studio/use_cases/automated_actions.rst:8
|
||||
msgid "Under *Automations*, click on *Create* and set the following rules:"
|
||||
msgstr ""
|
||||
|
||||
#: ../../studio/use_cases/automated_actions.rst:10
|
||||
msgid "*Model*: Lead/Opportunity"
|
||||
msgstr ""
|
||||
|
||||
#: ../../studio/use_cases/automated_actions.rst:11
|
||||
msgid "*Active*: On"
|
||||
msgstr ""
|
||||
|
||||
#: ../../studio/use_cases/automated_actions.rst:12
|
||||
msgid "*Trigger*: On Creation & Update"
|
||||
msgstr ""
|
||||
|
||||
#: ../../studio/use_cases/automated_actions.rst:13
|
||||
msgid "*Apply on*: Country > Country Name = Belgium"
|
||||
msgstr ""
|
||||
|
||||
#: ../../studio/use_cases/automated_actions.rst:14
|
||||
#: ../../studio/use_cases/filters_status_bar.rst:53
|
||||
msgid "*Action To Do*: Update the Record"
|
||||
msgstr ""
|
||||
|
||||
#: ../../studio/use_cases/automated_actions.rst:15
|
||||
msgid "*Data to Write*: Lead/Opportunity > Value > 3"
|
||||
msgstr ""
|
||||
|
||||
#: ../../studio/use_cases/automated_actions.rst:22
|
||||
msgid "Check :doc:`this doc <filters_status_bar>` in order to have another automated action example."
|
||||
msgstr ""
|
||||
|
||||
#: ../../studio/use_cases/automated_actions.rst:25
|
||||
msgid ":doc:`../concepts/understanding_automated_actions`"
|
||||
msgstr ""
|
||||
|
||||
#: ../../studio/use_cases/automated_actions.rst:26
|
||||
#: ../../studio/use_cases/filters_status_bar.rst:61
|
||||
#: ../../studio/use_cases/models_fields.rst:138
|
||||
#: ../../studio/use_cases/views.rst:28
|
||||
msgid ":doc:`../concepts/understanding_general`"
|
||||
msgstr ""
|
||||
|
||||
#: ../../studio/use_cases/filters_status_bar.rst:3
|
||||
msgid "Advanced Use Cases: Filters and Status Bar"
|
||||
msgstr ""
|
||||
|
||||
#: ../../studio/use_cases/filters_status_bar.rst:5
|
||||
msgid "**Case scenario 1: on Sales, set a filter on Belgian customers and define it as the default one (the user should still be able to unset the filter).**"
|
||||
msgstr ""
|
||||
|
||||
#: ../../studio/use_cases/filters_status_bar.rst:8
|
||||
msgid "On your customer’s page, use *Filters* > *Add Custom Filter* to group customers by country. Now, under *Favorites*, *Save Current Search* enabling *Use by default* and *Save*."
|
||||
msgstr ""
|
||||
|
||||
#: ../../studio/use_cases/filters_status_bar.rst:15
|
||||
msgid "On *Filter Rules* in Studio mode, select the respective filter and enable *Default Filter*."
|
||||
msgstr ""
|
||||
|
||||
#: ../../studio/use_cases/filters_status_bar.rst:21
|
||||
msgid "**Case scenario 2: add a status bar on the product form to manage its life cycle. Set the values: ‘Prototype’, ‘In use’ and ‘Deprecated’. By default, the Kanban view must be grouped by status.**"
|
||||
msgstr ""
|
||||
|
||||
#: ../../studio/use_cases/filters_status_bar.rst:26
|
||||
msgid "On your product form, *Add a pipeline status bar* and name its values. Status bars are *selection* fields that give you the ability to follow a specific flow. They are useful to show you the progress that has been made."
|
||||
msgstr ""
|
||||
|
||||
#: ../../studio/use_cases/filters_status_bar.rst:28
|
||||
msgid "On the *Views* menu, access *Kanban* and, under its *View* options, set the *Default Group by* as *Pipeline status bar*."
|
||||
msgstr ""
|
||||
|
||||
#: ../../studio/use_cases/filters_status_bar.rst:34
|
||||
msgid "Now, open your product form and set the right status for that product. As you move products throughout stages (also through the product’s form), stages are shown in the Kanban view."
|
||||
msgstr ""
|
||||
|
||||
#: ../../studio/use_cases/filters_status_bar.rst:38
|
||||
msgid "To make modifications in the pipeline status bar, for example, remember to go back to *Form View*."
|
||||
msgstr ""
|
||||
|
||||
#: ../../studio/use_cases/filters_status_bar.rst:44
|
||||
msgid "**Case scenario 2.a: when a product goes from ‘In use’ to ‘Deprecate’, set its cost to 0€.**"
|
||||
msgstr ""
|
||||
|
||||
#: ../../studio/use_cases/filters_status_bar.rst:46
|
||||
msgid "Create an :doc:`automated action <../concepts/understanding_automated_actions>` with the selected values:"
|
||||
msgstr ""
|
||||
|
||||
#: ../../studio/use_cases/filters_status_bar.rst:49
|
||||
msgid "*Model*: Product Template"
|
||||
msgstr ""
|
||||
|
||||
#: ../../studio/use_cases/filters_status_bar.rst:50
|
||||
msgid "*Trigger*: On Update"
|
||||
msgstr ""
|
||||
|
||||
#: ../../studio/use_cases/filters_status_bar.rst:51
|
||||
msgid "*First Domain*: Pipeline status bar = In use"
|
||||
msgstr ""
|
||||
|
||||
#: ../../studio/use_cases/filters_status_bar.rst:52
|
||||
msgid "*Second Domain*: Pipeline status bar = Deprecated"
|
||||
msgstr ""
|
||||
|
||||
#: ../../studio/use_cases/filters_status_bar.rst:54
|
||||
msgid "*Data to Write*: Cost (Product Template) > Value > 0"
|
||||
msgstr ""
|
||||
|
||||
#: ../../studio/use_cases/models_fields.rst:3
|
||||
msgid "Advanced Use Cases: Creating Models and Adding Fields"
|
||||
msgstr ""
|
||||
|
||||
#: ../../studio/use_cases/models_fields.rst:5
|
||||
msgid "**Case scenario 1: on the leads’ form, if the chosen country is France, show a field 'Pay by check?'**"
|
||||
msgstr ""
|
||||
|
||||
#: ../../studio/use_cases/models_fields.rst:8
|
||||
msgid "On your leads’ form, add a *Related Field* to *Country > Country Name*."
|
||||
msgstr ""
|
||||
|
||||
#: ../../studio/use_cases/models_fields.rst:10
|
||||
msgid "Now, add a *Checkbox* field and define its invisibility options as *Country* (carefully select the one just created) *> is not = > France.*"
|
||||
msgstr ""
|
||||
|
||||
#: ../../studio/use_cases/models_fields.rst:11
|
||||
msgid "You can now hide the related field created (*Country*) if you wish."
|
||||
msgstr ""
|
||||
|
||||
#: ../../studio/use_cases/models_fields.rst:19
|
||||
msgid "Another approach is to use the country’s ID. To do so, go to :menuselection:`Contacts --> Configuration --> Countries`, select France (for example), and on the URL check its *ID*."
|
||||
msgstr ""
|
||||
|
||||
#: ../../studio/use_cases/models_fields.rst:21
|
||||
msgid "The related field invisibility path should now be *Country* (carefully select the one just created) *> is not = > 75*."
|
||||
msgstr ""
|
||||
|
||||
#: ../../studio/use_cases/models_fields.rst:22
|
||||
msgid "Again, hide the related field with the country’s ID if you prefer."
|
||||
msgstr ""
|
||||
|
||||
#: ../../studio/use_cases/models_fields.rst:28
|
||||
msgid "**Case scenario 2: create a model called 'Properties' and add fields called: company, value, name, address, active, image.**"
|
||||
msgstr ""
|
||||
|
||||
#: ../../studio/use_cases/models_fields.rst:31
|
||||
msgid "From the dashboard, (optionally) start a new module. Then, click on *Edit Menu* and start a *New Menu* (model). Set your menu name and *Confirm*. Now, on its form, drag & drop the necessary fields."
|
||||
msgstr ""
|
||||
|
||||
#: ../../studio/use_cases/models_fields.rst:39
|
||||
msgid "**Case scenario 2.a: now, you would like to have a model called 'Regions' to which each property must be linked. And, on 'Regions', you would like to see the properties for each region.**"
|
||||
msgstr ""
|
||||
|
||||
#: ../../studio/use_cases/models_fields.rst:43
|
||||
msgid "Go to *Edit Menu > New Menu* and create your menu, calling it *Regions*. Add the necessary fields on its form by dragging & dropping them."
|
||||
msgstr ""
|
||||
|
||||
#: ../../studio/use_cases/models_fields.rst:45
|
||||
msgid "Now, in the form view of *Properties*, add a *Many2one* field with a relation to your model *Region*."
|
||||
msgstr ""
|
||||
|
||||
#: ../../studio/use_cases/models_fields.rst:48
|
||||
msgid "The *Existing Fields* are the ones that are on the current model but not yet in the view."
|
||||
msgstr ""
|
||||
|
||||
#: ../../studio/use_cases/models_fields.rst:60
|
||||
msgid "Now, go to the model *Regions*, select the form view, and add a status button selecting *Regions (Properties)* as your relational field."
|
||||
msgstr ""
|
||||
|
||||
#: ../../studio/use_cases/models_fields.rst:62
|
||||
msgid "*Status buttons* are computed fields, meaning that they count the numbers of records on the related model, and allow you to access them."
|
||||
msgstr ""
|
||||
|
||||
#: ../../studio/use_cases/models_fields.rst:69
|
||||
msgid "When searching for relations, click on *Search more* and filter it by *Custom*. This way you avoid creating duplicates."
|
||||
msgstr ""
|
||||
|
||||
#: ../../studio/use_cases/models_fields.rst:76
|
||||
msgid "**Case scenario 2.b: in the model 'Properties', show all the tags as checkboxes instead of tags.**"
|
||||
msgstr ""
|
||||
|
||||
#: ../../studio/use_cases/models_fields.rst:78
|
||||
msgid "Once the field *Tags* is added to the form, select it and, under its *Properties > Widgets*, choose *Checkboxes*."
|
||||
msgstr ""
|
||||
|
||||
#: ../../studio/use_cases/models_fields.rst:85
|
||||
msgid "**Case scenario 3: on the leads’ form, add a selection field with the values:'Tags' & 'List' & 'Checkboxes'. According to the value of the field, show tags as many2many_tags, many2many_radio, or many2many(_list).**"
|
||||
msgstr ""
|
||||
|
||||
#: ../../studio/use_cases/models_fields.rst:89
|
||||
msgid "In your form view, add a *Tags* field and relate it to *Partners Tag*. Under *Properties*, define its *Widget* as *Many2many*. Do the same process another 2 times for *Checkboxes* and *Tags*."
|
||||
msgstr ""
|
||||
|
||||
#: ../../studio/use_cases/models_fields.rst:96
|
||||
msgid "Now, add a *Selection* field and the necessary values."
|
||||
msgstr ""
|
||||
|
||||
#: ../../studio/use_cases/models_fields.rst:99
|
||||
msgid "Continue by selecting your *Tags* fields, one by one, to set their *Invisible* options according to their *Widget*. In the example below, the invisibility rule for the *Partner Tags* is set as: *Select Tag type > is not = > Tags.*"
|
||||
msgstr ""
|
||||
|
||||
#: ../../studio/use_cases/models_fields.rst:105
|
||||
msgid "**Case scenario 4: on a quotation’s form, add a selection field called 'Manager Validation' with the values: ‘Accepted’ and ‘Refused’. Only a sales manager can see it, and the field should be set as mandatory if the untaxed amount is higher than 500€.**"
|
||||
msgstr ""
|
||||
|
||||
#: ../../studio/use_cases/models_fields.rst:109
|
||||
msgid "On your quotation form, add a *Selection* field with the values *Accepted* and *Refused*. Set its *Required* condition as *Untaxed Amount > 500* and the *Limit visibility to groups* as *Sales / Administrator* or managers."
|
||||
msgstr ""
|
||||
|
||||
#: ../../studio/use_cases/models_fields.rst:117
|
||||
msgid "**Case scenario 5: change the tooltip of a field for all views.**"
|
||||
msgstr ""
|
||||
|
||||
#: ../../studio/use_cases/models_fields.rst:119
|
||||
msgid "Activate the :doc:`Developer mode <../../general/developer_mode/activate>` and open Studio."
|
||||
msgstr ""
|
||||
|
||||
#: ../../studio/use_cases/models_fields.rst:122
|
||||
msgid "Select the necessary field and, under *Properties*, click on *More* to write your tooltip message on *Field Help*. The tooltip message is the explanatory message shown when the user hovers the field. The message here written is displayed on all views forms where the field is added."
|
||||
msgstr ""
|
||||
|
||||
#: ../../studio/use_cases/models_fields.rst:129
|
||||
msgid "The *Field Help* message can only be applied to *new* fields. If you would like to change/apply a tooltip for a specific field, use the *Help Tooltip* option under *Properties*."
|
||||
msgstr ""
|
||||
|
||||
#: ../../studio/use_cases/views.rst:3
|
||||
msgid "Advanced Use Cases: Views"
|
||||
msgstr ""
|
||||
|
||||
#: ../../studio/use_cases/views.rst:5
|
||||
msgid "**Case scenario 1: in Sales, show orders in a Kanban View instead of a List View.**"
|
||||
msgstr ""
|
||||
|
||||
#: ../../studio/use_cases/views.rst:7
|
||||
msgid "From the Sales page, access Studio and, under *Views*, set the *Kanban* option as the default one."
|
||||
msgstr ""
|
||||
|
||||
#: ../../studio/use_cases/views.rst:14
|
||||
msgid "**Case scenario 2: allow for the list of leads to be edited inline without having to switch to the form view.**"
|
||||
msgstr ""
|
||||
|
||||
#: ../../studio/use_cases/views.rst:19
|
||||
msgid "On the *List View*, under *View* > *Editable*, choose between *New record on top* or *New record at the bottom*. This way, besides defining the order in which new records are displayed in the view, you are able to edit them."
|
||||
msgstr ""
|
||||
|
||||
#: ../../studio/use_cases/views.rst:21
|
||||
msgid "If the field is left blank, no editing is possible and records are shown based on your column preferences on the lead's page (front-end)."
|
||||
msgstr ""
|
||||
|
||||
567
locale/sources/subscriptions.pot
Normal file
567
locale/sources/subscriptions.pot
Normal file
@ -0,0 +1,567 @@
|
||||
# SOME DESCRIPTIVE TITLE.
|
||||
# Copyright (C) 2015-TODAY, Odoo S.A.
|
||||
# This file is distributed under the same license as the Odoo package.
|
||||
# FIRST AUTHOR <EMAIL@ADDRESS>, YEAR.
|
||||
#
|
||||
#, fuzzy
|
||||
msgid ""
|
||||
msgstr ""
|
||||
"Project-Id-Version: Odoo 13.0\n"
|
||||
"Report-Msgid-Bugs-To: \n"
|
||||
"POT-Creation-Date: 2020-09-22 16:26+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"
|
||||
"MIME-Version: 1.0\n"
|
||||
"Content-Type: text/plain; charset=UTF-8\n"
|
||||
"Content-Transfer-Encoding: 8bit\n"
|
||||
|
||||
#: ../../subscriptions.rst:5
|
||||
msgid "Subscriptions"
|
||||
msgstr ""
|
||||
|
||||
#: ../../subscriptions/configuration.rst:3
|
||||
#: ../../subscriptions/configuration/subscription_products.rst:16
|
||||
#: ../../subscriptions/configuration/subscription_templates.rst:32
|
||||
#: ../../subscriptions/sales_flow/closing.rst:31
|
||||
#: ../../subscriptions/sales_flow/upselling.rst:25
|
||||
msgid "Configuration"
|
||||
msgstr ""
|
||||
|
||||
#: ../../subscriptions/configuration/subscription_products.rst:3
|
||||
msgid "Add subscription products"
|
||||
msgstr ""
|
||||
|
||||
#: ../../subscriptions/configuration/subscription_products.rst:5
|
||||
msgid "To properly sell your subscriptions using our amazing **Odoo Subscriptions** application, you must follow these steps:"
|
||||
msgstr ""
|
||||
|
||||
#: ../../subscriptions/configuration/subscription_products.rst:8
|
||||
msgid "**Create your own subscription templates**"
|
||||
msgstr ""
|
||||
|
||||
#: ../../subscriptions/configuration/subscription_products.rst:9
|
||||
msgid "**Create your own subscription products with the right settings**"
|
||||
msgstr ""
|
||||
|
||||
#: ../../subscriptions/configuration/subscription_products.rst:11
|
||||
msgid "As a result, you will be able to manage your subscriptions like any other product, create your quotations and continue the sales flow to track the number of subscriptions you sell and manage the revenue they generate."
|
||||
msgstr ""
|
||||
|
||||
#: ../../subscriptions/configuration/subscription_products.rst:18
|
||||
msgid "Go to :menuselection:`Subscriptions --> Subscription products` to learn how you can configure your own subscription products. You have the possibility to create a new product or edit an existing one. Once named, be careful to select the option *Can be sold* and deselect *Can be purchased*. For the product type, it is recommended to use *Service* for subscription products as they are non-material products that you provide to your customers. Finally, you can adapt your prices and also add an internal reference."
|
||||
msgstr ""
|
||||
|
||||
#: ../../subscriptions/configuration/subscription_products.rst:30
|
||||
msgid "In the Sales tab, underneath the Subscriptions section, make sure the *Subscription products* option is activated. In fact, if you create a subscription product from the **Odoo Subscriptions** application, this option is selected by default. However, if you create a product from another application, it is not the case."
|
||||
msgstr ""
|
||||
|
||||
#: ../../subscriptions/configuration/subscription_products.rst:39
|
||||
msgid "You can also choose the subscription templates you want to use."
|
||||
msgstr ""
|
||||
|
||||
#: ../../subscriptions/configuration/subscription_products.rst:46
|
||||
msgid "Be sure to check out our documentation on how to create, edit and manage your own :doc:`Subscription templates <../../subscriptions/configuration/subscription_templates>` before creating your own subscription products. Once created, check out our documentation on how to :doc:`Create a quotation using subscription products <../../subscriptions/sales_flow/create_a_quotation>`, to complete the sales flow."
|
||||
msgstr ""
|
||||
|
||||
#: ../../subscriptions/configuration/subscription_products.rst:53
|
||||
#: ../../subscriptions/follow_up/automatic_alerts.rst:83
|
||||
#: ../../subscriptions/reporting/subscription_reports.rst:120
|
||||
#: ../../subscriptions/sales_flow/closing.rst:105
|
||||
#: ../../subscriptions/sales_flow/create_a_quotation.rst:79
|
||||
#: ../../subscriptions/sales_flow/renewals.rst:80
|
||||
#: ../../subscriptions/sales_flow/upselling.rst:83
|
||||
msgid ":doc:`../../subscriptions/configuration/subscription_templates`"
|
||||
msgstr ""
|
||||
|
||||
#: ../../subscriptions/configuration/subscription_products.rst:54
|
||||
#: ../../subscriptions/follow_up/automatic_alerts.rst:85
|
||||
#: ../../subscriptions/reporting/subscription_reports.rst:122
|
||||
#: ../../subscriptions/sales_flow/closing.rst:107
|
||||
#: ../../subscriptions/sales_flow/renewals.rst:82
|
||||
#: ../../subscriptions/sales_flow/upselling.rst:85
|
||||
msgid ":doc:`../../subscriptions/sales_flow/create_a_quotation`"
|
||||
msgstr ""
|
||||
|
||||
#: ../../subscriptions/configuration/subscription_templates.rst:3
|
||||
msgid "Use subscription templates"
|
||||
msgstr ""
|
||||
|
||||
#: ../../subscriptions/configuration/subscription_templates.rst:5
|
||||
msgid "The subscription business model is becoming more popular. Are you wondering why?"
|
||||
msgstr ""
|
||||
|
||||
#: ../../subscriptions/configuration/subscription_templates.rst:7
|
||||
msgid "For **customers**, value lies in **convenience**:"
|
||||
msgstr ""
|
||||
|
||||
#: ../../subscriptions/configuration/subscription_templates.rst:9
|
||||
msgid "Subscriptions simplify the business process. Indeed, subscribers never have to remember to renew their orders every month, which gives them the assurance that they will have everything they need before they actually need it."
|
||||
msgstr ""
|
||||
|
||||
#: ../../subscriptions/configuration/subscription_templates.rst:12
|
||||
msgid "Subscriptions help customers stay on budget."
|
||||
msgstr ""
|
||||
|
||||
#: ../../subscriptions/configuration/subscription_templates.rst:14
|
||||
msgid "For **businesses**, value lies in the **ability to predict recurring revenue**:"
|
||||
msgstr ""
|
||||
|
||||
#: ../../subscriptions/configuration/subscription_templates.rst:16
|
||||
msgid "Subscriptions reduce customer churn rate and significantly increase customer retention."
|
||||
msgstr ""
|
||||
|
||||
#: ../../subscriptions/configuration/subscription_templates.rst:17
|
||||
msgid "Subscriptions provide much higher payment security for your business. They stabilize and maintain recurring revenue streams by guaranteeing monthly revenues and adding value to your business."
|
||||
msgstr ""
|
||||
|
||||
#: ../../subscriptions/configuration/subscription_templates.rst:27
|
||||
msgid "**Odoo Subscriptions** help you save time and money. Subscription templates can help you generate recurring invoices and manage renewals at a fast pace. With Odoo you have the possibility to create, edit, and manage your own subscription templates."
|
||||
msgstr ""
|
||||
|
||||
#: ../../subscriptions/configuration/subscription_templates.rst:34
|
||||
msgid "Go to :menuselection:`Subscriptions --> Configuration --> Subscription templates`. By default, Odoo suggests you two types of subscription (MON - Monthly subscription *vs* YEA - Yearly subscription). You can also create your own ones."
|
||||
msgstr ""
|
||||
|
||||
#: ../../subscriptions/configuration/subscription_templates.rst:43
|
||||
msgid "The **Odoo Subscriptions** application automatically installs **Odoo Sales** and **Odoo Invoicing** as they work integrated."
|
||||
msgstr ""
|
||||
|
||||
#: ../../subscriptions/configuration/subscription_templates.rst:47
|
||||
msgid "Create your first template"
|
||||
msgstr ""
|
||||
|
||||
#: ../../subscriptions/configuration/subscription_templates.rst:49
|
||||
msgid "You can create a new template or edit an existing one. The first thing you need to do is give your template a name. After that, choose an *Invoicing period* and specify whether you would like to invoice your customers per *Days*, *Weeks*, *Months* or *Years*. On *Duration*, determine if the subscription must go on *Forever* (until it’s manually closed), or for a *Fixed amount* of time. Among the payment options, an additional field called *Invoice email* appears when you choose *Send*, *Send & try to charge* or *Send after successful payment*. This field allows you to add an invoice email template to your subscription templates."
|
||||
msgstr ""
|
||||
|
||||
#: ../../subscriptions/configuration/subscription_templates.rst:61
|
||||
msgid "For each template, you can also choose if you want your customers to be able to close their subscriptions or not. If enabled, you can set an *Automatic closing* limit and specify the *Group of subscription* and *Journal* options."
|
||||
msgstr ""
|
||||
|
||||
#: ../../subscriptions/configuration/subscription_templates.rst:66
|
||||
msgid "On each template, you can add your **Terms and Conditions**. Specifying terms and conditions is essential to set out important contractual points between the customers and the sellers (payment, refund policy, cancellation, complaints, etc.)."
|
||||
msgstr ""
|
||||
|
||||
#: ../../subscriptions/configuration/subscription_templates.rst:74
|
||||
msgid "Finally, if you want to know the basic running health status of your subscriptions, you also have access to a specific tab called **Health Check**. There, you can edit and create your own filters to define what is a subscription in good health *vs* bad health. The system automatically summarizes all the records corresponding to these filters and you are able to manage them in one click."
|
||||
msgstr ""
|
||||
|
||||
#: ../../subscriptions/configuration/subscription_templates.rst:85
|
||||
msgid "After creating your own subscription templates, be sure to check out our documentation on how to create, edit and manage your own :doc:`Subscription products <../../subscriptions/configuration/subscription_products>`, to complete the sales flow."
|
||||
msgstr ""
|
||||
|
||||
#: ../../subscriptions/configuration/subscription_templates.rst:91
|
||||
#: ../../subscriptions/follow_up/automatic_alerts.rst:84
|
||||
#: ../../subscriptions/reporting/subscription_reports.rst:121
|
||||
#: ../../subscriptions/sales_flow/closing.rst:106
|
||||
#: ../../subscriptions/sales_flow/create_a_quotation.rst:80
|
||||
#: ../../subscriptions/sales_flow/renewals.rst:81
|
||||
#: ../../subscriptions/sales_flow/upselling.rst:84
|
||||
msgid ":doc:`../../subscriptions/configuration/subscription_products`"
|
||||
msgstr ""
|
||||
|
||||
#: ../../subscriptions/follow_up.rst:3
|
||||
msgid "Follow-up"
|
||||
msgstr ""
|
||||
|
||||
#: ../../subscriptions/follow_up/automatic_alerts.rst:3
|
||||
msgid "Set up automatic alerts"
|
||||
msgstr ""
|
||||
|
||||
#: ../../subscriptions/follow_up/automatic_alerts.rst:5
|
||||
msgid "Now that your subscriptions are up and running, you want to stay up-to-date with your customers. Some automation would be appreciated since you would not want to go through the list of all your subscribers to check how things are going. This is what the *Automatic Alerts* feature is for."
|
||||
msgstr ""
|
||||
|
||||
#: ../../subscriptions/follow_up/automatic_alerts.rst:9
|
||||
msgid "For example, when customers subscribe to your magazine, you would probably want to send them an email to welcome them and express your gratitude. Or, if the satisfaction rate of your customers drops below 50%, you would probably want to schedule a call with them to understand the reasons for their dissatisfaction."
|
||||
msgstr ""
|
||||
|
||||
#: ../../subscriptions/follow_up/automatic_alerts.rst:14
|
||||
msgid "With **Odoo Subscriptions**, you can set automatic emails, create a \"Call\" task for one of your salespeople so that he/she can try to understand your customer's dissatisfaction, and finally, why not automatically send satisfaction surveys so customers can evaluate your services? All of that is now possible."
|
||||
msgstr ""
|
||||
|
||||
#: ../../subscriptions/follow_up/automatic_alerts.rst:20
|
||||
msgid "Create a new automatic alert"
|
||||
msgstr ""
|
||||
|
||||
#: ../../subscriptions/follow_up/automatic_alerts.rst:22
|
||||
msgid "The following example shows how to create a new automatic alert to send satisfaction surveys to your customers, by email, after one month of subscription. To do so, go to :menuselection:`Subscriptions --> Configuration --> Alerts`, and create a new alert."
|
||||
msgstr ""
|
||||
|
||||
#: ../../subscriptions/follow_up/automatic_alerts.rst:30
|
||||
msgid "On the *Apply on* section, first give the alert a name. Then, you can choose to apply this alert on a subscription template, on a specific customer, or even on a specific product. If you want to add more specifications, you can also specify the value of your MRR, the change rate of your MRR over a certain period of time, the value of the satisfaction rate, and even the stage to which you want to apply this alert."
|
||||
msgstr ""
|
||||
|
||||
#: ../../subscriptions/follow_up/automatic_alerts.rst:37
|
||||
msgid "In this example, the alert is applied to a specific product, and the stage goes from *Undefined* to *In Progress*."
|
||||
msgstr ""
|
||||
|
||||
#: ../../subscriptions/follow_up/automatic_alerts.rst:40
|
||||
msgid "For the *Action* section, specify the *Action* and the *Trigger on*. If the *Trigger on* is set to *Modification*, the action is triggered every time there is a change or anything added to the subscription, and all the conditions on the *Apply on* section are met. Now, if the *Trigger on* is set to *Timed condition*, it means that the action is triggered based on the type of *Trigger date*. After that, you can choose your *Action*. You have the choice between *Create next activity*, *Set a tag on the subscription*, *Set a stage on the subscription*, *Mark as To Renew*, *Send an email to the customer* and *Send an SMS Text Message to the customer*."
|
||||
msgstr ""
|
||||
|
||||
#: ../../subscriptions/follow_up/automatic_alerts.rst:50
|
||||
msgid "In the example above, the *Trigger on* is set to *Timed condition*, therefore, a *Trigger date* and *Delay after trigger* need to be specified. And because the *Send an email to the customer* action was adopted, an *Email template* can be chosen."
|
||||
msgstr ""
|
||||
|
||||
#: ../../subscriptions/follow_up/automatic_alerts.rst:54
|
||||
msgid "As a result, this alert will send a rating survey after one month, to the customers who have purchased that specific product. The survey will appear in the chatter of your respective subscription."
|
||||
msgstr ""
|
||||
|
||||
#: ../../subscriptions/follow_up/automatic_alerts.rst:63
|
||||
msgid "Modify an existing automatic alert"
|
||||
msgstr ""
|
||||
|
||||
#: ../../subscriptions/follow_up/automatic_alerts.rst:65
|
||||
msgid "By default, Odoo suggests you an automatic alert called *Take action on less satisfied clients*."
|
||||
msgstr ""
|
||||
|
||||
#: ../../subscriptions/follow_up/automatic_alerts.rst:71
|
||||
msgid "This alert is applied to the *Rating Satisfaction* of your customers, and the action is triggered on *Timed condition*. If their satisfaction rate is lower than 50%, a salesperson contacts the customer. This action is automatically assigned to the salesperson who manages the subscription, and the due date is 5 days after the triggering of this action. This alert ensures that your clients are happy and that you are taking actions if they are not. It helps to keep your customer retention rates very high."
|
||||
msgstr ""
|
||||
|
||||
#: ../../subscriptions/follow_up/automatic_alerts.rst:79
|
||||
msgid "By editing the alert, you can modify the *Apply on*, the *Action* and *Activity* sections, and adapt them to your own needs."
|
||||
msgstr ""
|
||||
|
||||
#: ../../subscriptions/follow_up/automatic_alerts.rst:86
|
||||
msgid ":doc:`../../subscriptions/reporting/subscription_reports`"
|
||||
msgstr ""
|
||||
|
||||
#: ../../subscriptions/reporting.rst:3
|
||||
msgid "Reporting"
|
||||
msgstr ""
|
||||
|
||||
#: ../../subscriptions/reporting/subscription_reports.rst:3
|
||||
msgid "Generate subscription reports"
|
||||
msgstr ""
|
||||
|
||||
#: ../../subscriptions/reporting/subscription_reports.rst:5
|
||||
msgid "As we know, understanding how our business is going, and where it is going, is key to success. And particularly so when we offer subscription services or products."
|
||||
msgstr ""
|
||||
|
||||
#: ../../subscriptions/reporting/subscription_reports.rst:8
|
||||
msgid "Before getting to the heart of the matter, it is very important to recall certain essential concepts to the proper understanding of the following reports:"
|
||||
msgstr ""
|
||||
|
||||
#: ../../subscriptions/reporting/subscription_reports.rst:11
|
||||
msgid "**Monthly Recurring Revenue (MRR)**: MRR is arguably the most important metric for subscription businesses. It shows the monthly revenue earned with subscription-based products or services. It is a consistent number used to track all recurring revenue over time, in monthly increments."
|
||||
msgstr ""
|
||||
|
||||
#: ../../subscriptions/reporting/subscription_reports.rst:15
|
||||
msgid "**Annual Run-Rate (ARR)**: ARR is the yearly version of MRR, which is based on the current MRR, to estimate the coming year's performance. However, this estimation does not take variations and growth into account."
|
||||
msgstr ""
|
||||
|
||||
#: ../../subscriptions/reporting/subscription_reports.rst:23
|
||||
msgid "**Non-Recurring Revenue (NRR)**: NRR shows the revenue earned for everything else than subscription-based products or services. This includes gains of a rare or unique nature that are unlikely to occur in the ordinary course of businesses."
|
||||
msgstr ""
|
||||
|
||||
#: ../../subscriptions/reporting/subscription_reports.rst:27
|
||||
msgid "**Customer Retention**: Practices to engage existing customers to continue buying products or services from your business. Customer retention can be a challenge, because you must prove you are worthy of your customers' trust."
|
||||
msgstr ""
|
||||
|
||||
#: ../../subscriptions/reporting/subscription_reports.rst:31
|
||||
msgid "**Churn Rate**: Also known as the Rate of Attrition or Customer Churn, the churn rate can be defined, in this case, as the percentage of subscribers who discontinued their subscriptions within a given time period. We can distinguish two types of Churn:"
|
||||
msgstr ""
|
||||
|
||||
#: ../../subscriptions/reporting/subscription_reports.rst:35
|
||||
msgid "**Logo Churn**: It corresponds to the subscription cancellation rate."
|
||||
msgstr ""
|
||||
|
||||
#: ../../subscriptions/reporting/subscription_reports.rst:37
|
||||
msgid "**Revenue Churn**: It corresponds to the monthly recurring revenue loss rate."
|
||||
msgstr ""
|
||||
|
||||
#: ../../subscriptions/reporting/subscription_reports.rst:39
|
||||
msgid "Let's imagine a 2$ increase in a subscription service."
|
||||
msgstr ""
|
||||
|
||||
#: ../../subscriptions/reporting/subscription_reports.rst:42
|
||||
msgid "We lost 3 customers out of the initial 20, which generates a **Logo Churn** of 15%."
|
||||
msgstr ""
|
||||
|
||||
#: ../../subscriptions/reporting/subscription_reports.rst:0
|
||||
msgid "Therefore, the 56$ of MRR difference out of the initial 600$ causes a **Revenue Churn**"
|
||||
msgstr ""
|
||||
|
||||
#: ../../subscriptions/reporting/subscription_reports.rst:0
|
||||
msgid "of 9,33%."
|
||||
msgstr ""
|
||||
|
||||
#: ../../subscriptions/reporting/subscription_reports.rst:50
|
||||
msgid "Reminder: even though they seem to evolve in the same direction most of the time, it might not be the case all the time."
|
||||
msgstr ""
|
||||
|
||||
#: ../../subscriptions/reporting/subscription_reports.rst:53
|
||||
msgid "**Customer Lifetime Value (CLV)**: Indicates how much revenue can be expected for a customer during his/her entire contract. This approach emphasizes the importance of customer retention, shifting our focus from a quarterly or yearly approach to a long-term one."
|
||||
msgstr ""
|
||||
|
||||
#: ../../subscriptions/reporting/subscription_reports.rst:57
|
||||
msgid "Check out the different kinds of reports you can access from the **Odoo Subscriptions** application."
|
||||
msgstr ""
|
||||
|
||||
#: ../../subscriptions/reporting/subscription_reports.rst:61
|
||||
msgid "Subscriptions analysis report"
|
||||
msgstr ""
|
||||
|
||||
#: ../../subscriptions/reporting/subscription_reports.rst:63
|
||||
msgid "Go to :menuselection:`Subscriptions --> Reporting --> Subscriptions`. From there, you can change the *Measures*. By default, Odoo uses the *Monthly Recurring Revenue*. In addition to that, you can choose *Quantity*, *Recurring Price*, *Yearly Recurring Revenue* and *Count*. For this example, *Quantity* is added. This way, you can review both of these measures at the same time. You can even *Group By Start Date* and, more precisely, by *Week*, to get a clear view of your report."
|
||||
msgstr ""
|
||||
|
||||
#: ../../subscriptions/reporting/subscription_reports.rst:74
|
||||
msgid "Retention analysis report"
|
||||
msgstr ""
|
||||
|
||||
#: ../../subscriptions/reporting/subscription_reports.rst:76
|
||||
msgid "Go to :menuselection:`Subscriptions --> Reporting --> Retention`. The default measure applied is *Count*, but you can change to the appropriate one for you. For the example below, *Monthly Recurring Revenue* was chosen, and the *Month* periodicity remains intact. By using these criteria, you can see the progression of the retention from its start."
|
||||
msgstr ""
|
||||
|
||||
#: ../../subscriptions/reporting/subscription_reports.rst:86
|
||||
msgid "Revenue KPIs report"
|
||||
msgstr ""
|
||||
|
||||
#: ../../subscriptions/reporting/subscription_reports.rst:88
|
||||
msgid "Go to :menuselection:`Subscriptions --> Reporting --> Revenue KPIs`. From there, you can check different KPIs: *Monthly Recurring Revenue*, *Net Revenue*, *Non-Recurring Revenue*, *Revenue per Subscription*, *Annual Run-Rate*, *Lifetime Value*, and more. You can also filter this information on subscriptions, companies, and sales teams. This is useful if you are looking for specific information."
|
||||
msgstr ""
|
||||
|
||||
#: ../../subscriptions/reporting/subscription_reports.rst:98
|
||||
msgid "The example below shows the *Monthly Recurring Revenue* detailed report. At the moment, there is no data, which is the typical scenario for a new business. But, as your company grows over the months, these graphs get populated with more and more data. Once again, you can filter these specific KPIs on subscriptions, companies, and sales teams."
|
||||
msgstr ""
|
||||
|
||||
#: ../../subscriptions/reporting/subscription_reports.rst:108
|
||||
msgid "Salesperson dashboard report"
|
||||
msgstr ""
|
||||
|
||||
#: ../../subscriptions/reporting/subscription_reports.rst:110
|
||||
msgid "Go to :menuselection:`Subscriptions --> Reporting --> Salesperson Dashboard`. This page gives you a summary of your *Monthly Recurring Revenue*, *Non-Recurring Revenue*, *Subscription modifications*, and *Non-Recurring Invoices* for each of your salespeople. You can choose the period you want to apply and the salesperson you want to analyze."
|
||||
msgstr ""
|
||||
|
||||
#: ../../subscriptions/sales_flow.rst:3
|
||||
msgid "Sales flow"
|
||||
msgstr ""
|
||||
|
||||
#: ../../subscriptions/sales_flow/closing.rst:3
|
||||
msgid "Close a subscription"
|
||||
msgstr ""
|
||||
|
||||
#: ../../subscriptions/sales_flow/closing.rst:5
|
||||
msgid "Losing a customer is always difficult, especially if you put a lot of effort into getting them to sign up for your products/services. However, many companies come up with dubious methods to reduce the probability of this happening."
|
||||
msgstr ""
|
||||
|
||||
#: ../../subscriptions/sales_flow/closing.rst:14
|
||||
msgid "If you adopt such methods, you are among companies that actively and indirectly spread the phobia of subscriptions, who do not think about how negatively dissatisfied customers could impact their business and, who frustrate the customers in a way or another. However, at some point, it is understandable that you do not want your customers to be involved in your subscription status."
|
||||
msgstr ""
|
||||
|
||||
#: ../../subscriptions/sales_flow/closing.rst:19
|
||||
msgid "If you do not adopt such methods, you are among companies that continue to evolve in a long-term subscription business model, especially in an era of ultra-fast communications between dissatisfied customers, and who retain their customers by making it easier for them to leave if they want to. By giving them the opportunity to close their own subscriptions, your customers do not feel trapped because they subscribed to your products/services."
|
||||
msgstr ""
|
||||
|
||||
#: ../../subscriptions/sales_flow/closing.rst:25
|
||||
msgid "In summary, the **Odoo Subscriptions** application gives you the **possibility to choose what you want to apply**. Indeed, you can decide whether to give your customers the option to close their subscriptions whenever they want to or to restrict this possibility. It depends on you and we will show you how to do that in our amazing application."
|
||||
msgstr ""
|
||||
|
||||
#: ../../subscriptions/sales_flow/closing.rst:33
|
||||
msgid "Go to :menuselection:`Subscriptions --> Configuration --> Subscription templates`. From there, you can create a new *Subscription template* or modify an existing one. When editing your template, underneath the Invoicing tab, you have the possibility to activate the option *Closable by customer*. Once enabled, this option gives your customers the right to close their own subscriptions."
|
||||
msgstr ""
|
||||
|
||||
#: ../../subscriptions/sales_flow/closing.rst:43
|
||||
msgid "Be sure to check out our documentation on how to :doc:`Use subscription templates <../../subscriptions/configuration/subscription_templates>` to fully understand the importance of this feature in a basic flow using the **Odoo Subscriptions** application."
|
||||
msgstr ""
|
||||
|
||||
#: ../../subscriptions/sales_flow/closing.rst:49
|
||||
msgid "Close your first subscription"
|
||||
msgstr ""
|
||||
|
||||
#: ../../subscriptions/sales_flow/closing.rst:52
|
||||
msgid "Administrator view"
|
||||
msgstr ""
|
||||
|
||||
#: ../../subscriptions/sales_flow/closing.rst:54
|
||||
msgid "Once confirmed, a quotation becomes a sales order and a new subscription is automatically created. Therefore, this subscription has the status *In progress*. From there, you have the possibility to close the subscription."
|
||||
msgstr ""
|
||||
|
||||
#: ../../subscriptions/sales_flow/closing.rst:62
|
||||
msgid "By using the smart button *Close*, you have to enter a close reason. For example, \"Subscription too expensive\", \"Subscription does not meet my requirements\", \"Subscription reached its end date\", etc. Immediately after confirming your close reason, you can observe that the status of the subscription is now *Closed* and that the close reason is mentioned on the subscription."
|
||||
msgstr ""
|
||||
|
||||
#: ../../subscriptions/sales_flow/closing.rst:72
|
||||
msgid "Customer view"
|
||||
msgstr ""
|
||||
|
||||
#: ../../subscriptions/sales_flow/closing.rst:74
|
||||
msgid "As previously explained in the *Administrator view* part, from the subscription form, you also have the possibility to visualize what your customers see when managing their subscriptions thanks to the *Customer preview* button. In this example, the customer has the choice to close his/her subscription whenever he/she wants to, due to the *Close Subscription* button."
|
||||
msgstr ""
|
||||
|
||||
#: ../../subscriptions/sales_flow/closing.rst:83
|
||||
msgid "By using this button, the customer can specify the reason for cancelling his/her subscription and he/she can even leave a message."
|
||||
msgstr ""
|
||||
|
||||
#: ../../subscriptions/sales_flow/closing.rst:90
|
||||
msgid "By confirming the cancellation, the customer is redirected to his/her portal. The administrator is informed of this modification. Indeed, the status of the subscription becomes *Closed* and a note appears in the chatter with the new stage, the end date, the close reason, and the closing text added by the customer."
|
||||
msgstr ""
|
||||
|
||||
#: ../../subscriptions/sales_flow/closing.rst:100
|
||||
msgid "Before closing a subscription, check out our documentation on how to :doc:`Create a quotation using subscription products <../../subscriptions/sales_flow/create_a_quotation>` to understand how subscriptions are managed in the **Odoo Subscriptions** application."
|
||||
msgstr ""
|
||||
|
||||
#: ../../subscriptions/sales_flow/create_a_quotation.rst:3
|
||||
msgid "Create a quotation using subscription products"
|
||||
msgstr ""
|
||||
|
||||
#: ../../subscriptions/sales_flow/create_a_quotation.rst:5
|
||||
msgid "Selling a digital product or service gives instant gratification. However, you have to work hard for a new customer to make a purchase. It costs time and money. By convincing customers to sign up for a subscription, you maximize your income and streamline your cash flow. You can sell any type of product or service through a subscription business model."
|
||||
msgstr ""
|
||||
|
||||
#: ../../subscriptions/sales_flow/create_a_quotation.rst:15
|
||||
msgid "Here is a scenario using **Odoo Subscriptions** to create a quotation including subscription products."
|
||||
msgstr ""
|
||||
|
||||
#: ../../subscriptions/sales_flow/create_a_quotation.rst:19
|
||||
msgid "Create your first quotation"
|
||||
msgstr ""
|
||||
|
||||
#: ../../subscriptions/sales_flow/create_a_quotation.rst:21
|
||||
msgid "Before creating your first quotation, be sure to check out our documentation on how to create and manage your own :doc:`Subscription templates <../../subscriptions/configuration/subscription_templates>` and on how to add :doc:`Subscription products <../../subscriptions/configuration/subscription_products>` to your templates."
|
||||
msgstr ""
|
||||
|
||||
#: ../../subscriptions/sales_flow/create_a_quotation.rst:30
|
||||
msgid "These steps are **mandatory** to make a basic sales flow using **Odoo Subscriptions**."
|
||||
msgstr ""
|
||||
|
||||
#: ../../subscriptions/sales_flow/create_a_quotation.rst:32
|
||||
msgid "Go to **Odoo Sales** and create a new quotation. Then, choose a customer and add a product. Be careful to select a product that you previously configured as a *Subscription product*."
|
||||
msgstr ""
|
||||
|
||||
#: ../../subscriptions/sales_flow/create_a_quotation.rst:39
|
||||
msgid "When your quotation is ready, you have the possibility to send it to your customers or to confirm it. It is better to first *Send by email* the quotation to your customers to have their confirmation and, then, *Confirm* it in **Odoo Sales**. By clicking on *Customer preview*, you have an idea of what your customers will see when receiving your quotation."
|
||||
msgstr ""
|
||||
|
||||
#: ../../subscriptions/sales_flow/create_a_quotation.rst:48
|
||||
msgid "From there, your customers have three choices: *Sign & Pay* the quotation, give you a *Feedback* or *Reject* the quotation. It appears that they are very happy and accept the option *Sign & Pay*. Then, they have to validate the order with a signature and by choosing a payment method. When it is done, you can check out the quotation in **Odoo Sales** and *Confirm* it."
|
||||
msgstr ""
|
||||
|
||||
#: ../../subscriptions/sales_flow/create_a_quotation.rst:54
|
||||
msgid "Manage your subscriptions from your SO"
|
||||
msgstr ""
|
||||
|
||||
#: ../../subscriptions/sales_flow/create_a_quotation.rst:56
|
||||
msgid "Once confirmed, the quotation becomes a sales order and a new button appears, *Subscriptions*. Indeed, a subscription is automatically created."
|
||||
msgstr ""
|
||||
|
||||
#: ../../subscriptions/sales_flow/create_a_quotation.rst:63
|
||||
msgid "By clicking on the *Subscriptions* button, you can see that the status of the subscription is *In progress*. From there, you will have three options: :doc:`Renew <../../subscriptions/sales_flow/renewals>`, :doc:`Close <../../subscriptions/sales_flow/closing>` or :doc:`Upsell <../../subscriptions/sales_flow/upselling>` your subscription."
|
||||
msgstr ""
|
||||
|
||||
#: ../../subscriptions/sales_flow/create_a_quotation.rst:73
|
||||
msgid "In the top-right corner, you can see the status of the subscription. When a subscription is new and created from **Odoo Subscriptions**, the status is *Draft*. When a sales order has been validated, the status is *In progress*. Finally, when a customer decides to close his subscription, the status becomes *Closed*."
|
||||
msgstr ""
|
||||
|
||||
#: ../../subscriptions/sales_flow/create_a_quotation.rst:81
|
||||
msgid ":doc:`../../subscriptions/sales_flow/renewals`"
|
||||
msgstr ""
|
||||
|
||||
#: ../../subscriptions/sales_flow/create_a_quotation.rst:82
|
||||
msgid ":doc:`../../subscriptions/sales_flow/closing`"
|
||||
msgstr ""
|
||||
|
||||
#: ../../subscriptions/sales_flow/create_a_quotation.rst:83
|
||||
msgid ":doc:`../../subscriptions/sales_flow/upselling`"
|
||||
msgstr ""
|
||||
|
||||
#: ../../subscriptions/sales_flow/renewals.rst:3
|
||||
msgid "Renew a subscription"
|
||||
msgstr ""
|
||||
|
||||
#: ../../subscriptions/sales_flow/renewals.rst:5
|
||||
msgid "The key feature of a subscription business model is the recurring nature of payments. In this model, customers pay a recurring amount in exchange for access to a product or a service."
|
||||
msgstr ""
|
||||
|
||||
#: ../../subscriptions/sales_flow/renewals.rst:14
|
||||
msgid "Each subscriber experiences this renewal process monthly, annually, or sometimes more, depending on the duration of the contract. Most subscription companies choose to automate their renewal processes but, in some cases, manual subscription renewals are still the preferred option."
|
||||
msgstr ""
|
||||
|
||||
#: ../../subscriptions/sales_flow/renewals.rst:18
|
||||
msgid "With **Odoo Subscriptions**, you can have all your subscriptions in one application, suggest an automatic subscription renewal to your customers (as well as a manual one) and, finally, filter all your subscriptions and easily find those to renew (with the help of the tag *To renew*)."
|
||||
msgstr ""
|
||||
|
||||
#: ../../subscriptions/sales_flow/renewals.rst:23
|
||||
msgid "Renew your first subscription"
|
||||
msgstr ""
|
||||
|
||||
#: ../../subscriptions/sales_flow/renewals.rst:25
|
||||
msgid "Before renewing a subscription, be sure to check out our documentation on how to :doc:`Create a quotation <../../subscriptions/sales_flow/create_a_quotation>` using subscription products. Indeed, once confirmed, a quotation becomes a sales order and a new subscription is automatically created. Therefore, this subscription has the status *In progress*. From there, you have the possibility to renew the subscription. In the Other Info tab, underneath the To Renew section, you can activate the *To renew* option. When activated, a yellow tag automatically appears in the upper right corner of the subscription."
|
||||
msgstr ""
|
||||
|
||||
#: ../../subscriptions/sales_flow/renewals.rst:38
|
||||
msgid "The *To renew* tag is automatically ticked when a payment fails. This indicator also appears on the customer portal. To visualize that, you just have to click on the *Customer preview* button. The tag *To renew* appears on the top right corner."
|
||||
msgstr ""
|
||||
|
||||
#: ../../subscriptions/sales_flow/renewals.rst:46
|
||||
msgid "When a subscription needs to be renewed, you have the possibility to use a new button called *Renewal quotation*. By clicking on it, a new quotation is created. From there, start a basic sales flow allowing you to send the quotation by email to your customers or to confirm it. It is better to first *Send by email* the quotation to your customers in order to have their confirmation and, then, *Confirm* it in **Odoo Sales**."
|
||||
msgstr ""
|
||||
|
||||
#: ../../subscriptions/sales_flow/renewals.rst:53
|
||||
msgid "In the Chatter of this new quotation, it is mentioned that \"This renewal order has been created from the previous subscription\". Once confirmed by your customers, this quotation becomes a sales order and a new sale is mentioned in the upper right corner of the subscription."
|
||||
msgstr ""
|
||||
|
||||
#: ../../subscriptions/sales_flow/renewals.rst:61
|
||||
msgid "By clicking on the *Sales* button, you have a summary of your sales orders in a list view. The only difference between your two quotations is the description underneath the *Subscription Management* category. There, you can easily visualize which one is your renewal."
|
||||
msgstr ""
|
||||
|
||||
#: ../../subscriptions/sales_flow/renewals.rst:70
|
||||
msgid "Visualize your subscriptions to renew"
|
||||
msgstr ""
|
||||
|
||||
#: ../../subscriptions/sales_flow/renewals.rst:72
|
||||
msgid "Finally, if you want to visualize all your subscriptions and easily find those to renew, you can go to your *Subscriptions dashboard* and use the filter *To renew*."
|
||||
msgstr ""
|
||||
|
||||
#: ../../subscriptions/sales_flow/upselling.rst:3
|
||||
msgid "Upsell a subscription"
|
||||
msgstr ""
|
||||
|
||||
#: ../../subscriptions/sales_flow/upselling.rst:5
|
||||
msgid "Subscriptions are recurrent and go on indefinitely. As time passes by, our customers may want to modify them. We must then be able to adapt the prices or change the products’ quantities to accommodate their needs. Two situations can happen:"
|
||||
msgstr ""
|
||||
|
||||
#: ../../subscriptions/sales_flow/upselling.rst:9
|
||||
msgid "**Loyal customers:** This kind of customers already trust you as a brand. Therefore, you are confident regarding what you offer since they keep paying for your products and services. Consequently, it is easier to sell them something additional than it would be to a new customer."
|
||||
msgstr ""
|
||||
|
||||
#: ../../subscriptions/sales_flow/upselling.rst:14
|
||||
msgid "**New customers:** For this kind of customers, you have to come with something new, something attractive. What about discounts? Typically, every subscription ends after a certain given time. Making these types of offers for new customers strengthens your relationships with them and also increases their retention."
|
||||
msgstr ""
|
||||
|
||||
#: ../../subscriptions/sales_flow/upselling.rst:27
|
||||
msgid "As previously explained, to upsell a subscription to new customers, it is recommended to offer *Discounts*. To activate this option, go to :menuselection:`Sales --> Configuration --> Settings` and, under the *Pricing* category, you have the possibility to grant discounts on sales order lines."
|
||||
msgstr ""
|
||||
|
||||
#: ../../subscriptions/sales_flow/upselling.rst:36
|
||||
msgid "Upsell your first subscription"
|
||||
msgstr ""
|
||||
|
||||
#: ../../subscriptions/sales_flow/upselling.rst:38
|
||||
msgid "Before upselling a subscription, be sure to check out our documentation on how to :doc:`Create a quotation <../../subscriptions/sales_flow/create_a_quotation>` using subscription products. Indeed, once confirmed, a quotation becomes a sales order and a new subscription is automatically created. Therefore, this subscription has the status *In progress*. From there, you have the possibility to upsell your subscription."
|
||||
msgstr ""
|
||||
|
||||
#: ../../subscriptions/sales_flow/upselling.rst:48
|
||||
msgid "By using the smart button *Upsell*, you are able to create a new quotation with new subscription products and send it to your customers for approval."
|
||||
msgstr ""
|
||||
|
||||
#: ../../subscriptions/sales_flow/upselling.rst:56
|
||||
msgid "When the quotation is confirmed by your customers, the products are added to the initial subscription. Quotation prices are, then, prorated to the remaining time of the current invoicing period."
|
||||
msgstr ""
|
||||
|
||||
#: ../../subscriptions/sales_flow/upselling.rst:60
|
||||
msgid "Of course, before sending this new quotation to your customers, you can change the unit price, taxes, and, even the discount you want to offer. The smart button *Customer preview* is useful for mimicking the customer's reaction. In this case, we can confidently say that the customer will *Sign and pay* this new quotation. When it is done, you have to go back in edit mode, confirm the quotation, and click on the smart button *Subscriptions* to visualize all updates. From there, you can see that an additional line has been added to the subscription with the new extra service the customer wanted to purchase."
|
||||
msgstr ""
|
||||
|
||||
#: ../../subscriptions/sales_flow/upselling.rst:72
|
||||
msgid "In addition, by clicking on the *Sales* button, you have a summary of your sales orders in a list view."
|
||||
msgstr ""
|
||||
|
||||
#: ../../subscriptions/sales_flow/upselling.rst:79
|
||||
msgid "The only difference between your two sales orders is the description underneath the *Subscription Management* category. There, you can easily visualize which one is your upselling."
|
||||
msgstr ""
|
||||
|
||||
@ -8,7 +8,7 @@ msgid ""
|
||||
msgstr ""
|
||||
"Project-Id-Version: Odoo 13.0\n"
|
||||
"Report-Msgid-Bugs-To: \n"
|
||||
"POT-Creation-Date: 2019-11-20 10:20+0100\n"
|
||||
"POT-Creation-Date: 2020-09-22 16:26+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,382 +61,203 @@ 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
|
||||
msgid "🟢"
|
||||
#: ../../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
|
||||
msgid "🟠"
|
||||
#: ../../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
|
||||
msgid "🔴"
|
||||
#: ../../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
|
||||
msgid "🟢 Supported version"
|
||||
msgstr ""
|
||||
|
||||
#: ../../support/supported_versions.rst:56
|
||||
msgid "🔴 End-of-support"
|
||||
msgid "|green| Supported version"
|
||||
msgstr ""
|
||||
|
||||
#: ../../support/supported_versions.rst:58
|
||||
msgid "N/A Never released for this platform"
|
||||
msgid "|red| End-of-support"
|
||||
msgstr ""
|
||||
|
||||
#: ../../support/supported_versions.rst:60
|
||||
msgid "🟠 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."
|
||||
msgid "N/A Never released for this platform"
|
||||
msgstr ""
|
||||
|
||||
#: ../../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:64
|
||||
msgid "🏁 Future version, not released yet"
|
||||
msgstr ""
|
||||
|
||||
#: ../../support/supported_versions.rst:66
|
||||
#: ../../support/supported_versions.rst:77
|
||||
msgid "I run an older version of Odoo/OpenERP/TinyERP"
|
||||
msgstr ""
|
||||
|
||||
#: ../../support/supported_versions.rst:68
|
||||
#: ../../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:70
|
||||
#: ../../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:72
|
||||
#: ../../support/supported_versions.rst:83
|
||||
msgid "You should consider `upgrading <https://upgrade.odoo.com/>`_ your database."
|
||||
msgstr ""
|
||||
|
||||
#: ../../support/user_doc.rst:6
|
||||
msgid "Contribute to the documentation"
|
||||
msgstr ""
|
||||
|
||||
#: ../../support/user_doc.rst:9
|
||||
msgid "First of all..."
|
||||
msgstr ""
|
||||
|
||||
#: ../../support/user_doc.rst:11
|
||||
msgid "**... Thank you for landing here and helping us to improve the user documentation of Odoo.**"
|
||||
msgstr ""
|
||||
|
||||
#: ../../support/user_doc.rst:15
|
||||
msgid "Edit an existing page"
|
||||
msgstr ""
|
||||
|
||||
#: ../../support/user_doc.rst:17
|
||||
msgid "As our documentation is maintained on GitHub, you'll need a free `GitHub account <https://help.github.com/en/articles/signing-up-for-a-new-github-account>`_."
|
||||
msgstr ""
|
||||
|
||||
#: ../../support/user_doc.rst:18
|
||||
msgid "Pick a page in our `user documentation <https://www.odoo.com/documentation/user>`_. **Please take care of choosing the right version of Odoo.**"
|
||||
msgstr ""
|
||||
|
||||
#: ../../support/user_doc.rst:19
|
||||
msgid "Click on **Edit on Github** in the left menu."
|
||||
msgstr ""
|
||||
|
||||
#: ../../support/user_doc.rst:25
|
||||
msgid "If this is the first time you edit our documentation, click on **Fork repository**, else you won't see this step."
|
||||
msgstr ""
|
||||
|
||||
#: ../../support/user_doc.rst:26
|
||||
msgid "Use Github's editor to add your text. Text is tagged with a simple syntax called `RST <http://docutils.sourceforge.net/rst.html>`_. Don't worry, it's not so hard to learn 🤓... See the following section of this document for a quick overview of RST commands."
|
||||
msgstr ""
|
||||
|
||||
#: ../../support/user_doc.rst:32
|
||||
msgid "Click on **Preview changes** to review your contribution in a human-readable format."
|
||||
msgstr ""
|
||||
|
||||
#: ../../support/user_doc.rst:38
|
||||
msgid "In the **Propose file change** section, add a short title to your contribution. The title should summarize your changes. You may use the second box to add an extended description if your contribution requires a longer explanation."
|
||||
msgstr ""
|
||||
|
||||
#: ../../support/user_doc.rst:44
|
||||
msgid "Submit your contribution by clicking on **Propose file change**."
|
||||
msgstr ""
|
||||
|
||||
#: ../../support/user_doc.rst:45
|
||||
msgid "Click on **Create pull request**."
|
||||
msgstr ""
|
||||
|
||||
#: ../../support/user_doc.rst:46
|
||||
msgid "Wait for an Odoo maintainer to add your contribution. Thank you for your help!"
|
||||
msgstr ""
|
||||
|
||||
#: ../../support/user_doc.rst:49
|
||||
msgid "There is no automatic port of your edit to another version of the documentation."
|
||||
msgstr ""
|
||||
|
||||
#: ../../support/user_doc.rst:51
|
||||
msgid "If your change should apply to multiple versions of Odoo, please warn us in your contribution message."
|
||||
msgstr ""
|
||||
|
||||
#: ../../support/user_doc.rst:55
|
||||
msgid "RST Cheat Sheet"
|
||||
msgstr ""
|
||||
|
||||
#: ../../support/user_doc.rst:57
|
||||
msgid "Here is a summary of the markup elements you may use while editing our documentation."
|
||||
msgstr ""
|
||||
|
||||
#: ../../support/user_doc.rst:60
|
||||
msgid "Code"
|
||||
msgstr ""
|
||||
|
||||
#: ../../support/user_doc.rst:60
|
||||
msgid "Display"
|
||||
msgstr ""
|
||||
|
||||
#: ../../support/user_doc.rst:60
|
||||
msgid "Comments"
|
||||
msgstr ""
|
||||
|
||||
#: ../../support/user_doc.rst:62
|
||||
msgid "Text in *italics*"
|
||||
msgstr ""
|
||||
|
||||
#: ../../support/user_doc.rst:66
|
||||
msgid "Text in **bold** letters"
|
||||
msgstr ""
|
||||
|
||||
#: ../../support/user_doc.rst:70
|
||||
#: ../../support/user_doc.rst:76
|
||||
msgid "Numbered"
|
||||
msgstr ""
|
||||
|
||||
#: ../../support/user_doc.rst:71
|
||||
#: ../../support/user_doc.rst:77
|
||||
msgid "Bullet"
|
||||
msgstr ""
|
||||
|
||||
#: ../../support/user_doc.rst:72
|
||||
#: ../../support/user_doc.rst:78
|
||||
msgid "List"
|
||||
msgstr ""
|
||||
|
||||
#: ../../support/user_doc.rst:70
|
||||
#: ../../support/user_doc.rst:76
|
||||
msgid "Must be surrounded by white lines."
|
||||
msgstr ""
|
||||
|
||||
#: ../../support/user_doc.rst:82
|
||||
msgid "This is `a hyper link <https://www.odoo.com>`_."
|
||||
msgstr ""
|
||||
|
||||
#: ../../support/user_doc.rst:82
|
||||
msgid "Here is `how to enter backticks on your keyboard <https://superuser.com/a/254077>`_."
|
||||
msgstr ""
|
||||
|
||||
#: ../../support/user_doc.rst:85
|
||||
msgid "Don't forget terminal *underscore*."
|
||||
msgstr ""
|
||||
|
||||
#: ../../support/user_doc.rst:90
|
||||
msgid "There are many more commands available, see `comprehensive documentation <http://docutils.sourceforge.net/docs/ref/rst/restructuredtext.html>`_ of RST."
|
||||
msgstr ""
|
||||
|
||||
#: ../../support/user_doc.rst:94
|
||||
msgid "Add images to your documents"
|
||||
msgstr ""
|
||||
|
||||
#: ../../support/user_doc.rst:98
|
||||
msgid "This procedure is possible only for users who have **push** access on the documentation repository (eg: mainly, Odoo maintainers). We are working on improving this."
|
||||
msgstr ""
|
||||
|
||||
#: ../../support/user_doc.rst:101
|
||||
msgid "First of all, prepare your screenshots."
|
||||
msgstr ""
|
||||
|
||||
#: ../../support/user_doc.rst:103
|
||||
msgid "They must be good-quality PNG images."
|
||||
msgstr ""
|
||||
|
||||
#: ../../support/user_doc.rst:104
|
||||
msgid "Crop your screenshots to display only the relevant part of the screen. Large screenshots are hard to read and don't display well in a documentation."
|
||||
msgstr ""
|
||||
|
||||
#: ../../support/user_doc.rst:106
|
||||
msgid "Always take your screenshots on a demo instance of Odoo; **never** include any personal data."
|
||||
msgstr ""
|
||||
|
||||
#: ../../support/user_doc.rst:108
|
||||
msgid "Upload them to the ``media/`` directory which is located next to the page you are editing. If the directory does not exist, create it."
|
||||
msgstr ""
|
||||
|
||||
#: ../../support/user_doc.rst:109
|
||||
msgid "When editing your page, use this code piece in order to load your image:"
|
||||
msgstr ""
|
||||
|
||||
#: ../../support/user_doc.rst:117
|
||||
msgid "Submit your changes"
|
||||
msgstr ""
|
||||
|
||||
#: ../../support/user_doc.rst:128
|
||||
msgid "Technical Details for Nerds"
|
||||
msgstr ""
|
||||
|
||||
#: ../../support/user_doc.rst:130
|
||||
msgid "Advanced users may, of course, fork and clone `the GitHub repository <https://github.com/odoo/documentation-user>`_. Then submit a pull request with the canonical Git/GitHub workflow."
|
||||
msgstr ""
|
||||
|
||||
#: ../../support/user_doc.rst:133
|
||||
msgid "See our `README <https://github.com/odoo/documentation-user/blob/13.0/README.rst>`_ file about building the documentation."
|
||||
msgstr ""
|
||||
|
||||
#: ../../support/user_doc.rst:138
|
||||
msgid "Developer documentation"
|
||||
msgstr ""
|
||||
|
||||
#: ../../support/user_doc.rst:140
|
||||
msgid "Documentation that targets developers of Odoo apps is maintained alongside `the source code of Odoo <https://github.com/odoo/odoo/tree/13.0/doc>`_."
|
||||
msgstr ""
|
||||
|
||||
#: ../../support/user_doc.rst:143
|
||||
msgid "User documentation might contain technicalities yet, when they are related to configuration and everyday use of Odoo."
|
||||
msgstr ""
|
||||
|
||||
#: ../../support/user_doc.rst:149
|
||||
#: ../../support/where_can_i_get_support.rst:36
|
||||
msgid "*Last revision of this page:* |date|"
|
||||
msgstr ""
|
||||
|
||||
#: ../../support/what_can_i_expect.rst:8
|
||||
msgid "What can I expect from the support service?"
|
||||
msgstr ""
|
||||
@ -478,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
|
||||
@ -533,43 +354,43 @@ msgstr ""
|
||||
msgid "Users who have a valid Odoo Enterprise subscription may always contact our support teams through our `support form <https://www.odoo.com/help>`_, no matter the hosting type you chose (Odoo Online, Odoo.sh or on your own server)."
|
||||
msgstr ""
|
||||
|
||||
#: ../../support/where_can_i_get_support.rst:14
|
||||
#: ../../support/where_can_i_get_support.rst:16
|
||||
msgid "Please include in your request:"
|
||||
msgstr ""
|
||||
|
||||
#: ../../support/where_can_i_get_support.rst:16
|
||||
msgid "your subscription number,"
|
||||
msgstr ""
|
||||
|
||||
#: ../../support/where_can_i_get_support.rst:17
|
||||
msgid "if your database is hosted by Odoo (Odoo Online or Odoo.sh), please also send the URL of your database."
|
||||
#: ../../support/where_can_i_get_support.rst:18
|
||||
msgid "your subscription number"
|
||||
msgstr ""
|
||||
|
||||
#: ../../support/where_can_i_get_support.rst:19
|
||||
msgid "the URL of your database if your database is hosted by Odoo (Odoo Online or Odoo.sh)"
|
||||
msgstr ""
|
||||
|
||||
#: ../../support/where_can_i_get_support.rst:21
|
||||
msgid "Our agents will get back to you as soon as possible."
|
||||
msgstr ""
|
||||
|
||||
#: ../../support/where_can_i_get_support.rst:23
|
||||
#: ../../support/where_can_i_get_support.rst:25
|
||||
msgid "Odoo Community"
|
||||
msgstr ""
|
||||
|
||||
#: ../../support/where_can_i_get_support.rst:25
|
||||
#: ../../support/where_can_i_get_support.rst:27
|
||||
msgid "*Odoo Community users don't get access to the support service.*"
|
||||
msgstr ""
|
||||
|
||||
#: ../../support/where_can_i_get_support.rst:27
|
||||
#: ../../support/where_can_i_get_support.rst:29
|
||||
msgid "Here are some resources that might help you:"
|
||||
msgstr ""
|
||||
|
||||
#: ../../support/where_can_i_get_support.rst:29
|
||||
#: ../../support/where_can_i_get_support.rst:31
|
||||
msgid "Our `documentation pages <https://www.odoo.com/page/docs>`_."
|
||||
msgstr ""
|
||||
|
||||
#: ../../support/where_can_i_get_support.rst:30
|
||||
#: ../../support/where_can_i_get_support.rst:32
|
||||
msgid "Ask your question on the `community forum <https://www.odoo.com/forum/help-1>`_."
|
||||
msgstr ""
|
||||
|
||||
#: ../../support/where_can_i_get_support.rst:31
|
||||
msgid "`Buy Odoo Enterprise <https://www.odoo.com/help>`_ to get the support and bugfix services."
|
||||
#: ../../support/where_can_i_get_support.rst:33
|
||||
msgid "`Buy Odoo Enterprise <https://www.odoo.com/documentation/13.0/setup/enterprise.html>`_ to get the support and bugfix services."
|
||||
msgstr ""
|
||||
|
||||
|
||||
172
locale/sources/survey.pot
Normal file
172
locale/sources/survey.pot
Normal file
@ -0,0 +1,172 @@
|
||||
# SOME DESCRIPTIVE TITLE.
|
||||
# Copyright (C) 2015-TODAY, Odoo S.A.
|
||||
# This file is distributed under the same license as the Odoo package.
|
||||
# FIRST AUTHOR <EMAIL@ADDRESS>, YEAR.
|
||||
#
|
||||
#, fuzzy
|
||||
msgid ""
|
||||
msgstr ""
|
||||
"Project-Id-Version: Odoo 13.0\n"
|
||||
"Report-Msgid-Bugs-To: \n"
|
||||
"POT-Creation-Date: 2020-09-22 16:26+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"
|
||||
"MIME-Version: 1.0\n"
|
||||
"Content-Type: text/plain; charset=UTF-8\n"
|
||||
"Content-Transfer-Encoding: 8bit\n"
|
||||
|
||||
#: ../../survey.rst:5
|
||||
msgid "Survey"
|
||||
msgstr ""
|
||||
|
||||
#: ../../survey/overview.rst:3
|
||||
msgid "Overview"
|
||||
msgstr ""
|
||||
|
||||
#: ../../survey/overview/create.rst:3
|
||||
msgid "Get Started with Surveys"
|
||||
msgstr ""
|
||||
|
||||
#: ../../survey/overview/create.rst:5
|
||||
msgid "Surveys can be used for a range of purposes that can go from collecting customer feedback, evaluate the success of an event, measure how pleased customers are with your products/services, gauge whether employees are happy and satisfied with their work environment, and even to find out what your market is thinking."
|
||||
msgstr ""
|
||||
|
||||
#: ../../survey/overview/create.rst:11
|
||||
msgid "Get started"
|
||||
msgstr ""
|
||||
|
||||
#: ../../survey/overview/create.rst:13
|
||||
msgid "When creating your survey, choose a *Title* and *Category*. The *Category* field is used to know in which context the survey is being conducted, as different applications might use it for different purposes such as recruitment, certification, or employee appraisal."
|
||||
msgstr ""
|
||||
|
||||
#: ../../survey/overview/create.rst:22
|
||||
msgid "Tab: Questions"
|
||||
msgstr ""
|
||||
|
||||
#: ../../survey/overview/create.rst:24
|
||||
msgid "Add sections and questions by clicking on the respective links."
|
||||
msgstr ""
|
||||
|
||||
#: ../../survey/overview/create.rst:27
|
||||
msgid "On the *Sections and Questions* form, once the question type is chosen and the answer added, under the tab *Options*, enable *Mandatory Answer*, and set an *Error message* to be shown when the user tries to submit the survey without answering the respective question."
|
||||
msgstr ""
|
||||
|
||||
#: ../../survey/overview/create.rst:29
|
||||
msgid "Depending on the *Question Type*, the tab *Options* aggregates extra and different possibilities. Examples:"
|
||||
msgstr ""
|
||||
|
||||
#: ../../survey/overview/create.rst:31
|
||||
msgid "*Single Line Text Box* - can choose a minimum and maximum text length (number of characters - spaces do not count), and its error message."
|
||||
msgstr ""
|
||||
|
||||
#: ../../survey/overview/create.rst:33
|
||||
msgid "*Multiple choice: multiple answers allowed*: choose between radio buttons or a dropdown menu list, and if you would like to have a comment field. If the user select an answer and type a comment, the values are separately recorded. Or, enable the comment field to be displayed as an answer choice, with which a text type field is displayed."
|
||||
msgstr ""
|
||||
|
||||
#: ../../survey/overview/create.rst:37
|
||||
msgid "*Matrix Type*: choose if you would like to have one or multiple choices per row."
|
||||
msgstr ""
|
||||
|
||||
#: ../../survey/overview/create.rst:44
|
||||
msgid "Tab: Description"
|
||||
msgstr ""
|
||||
|
||||
#: ../../survey/overview/create.rst:46
|
||||
msgid "Write a *Description* to be displayed under the title of the survey's homepage."
|
||||
msgstr ""
|
||||
|
||||
#: ../../survey/overview/create.rst:53
|
||||
msgid "Click on *Edit* to personalize your pages with the website builder."
|
||||
msgstr ""
|
||||
|
||||
#: ../../survey/overview/create.rst:56
|
||||
msgid "Tab: Options"
|
||||
msgstr ""
|
||||
|
||||
#: ../../survey/overview/create.rst:58
|
||||
msgid "Under the tab *Options*, choose the *Layout* of your questions. If choosing *One page per section* or *One page per question*, an option *Back Button* becomes available, which allows the user to go back pages."
|
||||
msgstr ""
|
||||
|
||||
#: ../../survey/overview/create.rst:67
|
||||
msgid "Test and share the survey"
|
||||
msgstr ""
|
||||
|
||||
#: ../../survey/overview/create.rst:70
|
||||
msgid "Once your Survey is ready, *Test* it to avoid *Sharing* it with potential errors. As answers get collected, click on *Answers* to access all the details of the respondent and his answers."
|
||||
msgstr ""
|
||||
|
||||
#: ../../survey/overview/create.rst:72
|
||||
msgid "By default, a filter *Except Test Entries* is applied to keep the list of entries clean with only real participants."
|
||||
msgstr ""
|
||||
|
||||
#: ../../survey/overview/create.rst:79
|
||||
msgid "Another way to access detailed answers is by going to :menuselection:`Participations --> Participations`."
|
||||
msgstr ""
|
||||
|
||||
#: ../../survey/overview/create.rst:80
|
||||
msgid "Click on *See results* to be redirected to an analytical page."
|
||||
msgstr ""
|
||||
|
||||
#: ../../survey/overview/create.rst:87
|
||||
#: ../../survey/overview/time_random.rst:34
|
||||
msgid ":doc:`scoring`"
|
||||
msgstr ""
|
||||
|
||||
#: ../../survey/overview/create.rst:88
|
||||
#: ../../survey/overview/scoring.rst:35
|
||||
msgid ":doc:`time_random`"
|
||||
msgstr ""
|
||||
|
||||
#: ../../survey/overview/scoring.rst:3
|
||||
msgid "Scoring Surveys"
|
||||
msgstr ""
|
||||
|
||||
#: ../../survey/overview/scoring.rst:5
|
||||
msgid "To measure your respondent’s performance, knowledge of a subject, or overall satisfaction, attach points to the answers of specific questions. The points are summed up to give your respondent a final score."
|
||||
msgstr ""
|
||||
|
||||
#: ../../survey/overview/scoring.rst:9
|
||||
msgid "On your survey’s form, click on *Add a question* and, under the tab *Options*, choose between *Scoring with answers at the end* or *Scoring without answers at the end*. Now, on your question’s form, set the right answer and score."
|
||||
msgstr ""
|
||||
|
||||
#: ../../survey/overview/scoring.rst:17
|
||||
msgid "Set the percentage score the user needs to achieve to have successfully taken the survey. If enabling *Certificate*, choose its template. The certification is automatically sent by email to the users who successfully finish it."
|
||||
msgstr ""
|
||||
|
||||
#: ../../survey/overview/scoring.rst:25
|
||||
msgid "Enable *Login required* to be able to *Give Badges*. Badges are related to the eLearning section of your website. Besides the logged-in user, visitors of the website that access the page *Courses* can also see the granted badges."
|
||||
msgstr ""
|
||||
|
||||
#: ../../survey/overview/time_random.rst:3
|
||||
msgid "Time and Randomize Questions"
|
||||
msgstr ""
|
||||
|
||||
#: ../../survey/overview/time_random.rst:6
|
||||
msgid "Time Limit"
|
||||
msgstr ""
|
||||
|
||||
#: ../../survey/overview/time_random.rst:10
|
||||
msgid "On timed surveys, respondents need to complete the survey within a certain period of time. It can be used to ensure that all respondents get the same amount of time to find the answers, or to decrease the chance of having them looking at external resources."
|
||||
msgstr ""
|
||||
|
||||
#: ../../survey/overview/time_random.rst:11
|
||||
msgid "Set the *Time limit* under the tab *Options*."
|
||||
msgstr ""
|
||||
|
||||
#: ../../survey/overview/time_random.rst:17
|
||||
msgid "A timer is shown on the pages so the user can keep track of the remaining time. Surveys not \\ submitted by the *Time limit* do not have their answers saved."
|
||||
msgstr ""
|
||||
|
||||
#: ../../survey/overview/time_random.rst:21
|
||||
msgid "Selection"
|
||||
msgstr ""
|
||||
|
||||
#: ../../survey/overview/time_random.rst:25
|
||||
msgid "When you randomize a survey, you allow for the questions to be shuffled in a random order every time someone opens the questionnaire. This can be useful to avoid having respondents looking at each others' answers."
|
||||
msgstr ""
|
||||
|
||||
#: ../../survey/overview/time_random.rst:27
|
||||
msgid "To do so, under the tab *Options*, enable *Randomized per section*. Now, under the tab *Questions*, set how many of the questions in that section should be taken into account during the shuffling."
|
||||
msgstr ""
|
||||
|
||||
158
locale/sources/timesheets.pot
Normal file
158
locale/sources/timesheets.pot
Normal file
@ -0,0 +1,158 @@
|
||||
# SOME DESCRIPTIVE TITLE.
|
||||
# Copyright (C) 2015-TODAY, Odoo S.A.
|
||||
# This file is distributed under the same license as the Odoo package.
|
||||
# FIRST AUTHOR <EMAIL@ADDRESS>, YEAR.
|
||||
#
|
||||
#, fuzzy
|
||||
msgid ""
|
||||
msgstr ""
|
||||
"Project-Id-Version: Odoo 13.0\n"
|
||||
"Report-Msgid-Bugs-To: \n"
|
||||
"POT-Creation-Date: 2020-09-22 16:26+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"
|
||||
"MIME-Version: 1.0\n"
|
||||
"Content-Type: text/plain; charset=UTF-8\n"
|
||||
"Content-Transfer-Encoding: 8bit\n"
|
||||
|
||||
#: ../../timesheets.rst:5
|
||||
msgid "Timesheets"
|
||||
msgstr ""
|
||||
|
||||
#: ../../timesheets/overview.rst:3
|
||||
msgid "Overview"
|
||||
msgstr ""
|
||||
|
||||
#: ../../timesheets/overview/compare.rst:3
|
||||
msgid "Compare Hours and do Analyses"
|
||||
msgstr ""
|
||||
|
||||
#: ../../timesheets/overview/compare.rst:5
|
||||
msgid "Make sure your employees’ workload is being fairly distributed and control your tasks to get powerful insights when comparing planned versus effective hours."
|
||||
msgstr ""
|
||||
|
||||
#: ../../timesheets/overview/compare.rst:9
|
||||
msgid "Compare the planned and effective hours of your tasks"
|
||||
msgstr ""
|
||||
|
||||
#: ../../timesheets/overview/compare.rst:11
|
||||
msgid "Go to :menuselection:`Project --> Reporting --> Tasks Analysis`, select the *Pivot* view and refine your *Measures* to *Effective Hours* and *Planned Hours*."
|
||||
msgstr ""
|
||||
|
||||
#: ../../timesheets/overview/compare.rst:18
|
||||
msgid "Still on *Project*, under :menuselection:`Reporting --> Planning Analysis` find a pivot view with an analysis of allocated and effective hours of your tasks by user and start date, or by any of the other available filters."
|
||||
msgstr ""
|
||||
|
||||
#: ../../timesheets/overview/compare.rst:27
|
||||
msgid "HR analysis"
|
||||
msgstr ""
|
||||
|
||||
#: ../../timesheets/overview/compare.rst:29
|
||||
msgid "Under :menuselection:`Timesheets --> Reporting --> Timesheet/Attendance` have an overview of the worked hours and allocated time of your employees."
|
||||
msgstr ""
|
||||
|
||||
#: ../../timesheets/overview/get_started.rst:3
|
||||
msgid "Get Started with Timesheets"
|
||||
msgstr ""
|
||||
|
||||
#: ../../timesheets/overview/get_started.rst:5
|
||||
msgid "When you use timesheets (from any device, anywhere) to track the time spent on tasks, you are able to bill customers for the exact right amount they should be billed. In addition to it, add a description of the work done to have a reliable tracking and history, and compare the forecasted times, all in favor of becoming a more proactive company."
|
||||
msgstr ""
|
||||
|
||||
#: ../../timesheets/overview/get_started.rst:11
|
||||
msgid "Choose an encoding unit"
|
||||
msgstr ""
|
||||
|
||||
#: ../../timesheets/overview/get_started.rst:14
|
||||
msgid "Under :menuselection:`Timesheets --> Configuration --> Settings`, choose the unit of measure to register your timesheet. This provides tools and widgets to help you encoding."
|
||||
msgstr ""
|
||||
|
||||
#: ../../timesheets/overview/get_started.rst:15
|
||||
msgid "*Minimal duration* is the minimum time at which a task is recorded."
|
||||
msgstr ""
|
||||
|
||||
#: ../../timesheets/overview/get_started.rst:18
|
||||
msgid "*Rounding up* allows you to time up or down to the nearest minutes or hours. For example: if the interval is set to 30min, a 14min entry will show up in reports as 0min, and a 29min entry as 30min."
|
||||
msgstr ""
|
||||
|
||||
#: ../../timesheets/overview/get_started.rst:25
|
||||
msgid "Reportings are expressed in hours, the default value."
|
||||
msgstr ""
|
||||
|
||||
#: ../../timesheets/overview/get_started.rst:28
|
||||
msgid "Create a task from a SO & timesheet on it"
|
||||
msgstr ""
|
||||
|
||||
#: ../../timesheets/overview/get_started.rst:30
|
||||
msgid "Under the *General Settings* of your product, categorize it as a service."
|
||||
msgstr ""
|
||||
|
||||
#: ../../timesheets/overview/get_started.rst:34
|
||||
msgid "On the *Sales* tab, (section *Sales Invoicing Policy*) choose if you want to invoice customers based on the quantity previous ordered (the one sent on a quotation, for instance), on the time recorded (while the service was being executed), or by manually adding the time spent when creating the invoice."
|
||||
msgstr ""
|
||||
|
||||
#: ../../timesheets/overview/get_started.rst:37
|
||||
msgid "Chose the right *Service Tracking* for you and, from now on, when a sales order is confirmed, Odoo automatically creates a task/project (if that was the chosen option) and allows you to timesheet on it."
|
||||
msgstr ""
|
||||
|
||||
#: ../../timesheets/overview/get_started.rst:44
|
||||
msgid "Choose an Invoicing Policy"
|
||||
msgstr ""
|
||||
|
||||
#: ../../timesheets/overview/get_started.rst:46
|
||||
msgid "Go to :menuselection:`Timesheets --> Configuration --> Settings` and choose if you want the recorded time to be directly invoiced, or if it should be approved first."
|
||||
msgstr ""
|
||||
|
||||
#: ../../timesheets/overview/get_started.rst:54
|
||||
msgid "Send reminders"
|
||||
msgstr ""
|
||||
|
||||
#: ../../timesheets/overview/get_started.rst:57
|
||||
msgid "Choose to have an automatic email being sent to all users and managers who have not recorded their times."
|
||||
msgstr ""
|
||||
|
||||
#: ../../timesheets/overview/get_started.rst:59
|
||||
msgid "Go to :menuselection:`Timesheets --> Configuration --> Settings` and enable the *Employee Reminder* and *Manager Reminder* features."
|
||||
msgstr ""
|
||||
|
||||
#: ../../timesheets/overview/get_started.rst:66
|
||||
msgid "Odoo Timesheets continues to run even if there is no internet connection. The data syncs once you are back online."
|
||||
msgstr ""
|
||||
|
||||
#: ../../timesheets/overview/time_off.rst:3
|
||||
msgid "Create Timesheets upon Time Off Validation"
|
||||
msgstr ""
|
||||
|
||||
#: ../../timesheets/overview/time_off.rst:5
|
||||
msgid "Odoo automatically timesheets on project/tasks upon time off requests. This allows for better overall control over the validation of timesheets, as it does not leave place for forgetfulness and questions after hours that have not been timesheeted by the employee."
|
||||
msgstr ""
|
||||
|
||||
#: ../../timesheets/overview/time_off.rst:9
|
||||
msgid "Activate the :doc:`Developer mode <../../general/developer_mode/activate>`, go to *Timesheets*, and change the *Project* and *Task* set by default, if you like."
|
||||
msgstr ""
|
||||
|
||||
#: ../../timesheets/overview/time_off.rst:16
|
||||
msgid "Go to :menuselection:`Time Off --> Configuration --> Time Off Types`. Select or create the needed type, and decide if you would like the requests to be validated or not."
|
||||
msgstr ""
|
||||
|
||||
#: ../../timesheets/overview/time_off.rst:26
|
||||
msgid "Now, once the employee has requested his time off and the request has been validated (or not, depending on the setting chosen), the time is automatically allocated on *Timesheets*, under the respective project and task."
|
||||
msgstr ""
|
||||
|
||||
#: ../../timesheets/overview/time_off.rst:27
|
||||
msgid "On the example below, the user requested *Paid Time off* from July 13th to 15th."
|
||||
msgstr ""
|
||||
|
||||
#: ../../timesheets/overview/time_off.rst:33
|
||||
msgid "Considering that validation is not required, the requested time off is automatically displayed in *Timesheets*. If validation is necessary, the time is automatically allocated after the responsible person for validating does it so."
|
||||
msgstr ""
|
||||
|
||||
#: ../../timesheets/overview/time_off.rst:41
|
||||
msgid "Click on the magnifying glass, hovering over the concerned cell, to access all the aggregated data on that cell (day), and see details regarding the project/task."
|
||||
msgstr ""
|
||||
|
||||
#: ../../timesheets/overview/time_off.rst:49
|
||||
msgid ":doc:`compare`"
|
||||
msgstr ""
|
||||
|
||||
@ -8,7 +8,7 @@ msgid ""
|
||||
msgstr ""
|
||||
"Project-Id-Version: Odoo 13.0\n"
|
||||
"Report-Msgid-Bugs-To: \n"
|
||||
"POT-Creation-Date: 2019-11-21 10:39+0100\n"
|
||||
"POT-Creation-Date: 2020-09-22 16:26+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"
|
||||
@ -49,10 +49,10 @@ msgid "Go to the *Configuration* menu of your Odoo's Website app. In the setting
|
||||
msgstr ""
|
||||
|
||||
#: ../../website/optimize/google_analytics.rst:27
|
||||
msgid "To make your first steps in Google Analytics, refer to `Google Documentation. <https://support.google.com/analytics/answer/1008015?hl=en/>`__"
|
||||
msgid "To make your first steps in Google Analytics, refer to `Google Documentation <https://support.google.com/analytics/answer/1008015?hl=en/>`_."
|
||||
msgstr ""
|
||||
|
||||
#: ../../website/optimize/google_analytics.rst:31
|
||||
#: ../../website/optimize/google_analytics.rst:32
|
||||
msgid ":doc:`google_analytics_dashboard`"
|
||||
msgstr ""
|
||||
|
||||
@ -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 ""
|
||||
@ -169,15 +237,15 @@ msgid "**Odoo Blogs**: write great contents."
|
||||
msgstr ""
|
||||
|
||||
#: ../../website/optimize/seo.rst:62
|
||||
msgid "**Odoo Slides**: publish all your Powerpoint or PDF presentations. Their content is automatically indexed on the web page. Example: `https://www.odoo.com/slides/public-channel-1 <https://www.odoo.com/slides/public-channel-1>`__"
|
||||
msgid "**Odoo Slides**: publish all your Powerpoint or PDF presentations. Their content is automatically indexed on the web page. Example: `odoo.com/slides/public-channel-1 <https://www.odoo.com/slides/public-channel-1>`_"
|
||||
msgstr ""
|
||||
|
||||
#: ../../website/optimize/seo.rst:66
|
||||
msgid "**Odoo Forum**: let your community create contents for you. Example: `https://odoo.com/forum/1 <https://odoo.com/forum/1>`__ (accounts for 30% of Odoo.com landing pages)"
|
||||
msgid "**Odoo Forum**: let your community create contents for you. Example: `odoo.com/forum/1 <https://odoo.com/forum/1>`_ (accounts for 30% of Odoo.com landing pages)"
|
||||
msgstr ""
|
||||
|
||||
#: ../../website/optimize/seo.rst:70
|
||||
msgid "**Odoo Mailing List Archive**: publish mailing list archives on your website. Example: `https://www.odoo.com/groups/community-59 <https://www.odoo.com/groups/community-59>`__ (1000 pages created per month)"
|
||||
msgid "**Odoo Mailing List Archive**: publish mailing list archives on your website. Example: `odoo.com/groups/community-59 <https://www.odoo.com/groups/community-59>`_ (1000 pages created per month)"
|
||||
msgstr ""
|
||||
|
||||
#: ../../website/optimize/seo.rst:76
|
||||
@ -237,7 +305,7 @@ msgid "Test Your Website"
|
||||
msgstr ""
|
||||
|
||||
#: ../../website/optimize/seo.rst:131
|
||||
msgid "You can compare how your website rank, in terms of SEO, against Odoo using WooRank free services: `https://www.woorank.com <https://www.woorank.com>`__"
|
||||
msgid "You can compare how your website rank, in terms of SEO, against Odoo using WooRank free services: `woorank.com <https://www.woorank.com>`_"
|
||||
msgstr ""
|
||||
|
||||
#: ../../website/optimize/seo.rst:136
|
||||
@ -665,7 +733,7 @@ msgid "Most visitors of your website will only need the first two bundles, resul
|
||||
msgstr ""
|
||||
|
||||
#: ../../website/optimize/seo.rst:483
|
||||
msgid "If you work in debug mode, the CSS and Javascript are neither concatenated, nor minified. Thus, it's much slower. But it allows you to easily debug with the Chrome debugger as CSS and Javascript resources are not transformed from their original versions."
|
||||
msgid "If you work on :doc:`Developer mode <../../general/developer_mode/activate>`, the CSS and Javascript are neither concatenated, nor minified. Thus, it's much slower. But it allows you to easily debug with the Chrome debugger as CSS and Javascript resources are not transformed from their original versions."
|
||||
msgstr ""
|
||||
|
||||
#: ../../website/optimize/seo.rst:489
|
||||
@ -737,7 +805,7 @@ msgid "Browser Caching"
|
||||
msgstr ""
|
||||
|
||||
#: ../../website/optimize/seo.rst:548
|
||||
msgid "Javascript, images and CSS resources have an URL that changes dynamically when their content change. As an example, all CSS files are loaded through this URL: `http://localhost:8069/web/content/457-0da1d9d/web.assets\\_common.0.css <http://localhost:8069/web/content/457-0da1d9d/web.assets_common.0.css>`__. The ``457-0da1d9d`` part of this URL will change if you modify the CSS of your website."
|
||||
msgid "Javascript, images and CSS resources have an URL that changes dynamically when their content change. As an example, all CSS files are loaded through this URL: `localhost:8069/web/content/457-0da1d9d/web.assets\\_common.0.css <http://localhost:8069/web/content/457-0da1d9d/web.assets_common.0.css>`__. The ``457-0da1d9d`` part of this URL will change if you modify the CSS of your website."
|
||||
msgstr ""
|
||||
|
||||
#: ../../website/optimize/seo.rst:555
|
||||
@ -749,79 +817,79 @@ msgid "Scalability"
|
||||
msgstr ""
|
||||
|
||||
#: ../../website/optimize/seo.rst:562
|
||||
msgid "In addition to being fast, Odoo is also more scalable than traditional CMS and eCommerce (Drupal, Wordpress, Magento, Prestashop). The following link provides an analysis of the major open source CMS and eCommerce compared to Odoo when it comes to high query volumes: `*https://www.odoo.com/slides/slide/197* <https://www.odoo.com/slides/slide/odoo-cms-performance-comparison-and-optimisation-197>`__"
|
||||
msgid "In addition to being fast, Odoo is also more scalable than traditional CMS and eCommerce (Drupal, Wordpress, Magento, Prestashop). The following link provides an analysis of the major open source CMS and eCommerce compared to Odoo when it comes to high query volumes: `https://www.odoo.com/slides/slide/197 <https://www.odoo.com/slides/slide/odoo-cms-performance-comparison-and-optimisation-197>`_"
|
||||
msgstr ""
|
||||
|
||||
#: ../../website/optimize/seo.rst:568
|
||||
#: ../../website/optimize/seo.rst:571
|
||||
msgid "Here is the slide that summarizes the scalability of Odoo Website & eCommerce."
|
||||
msgstr ""
|
||||
|
||||
#: ../../website/optimize/seo.rst:574
|
||||
#: ../../website/optimize/seo.rst:577
|
||||
msgid "Search Engines Files"
|
||||
msgstr ""
|
||||
|
||||
#: ../../website/optimize/seo.rst:577
|
||||
#: ../../website/optimize/seo.rst:580
|
||||
msgid "Sitemap"
|
||||
msgstr ""
|
||||
|
||||
#: ../../website/optimize/seo.rst:579
|
||||
#: ../../website/optimize/seo.rst:582
|
||||
msgid "The sitemap points out pages to index to search engine robots. Odoo generates a ``/sitemap.xml`` file automatically for you. For performance reasons, this file is cached and updated every 12 hours."
|
||||
msgstr ""
|
||||
|
||||
#: ../../website/optimize/seo.rst:583
|
||||
#: ../../website/optimize/seo.rst:586
|
||||
msgid "By default, all URLs will be in a single ``/sitemap.xml`` file, but if you have a lot of pages, Odoo will automatically create a Sitemap Index file, respecting the `sitemaps.org protocol <http://www.sitemaps.org/protocol.html>`__ grouping sitemap URL's in 45000 chunks per file."
|
||||
msgstr ""
|
||||
|
||||
#: ../../website/optimize/seo.rst:589
|
||||
#: ../../website/optimize/seo.rst:592
|
||||
msgid "Every sitemap entry has 4 attributes that are computed automatically:"
|
||||
msgstr ""
|
||||
|
||||
#: ../../website/optimize/seo.rst:591
|
||||
#: ../../website/optimize/seo.rst:594
|
||||
msgid "``<loc>`` : the URL of a page"
|
||||
msgstr ""
|
||||
|
||||
#: ../../website/optimize/seo.rst:593
|
||||
#: ../../website/optimize/seo.rst:596
|
||||
msgid "``<lastmod>`` : last modification date of the resource, computed automatically based on related object. For a page related to a product, this could be the last modification date of the product or the page."
|
||||
msgstr ""
|
||||
|
||||
#: ../../website/optimize/seo.rst:598
|
||||
#: ../../website/optimize/seo.rst:601
|
||||
msgid "``<priority>`` : modules may implement their own priority algorithm based on their content (example: a forum might assign a priority based on the number of votes on a specific post). The priority of a static page is defined by it's priority field, which is normalized (16 is the default)."
|
||||
msgstr ""
|
||||
|
||||
#: ../../website/optimize/seo.rst:605
|
||||
#: ../../website/optimize/seo.rst:608
|
||||
msgid "Structured Data Markup"
|
||||
msgstr ""
|
||||
|
||||
#: ../../website/optimize/seo.rst:607
|
||||
#: ../../website/optimize/seo.rst:610
|
||||
msgid "Structured Data Markup is used to generate Rich Snippets in search engine results. It is a way for website owners to send structured data to search engine robots; helping them understand your content and create well-presented search results."
|
||||
msgstr ""
|
||||
|
||||
#: ../../website/optimize/seo.rst:612
|
||||
#: ../../website/optimize/seo.rst:615
|
||||
msgid "Google supports a number of rich snippets for content types, including: Reviews, People, Products, Businesses, Events and Organizations."
|
||||
msgstr ""
|
||||
|
||||
#: ../../website/optimize/seo.rst:615
|
||||
#: ../../website/optimize/seo.rst:618
|
||||
msgid "Odoo implements micro data as defined in the `schema.org <http://schema.org>`__ specification for events, eCommerce products, forum posts and contact addresses. This allows your product pages to be displayed in Google using extra information like the price and rating of a product:"
|
||||
msgstr ""
|
||||
|
||||
#: ../../website/optimize/seo.rst:625
|
||||
#: ../../website/optimize/seo.rst:628
|
||||
msgid "robots.txt"
|
||||
msgstr ""
|
||||
|
||||
#: ../../website/optimize/seo.rst:627
|
||||
#: ../../website/optimize/seo.rst:630
|
||||
msgid "When indexing your website, search engines take a first look at the general indexing rules of the a``/robots.txt`` file (allowed robots, sitemap path, etc.). Odoo automatically creates it. Its content is:"
|
||||
msgstr ""
|
||||
|
||||
#: ../../website/optimize/seo.rst:631
|
||||
#: ../../website/optimize/seo.rst:634
|
||||
msgid "User-agent: \\* Sitemap: https://www.odoo.com/sitemap.xml"
|
||||
msgstr ""
|
||||
|
||||
#: ../../website/optimize/seo.rst:634
|
||||
#: ../../website/optimize/seo.rst:637
|
||||
msgid "It means that all robots are allowed to index your website and there is no other indexing rule than specified in the sitemap to be found at following address."
|
||||
msgstr ""
|
||||
|
||||
#: ../../website/optimize/seo.rst:638
|
||||
msgid "You can customize the file *robots* in developer mode from *Settings --> Technical --> User Interface --> Views* (exclude robots, exclude some pages, redirect to a custom Sitemap). Make the Model Data of the view *Non Updatable* to not reset the file after system upgrades."
|
||||
#: ../../website/optimize/seo.rst:641
|
||||
msgid "You can customize the file *robots* in :doc:`Developer mode <../../general/developer_mode/activate>` from *Settings --> Technical --> User Interface --> Views* (exclude robots, exclude some pages, redirect to a custom Sitemap). Make the Model Data of the view *Non Updatable* to not reset the file after system upgrades."
|
||||
msgstr ""
|
||||
|
||||
#: ../../website/publish.rst:3
|
||||
@ -968,20 +1036,44 @@ msgstr ""
|
||||
msgid "It is not required anymore: Odoo generates the certificate for you automatically, using integration with `Let's Encrypt Certificate Authority and ACME protocol <https://letsencrypt.org/how-it-works/>`__. In order to get this, simply add your domain name in your customer portal (a separate certificate is generated for each domain name specified)."
|
||||
msgstr ""
|
||||
|
||||
#: ../../website/publish/domain_name.rst:92
|
||||
msgid "If you already use CloudFlare or a similar service, you can keep using it or simply change for Odoo. The choice is yours."
|
||||
#: ../../website/publish/domain_name.rst:93
|
||||
msgid "**Please note that the certificate generation may take up to 24h.**"
|
||||
msgstr ""
|
||||
|
||||
#: ../../website/publish/domain_name.rst:95
|
||||
msgid "If you already use CloudFlare or a similar service, you can keep using it or simply change for Odoo. The choice is yours."
|
||||
msgstr ""
|
||||
|
||||
#: ../../website/publish/domain_name.rst:99
|
||||
msgid "How to make sure that all my URLs use my custom domain?"
|
||||
msgstr ""
|
||||
|
||||
#: ../../website/publish/domain_name.rst:101
|
||||
msgid "To set up the root URL of your website and of all the links sent in emails, you can ask an administrator of your database (any user in the *Settings* group) to perform a login from the login screen. It's as simple as that!"
|
||||
msgstr ""
|
||||
|
||||
#: ../../website/publish/domain_name.rst:103
|
||||
msgid "If you want to do it manually, you can go to :menuselection:`Settings --> Technical --> System Parameters` . Find the entry called ``web.base.url`` (you can create it if it does not exist) and enter the full URL of your website, like ``https://www.myodoowebsite.com``."
|
||||
msgstr ""
|
||||
|
||||
#: ../../website/publish/domain_name.rst:107
|
||||
msgid "The URL must include the protocol (``https://`` or ``http://``) and must not end by a slash (``/``)."
|
||||
msgstr ""
|
||||
|
||||
#: ../../website/publish/domain_name.rst:109
|
||||
msgid "If you want to block the root URL update when an administrator logs in, you can add a System Parameter called ``web.base.url.freeze`` with its value set to ``True``."
|
||||
msgstr ""
|
||||
|
||||
#: ../../website/publish/domain_name.rst:113
|
||||
msgid "My website is indexed twice by Google"
|
||||
msgstr ""
|
||||
|
||||
#: ../../website/publish/domain_name.rst:97
|
||||
#: ../../website/publish/domain_name.rst:115
|
||||
msgid "If you set up a custom domain *mydomain.com* name for *mydatabase.odoo.com*, Google indexes your website under both names. This is a limitation of the Odoo cloud platforms/"
|
||||
msgstr ""
|
||||
|
||||
#: ../../website/publish/domain_name.rst:102
|
||||
msgid ":doc:`../../discuss/email_servers`"
|
||||
#: ../../website/publish/domain_name.rst:120
|
||||
msgid ":doc:`../../discuss/advanced/email_servers`"
|
||||
msgstr ""
|
||||
|
||||
#: ../../website/publish/multi_website.rst:3
|
||||
@ -1017,7 +1109,7 @@ msgid "Once the theme is selected, you can start to build the homepage of your w
|
||||
msgstr ""
|
||||
|
||||
#: ../../website/publish/multi_website.rst:48
|
||||
msgid "If you run Odoo Online, don’t forget to redirect any new domain name to your Odoo database (CNAME) and to authorize it Odoo-side. `Read <https://www.odoo.com/documentation/user/online/website/publish/domain_name.html>`__"
|
||||
msgid "If you run Odoo Online, don’t forget to redirect any new domain name to your Odoo database (``CNAME``) and to authorize it Odoo-side. See :doc:`domain_name`."
|
||||
msgstr ""
|
||||
|
||||
#: ../../website/publish/multi_website.rst:52
|
||||
@ -1025,7 +1117,7 @@ msgid "Create the menu"
|
||||
msgstr ""
|
||||
|
||||
#: ../../website/publish/multi_website.rst:54
|
||||
msgid "The new website has a default menu with all the installed applications. To edit it, click *Pages > Edit Menu*. Moving forward you only edit the menu of the current website."
|
||||
msgid "The new website has a default menu with all the installed applications. To edit it, click :menuselection:`Pages --> Edit Menu`. Moving forward you only edit the menu of the current website."
|
||||
msgstr ""
|
||||
|
||||
#: ../../website/publish/multi_website.rst:59
|
||||
@ -1037,261 +1129,341 @@ msgid "As easy as ABC! There is a website switcher in the right corner of the ed
|
||||
msgstr ""
|
||||
|
||||
#: ../../website/publish/multi_website.rst:71
|
||||
msgid "When switching, you are redirected to the same domain path on the other website (e.g.,/shop/myproduct). If this URL is not used, you will be redirected to a 404 page but suggested to create a new page from there."
|
||||
msgstr ""
|
||||
|
||||
#: ../../website/publish/multi_website.rst:74
|
||||
msgid "Add features"
|
||||
msgid "When switching, you are redirected to the same domain path on the other website (e.g., ``/shop/myproduct``). If this URL is not used, you will be redirected to a 404 page but prompted to create a new page from there."
|
||||
msgstr ""
|
||||
|
||||
#: ../../website/publish/multi_website.rst:76
|
||||
msgid "Add features"
|
||||
msgstr ""
|
||||
|
||||
#: ../../website/publish/multi_website.rst:78
|
||||
msgid "The website apps you install (e.g., Slides, Blogs) are made available on all your websites. You can, of course, keep them hidden in one website by removing the menu item."
|
||||
msgstr ""
|
||||
|
||||
#: ../../website/publish/multi_website.rst:80
|
||||
#: ../../website/publish/multi_website.rst:82
|
||||
msgid "Each website comes with a high range of specific options in the settings. First, select the website to configure."
|
||||
msgstr ""
|
||||
|
||||
#: ../../website/publish/multi_website.rst:86
|
||||
#: ../../website/publish/multi_website.rst:88
|
||||
msgid "Then, take a look at the options flagged with the earth icon. It means they only impact the very website you are working on."
|
||||
msgstr ""
|
||||
|
||||
#: ../../website/publish/multi_website.rst:92
|
||||
#: ../../website/publish/multi_website.rst:94
|
||||
msgid "You can, for instance, set specific :"
|
||||
msgstr ""
|
||||
|
||||
#: ../../website/publish/multi_website.rst:94
|
||||
#: ../../website/publish/multi_website.rst:96
|
||||
msgid "languages,"
|
||||
msgstr ""
|
||||
|
||||
#: ../../website/publish/multi_website.rst:96
|
||||
#: ../../website/publish/multi_website.rst:98
|
||||
msgid "domain names,"
|
||||
msgstr ""
|
||||
|
||||
#: ../../website/publish/multi_website.rst:98
|
||||
#: ../../website/publish/multi_website.rst:100
|
||||
msgid "social media links,"
|
||||
msgstr ""
|
||||
|
||||
#: ../../website/publish/multi_website.rst:100
|
||||
#: ../../website/publish/multi_website.rst:102
|
||||
msgid "customer portal mode (B2C vs. B2B),"
|
||||
msgstr ""
|
||||
|
||||
#: ../../website/publish/multi_website.rst:102
|
||||
#: ../../website/publish/multi_website.rst:104
|
||||
msgid "dedicated live chat channels,"
|
||||
msgstr ""
|
||||
|
||||
#: ../../website/publish/multi_website.rst:104
|
||||
#: ../../website/publish/multi_website.rst:106
|
||||
msgid "etc."
|
||||
msgstr ""
|
||||
|
||||
#: ../../website/publish/multi_website.rst:106
|
||||
#: ../../website/publish/multi_website.rst:108
|
||||
msgid "The other options are global and apply to all your websites."
|
||||
msgstr ""
|
||||
|
||||
#: ../../website/publish/multi_website.rst:109
|
||||
#: ../../website/publish/multi_website.rst:111
|
||||
msgid "Manage domain names"
|
||||
msgstr ""
|
||||
|
||||
#: ../../website/publish/multi_website.rst:111
|
||||
msgid "As said earlier, your websites can either share the same domain name or use a specific one. If you share it and want to adapt the content per region, set country groups in the setting of each website. Visitors will be redirected to the right website using Geo IP."
|
||||
#: ../../website/publish/multi_website.rst:113
|
||||
msgid "As said earlier, your websites can either share the same domain name or use a specific one. If you share it and want to adapt the content per region, set country groups in the setting of each website. Visitors will be redirected to the right website using GeoIP."
|
||||
msgstr ""
|
||||
|
||||
#: ../../website/publish/multi_website.rst:120
|
||||
msgid "Geo IP is installed by default in Odoo Online. If you run Odoo on-premise, don’t forget to install *Geoip* library."
|
||||
#: ../../website/publish/multi_website.rst:122
|
||||
msgid "Geo IP is installed by default in Odoo Online. If you run Odoo on-premise, don’t forget to install *GeoIP* library. See :doc:`on-premise_geo-ip-installation`"
|
||||
msgstr ""
|
||||
|
||||
#: ../../website/publish/multi_website.rst:123
|
||||
msgid "`Read the full documenation about domain names here <https://www.odoo.com/documentation/user/online/website/publish/domain_name.html>`__,"
|
||||
#: ../../website/publish/multi_website.rst:127
|
||||
msgid ":doc:`domain_name`"
|
||||
msgstr ""
|
||||
|
||||
#: ../../website/publish/multi_website.rst:126
|
||||
#: ../../website/publish/multi_website.rst:130
|
||||
msgid "Customize the visitor experience"
|
||||
msgstr ""
|
||||
|
||||
#: ../../website/publish/multi_website.rst:129
|
||||
#: ../../website/publish/multi_website.rst:133
|
||||
msgid "The customer experience can be customized very profoundly thanks to the menu \\*Customize\\*. All the visual options available there are specific to each website. Go through the different pages to adapt them to this new audience. Focus on workflows, and automatic pages (eCommerce checkout, blogs, events, etc.) as the number of available options is higher there."
|
||||
msgstr ""
|
||||
|
||||
#: ../../website/publish/multi_website.rst:139
|
||||
#: ../../website/publish/multi_website.rst:143
|
||||
msgid "Publish specific content per website"
|
||||
msgstr ""
|
||||
|
||||
#: ../../website/publish/multi_website.rst:142
|
||||
#: ../../website/publish/multi_website.rst:146
|
||||
msgid "Like static pages, any content created from the front-end (product, blog post, etc.) is always only published in the current website. You can change that from the edit form view in the backend and leave the *Website* field blank. This will publish it in all the websites."
|
||||
msgstr ""
|
||||
|
||||
#: ../../website/publish/multi_website.rst:150
|
||||
#: ../../website/publish/multi_website.rst:154
|
||||
msgid "Here are all the objects that you can link to *either one or all the websites*:"
|
||||
msgstr ""
|
||||
|
||||
#: ../../website/publish/multi_website.rst:153
|
||||
#: ../../website/publish/multi_website.rst:157
|
||||
msgid "Products"
|
||||
msgstr ""
|
||||
|
||||
#: ../../website/publish/multi_website.rst:155
|
||||
#: ../../website/publish/multi_website.rst:159
|
||||
msgid "Product Categories for eCommerce"
|
||||
msgstr ""
|
||||
|
||||
#: ../../website/publish/multi_website.rst:157
|
||||
#: ../../website/publish/multi_website.rst:161
|
||||
msgid "Blogs"
|
||||
msgstr ""
|
||||
|
||||
#: ../../website/publish/multi_website.rst:159
|
||||
#: ../../website/publish/multi_website.rst:163
|
||||
msgid "Slide Channels"
|
||||
msgstr ""
|
||||
|
||||
#: ../../website/publish/multi_website.rst:161
|
||||
#: ../../website/publish/multi_website.rst:165
|
||||
msgid "Forums"
|
||||
msgstr ""
|
||||
|
||||
#: ../../website/publish/multi_website.rst:163
|
||||
#: ../../website/publish/multi_website.rst:167
|
||||
msgid "Events"
|
||||
msgstr ""
|
||||
|
||||
#: ../../website/publish/multi_website.rst:165
|
||||
#: ../../website/publish/multi_website.rst:169
|
||||
msgid "Job Positions"
|
||||
msgstr ""
|
||||
|
||||
#: ../../website/publish/multi_website.rst:168
|
||||
#: ../../website/publish/multi_website.rst:172
|
||||
msgid "When you create the record from the backend and publish it, typically a product or an event, it is made available in all websites."
|
||||
msgstr ""
|
||||
|
||||
#: ../../website/publish/multi_website.rst:172
|
||||
#: ../../website/publish/multi_website.rst:176
|
||||
msgid "Publish a page in all websites"
|
||||
msgstr ""
|
||||
|
||||
#: ../../website/publish/multi_website.rst:174
|
||||
#: ../../website/publish/multi_website.rst:178
|
||||
msgid "A new static page is created and only made available in the current website. You can duplicate it to other websites from :menuselection:`Website --> Configuration --> Pages`. To do so, leave the *Website* field empty."
|
||||
msgstr ""
|
||||
|
||||
#: ../../website/publish/multi_website.rst:178
|
||||
#: ../../website/publish/multi_website.rst:182
|
||||
msgid "If you want to duplicate it in just one other website, duplicate the page and set the new website."
|
||||
msgstr ""
|
||||
|
||||
#: ../../website/publish/multi_website.rst:184
|
||||
#: ../../website/publish/multi_website.rst:188
|
||||
msgid "When you edit the page again, the change only affects the current website. A new page is duplicated and tied up to the website. The original page still being linked to all websites."
|
||||
msgstr ""
|
||||
|
||||
#: ../../website/publish/multi_website.rst:189
|
||||
#: ../../website/publish/multi_website.rst:193
|
||||
msgid "By grouping pages by URL in the page manager, you quickly find the original page behind each edited page."
|
||||
msgstr ""
|
||||
|
||||
#: ../../website/publish/multi_website.rst:196
|
||||
#: ../../website/publish/multi_website.rst:200
|
||||
msgid "Multi-companies"
|
||||
msgstr ""
|
||||
|
||||
#: ../../website/publish/multi_website.rst:198
|
||||
#: ../../website/publish/multi_website.rst:202
|
||||
msgid "Each website can be linked to a specific company of your system, in a multi-companies environment."
|
||||
msgstr ""
|
||||
|
||||
#: ../../website/publish/multi_website.rst:204
|
||||
#: ../../website/publish/multi_website.rst:208
|
||||
msgid "With such a configuration, only company-related data appear on the website (products, jobs, events, etc.)."
|
||||
msgstr ""
|
||||
|
||||
#: ../../website/publish/multi_website.rst:207
|
||||
#: ../../website/publish/multi_website.rst:211
|
||||
msgid "Website editors can only view and edit the pages of the records they have access to, typically the ones belonging to their current company (and to their subsidiaries, or child companies in Odoo language). And so is it for visitors."
|
||||
msgstr ""
|
||||
|
||||
#: ../../website/publish/multi_website.rst:213
|
||||
#: ../../website/publish/multi_website.rst:217
|
||||
msgid "If websites are multi-companies, you don’t change company when switching websites. To change the company and see the related content, use the company selector in the menu."
|
||||
msgstr ""
|
||||
|
||||
#: ../../website/publish/multi_website.rst:219
|
||||
#: ../../website/publish/multi_website.rst:223
|
||||
msgid "Configure your eCommerce website"
|
||||
msgstr ""
|
||||
|
||||
#: ../../website/publish/multi_website.rst:221
|
||||
#: ../../website/publish/multi_website.rst:225
|
||||
msgid "eCommerce is a crucial feature in the multi-websites environment. We made it so that the entire flow can be customized to fit the very audience of each website."
|
||||
msgstr ""
|
||||
|
||||
#: ../../website/publish/multi_website.rst:226
|
||||
#: ../../website/publish/multi_website.rst:230
|
||||
msgid "Products only available on one website"
|
||||
msgstr ""
|
||||
|
||||
#: ../../website/publish/multi_website.rst:228
|
||||
#: ../../website/publish/multi_website.rst:232
|
||||
msgid "We already saw earlier how to publish a specific record in only one website. You will find the \\*Website\\* field in the eCommerce tab of the product edit form. Empty means available in all websites."
|
||||
msgstr ""
|
||||
|
||||
#: ../../website/publish/multi_website.rst:236
|
||||
#: ../../website/publish/multi_website.rst:240
|
||||
msgid "Products available on *some* websites"
|
||||
msgstr ""
|
||||
|
||||
#: ../../website/publish/multi_website.rst:238
|
||||
#: ../../website/publish/multi_website.rst:242
|
||||
msgid "To make a product available on some websites, but not all of them, you should duplicate the product for each website."
|
||||
msgstr ""
|
||||
|
||||
#: ../../website/publish/multi_website.rst:241
|
||||
#: ../../website/publish/multi_website.rst:245
|
||||
msgid "If you need a unique reference to manage in your inventory, you should install *Manufacturing\\ and create *Kits* BoMs (bills of materials). Each kit will link each published “virtual” product to the main reference managed in your inventory. That way, any item sold from your website will be converted into the storable item in the delivery order."
|
||||
msgstr ""
|
||||
|
||||
#: ../../website/publish/multi_website.rst:248
|
||||
#: ../../website/publish/multi_website.rst:252
|
||||
msgid "Pricelists"
|
||||
msgstr ""
|
||||
|
||||
#: ../../website/publish/multi_website.rst:250
|
||||
#: ../../website/publish/multi_website.rst:254
|
||||
msgid "To manage specific prices by websites, you can activate *Multiple Sales Prices per Product* in Website settings."
|
||||
msgstr ""
|
||||
|
||||
#: ../../website/publish/multi_website.rst:253
|
||||
msgid "Then, go to :menuselection:`Website --> Products --> Pricelists` to create additional pricelists. Read `Pricelists Documentation <https://www.odoo.com/documentation/user/online/ecommerce/maximizing_revenue/pricing.html>`__,"
|
||||
#: ../../website/publish/multi_website.rst:257
|
||||
msgid "Then, go to :menuselection:`Website --> Products --> Pricelists` to create additional pricelists. See :doc:`../../ecommerce/maximizing_revenue/pricing`."
|
||||
msgstr ""
|
||||
|
||||
#: ../../website/publish/multi_website.rst:256
|
||||
#: ../../website/publish/multi_website.rst:260
|
||||
msgid "If you need help. Select a website to make a pricelist only available on this website."
|
||||
msgstr ""
|
||||
|
||||
#: ../../website/publish/multi_website.rst:262
|
||||
#: ../../website/publish/multi_website.rst:266
|
||||
msgid "Leaving the field empty means that you make it work in all websites if *Selectable* is selected. Otherwise, it makes it only available for backend operations of Sales and Point of Sale applications."
|
||||
msgstr ""
|
||||
|
||||
#: ../../website/publish/multi_website.rst:267
|
||||
#: ../../website/publish/multi_website.rst:271
|
||||
msgid "Payment Acquirers and Delivery Methods"
|
||||
msgstr ""
|
||||
|
||||
#: ../../website/publish/multi_website.rst:269
|
||||
#: ../../website/publish/multi_website.rst:273
|
||||
msgid "By default, published payment acquirers and delivery methods are deployed in all websites. You could already use specific payment acquirers per country using Geo IP by defining countries in their configuration. Now you can also do it per website by filling in the *Website* field."
|
||||
msgstr ""
|
||||
|
||||
#: ../../website/publish/multi_website.rst:275
|
||||
#: ../../website/publish/multi_website.rst:279
|
||||
msgid "Customer accounts"
|
||||
msgstr ""
|
||||
|
||||
#: ../../website/publish/multi_website.rst:277
|
||||
#: ../../website/publish/multi_website.rst:281
|
||||
msgid "There is a setting to choose how to manage customer accounts in Website settings. You can either allow customers to use one account through all the websites or compel them to create one account for each website. This last option is convenient if your websites shouldn’t be related to each other in the visitor mind."
|
||||
msgstr ""
|
||||
|
||||
#: ../../website/publish/multi_website.rst:287
|
||||
#: ../../website/publish/multi_website.rst:291
|
||||
msgid "Technical hints for customization"
|
||||
msgstr ""
|
||||
|
||||
#: ../../website/publish/multi_website.rst:289
|
||||
#: ../../website/publish/multi_website.rst:293
|
||||
msgid "If you want to publish custom objects on the website, here are a few tips to make it work with multi websites:"
|
||||
msgstr ""
|
||||
|
||||
#: ../../website/publish/multi_website.rst:293
|
||||
#: ../../website/publish/multi_website.rst:297
|
||||
msgid "Sitemap: don’t forget the domain in the route to only publish"
|
||||
msgstr ""
|
||||
|
||||
#: ../../website/publish/multi_website.rst:293
|
||||
#: ../../website/publish/multi_website.rst:297
|
||||
msgid "available records in each website’s sitemap."
|
||||
msgstr ""
|
||||
|
||||
#: ../../website/publish/multi_website.rst:297
|
||||
#: ../../website/publish/multi_website.rst:301
|
||||
msgid "Access: you should call the method"
|
||||
msgstr ""
|
||||
|
||||
#: ../../website/publish/multi_website.rst:296
|
||||
#: ../../website/publish/multi_website.rst:300
|
||||
msgid "*can_access_from_current_website* in the controller to make sure the visitor can see a record in the current website."
|
||||
msgstr ""
|
||||
|
||||
#: ../../website/publish/multi_website.rst:301
|
||||
#: ../../website/publish/multi_website.rst:305
|
||||
msgid "Search: when a list of records is displayed, don’t forget to specify"
|
||||
msgstr ""
|
||||
|
||||
#: ../../website/publish/multi_website.rst:300
|
||||
#: ../../website/publish/multi_website.rst:304
|
||||
msgid "the domain to only display records available for the current website."
|
||||
msgstr ""
|
||||
|
||||
#: ../../website/publish/on-premise_geo-ip-installation.rst:3
|
||||
msgid "Geo IP installation (on-premises database)"
|
||||
msgstr ""
|
||||
|
||||
#: ../../website/publish/on-premise_geo-ip-installation.rst:6
|
||||
msgid "Installation"
|
||||
msgstr ""
|
||||
|
||||
#: ../../website/publish/on-premise_geo-ip-installation.rst:8
|
||||
msgid "Please note that the installation depends on your computer operating system and distribution. We will assume here that a Linux operating system is used."
|
||||
msgstr ""
|
||||
|
||||
#: ../../website/publish/on-premise_geo-ip-installation.rst:13
|
||||
msgid "Install `geoip2 <https://pypi.org/project/geoip2/>`__ Python library"
|
||||
msgstr ""
|
||||
|
||||
#: ../../website/publish/on-premise_geo-ip-installation.rst:15
|
||||
msgid "Download the `GeoLite2 City database <https://dev.maxmind.com/geoip/geoip2/geolite2/>`_. You should end up with a file called ``GeoLite2-City.mmdb``"
|
||||
msgstr ""
|
||||
|
||||
#: ../../website/publish/on-premise_geo-ip-installation.rst:19
|
||||
msgid "Move the file to the folder ``/usr/share/GeoIP/``"
|
||||
msgstr ""
|
||||
|
||||
#: ../../website/publish/on-premise_geo-ip-installation.rst:21
|
||||
msgid "Restart the server"
|
||||
msgstr ""
|
||||
|
||||
#: ../../website/publish/on-premise_geo-ip-installation.rst:23
|
||||
msgid "If you can't/don't want to locate the geoip database in ``/usr/share/GeoIP/``, you can use the ``--geoip-db`` option of the Odoo command line interface. This option takes the absolute path to the GeoIP database file and will use it as the GeoIP database. For example:"
|
||||
msgstr ""
|
||||
|
||||
#: ../../website/publish/on-premise_geo-ip-installation.rst:32
|
||||
msgid "`CLI documentation <https://www.odoo.com/documentation/13.0/reference/cmdline.html>`_."
|
||||
msgstr ""
|
||||
|
||||
#: ../../website/publish/on-premise_geo-ip-installation.rst:34
|
||||
msgid "``GeoIP`` Python library can also be used. However this version is discontinued since January 2019. See `GeoLite Legacy databases are now discontinued <https://support.maxmind.com/geolite-legacy-discontinuation-notice/>`_"
|
||||
msgstr ""
|
||||
|
||||
#: ../../website/publish/on-premise_geo-ip-installation.rst:37
|
||||
msgid "How to test GeoIP geolocation in your Odoo website?"
|
||||
msgstr ""
|
||||
|
||||
#: ../../website/publish/on-premise_geo-ip-installation.rst:38
|
||||
msgid "Go into your website. Open the web page on which you want to test ``GeoIP``."
|
||||
msgstr ""
|
||||
|
||||
#: ../../website/publish/on-premise_geo-ip-installation.rst:39
|
||||
msgid "Choose :menuselection:`Customize --> HTML/CSS/JS Editor`."
|
||||
msgstr ""
|
||||
|
||||
#: ../../website/publish/on-premise_geo-ip-installation.rst:40
|
||||
msgid "Add the following piece of XML in the page :"
|
||||
msgstr ""
|
||||
|
||||
#: ../../website/publish/on-premise_geo-ip-installation.rst:46
|
||||
msgid "You should end up with a dictionary indicating the location of the ip address."
|
||||
msgstr ""
|
||||
|
||||
#: ../../website/publish/on-premise_geo-ip-installation.rst:51
|
||||
msgid "If the curly braces are empty ``{}``, it can be for any of the following reason :"
|
||||
msgstr ""
|
||||
|
||||
#: ../../website/publish/on-premise_geo-ip-installation.rst:53
|
||||
msgid "The browsing IP address is the localhost (``127.0.0.1``) or a local area network one (``192.168.*.*``)"
|
||||
msgstr ""
|
||||
|
||||
#: ../../website/publish/on-premise_geo-ip-installation.rst:54
|
||||
msgid "If a reversed proxy is used, make sure to configure it correctly. See `--proxy-mode <https://www.odoo.com/documentation/13.0/reference/cmdline.html#cmdoption-odoo-bin-proxy-mode>`__"
|
||||
msgstr ""
|
||||
|
||||
#: ../../website/publish/on-premise_geo-ip-installation.rst:55
|
||||
msgid "``geoip2`` is not installed or the GeoIP database file wasn't found"
|
||||
msgstr ""
|
||||
|
||||
#: ../../website/publish/on-premise_geo-ip-installation.rst:56
|
||||
msgid "The GeoIP database was unable to resolve the given IP address"
|
||||
msgstr ""
|
||||
|
||||
#: ../../website/publish/translate.rst:3
|
||||
msgid "How to translate my website"
|
||||
msgstr ""
|
||||
@ -1333,7 +1505,7 @@ msgid "To translate the content of the website, click on **Translate** (here **T
|
||||
msgstr ""
|
||||
|
||||
#: ../../website/publish/translate.rst:45
|
||||
msgid "There, if you have installed the Gengo Translator, You will see that next to the **Translate** button you also have a button **Translate automatically**. Once you click on that button, you will be asked some information on your account. If you don't have an account yet, go to `*https://gengo.com/auth/form/login/* <https://gengo.com/auth/form/login/>`__ in order to create one. You need to ask for a public key and a private key."
|
||||
msgid "There, if you have installed the Gengo Translator, You will see that next to the **Translate** button you also have a button **Translate automatically**. Once you click on that button, you will be asked some information on your account. If you don't have an account yet, follow `this link <https://gengo.com/auth/form/login/>`_ in order to create one. You need to ask for a public key and a private key."
|
||||
msgstr ""
|
||||
|
||||
#: ../../website/publish/translate.rst:53
|
||||
|
||||
Loading…
Reference in New Issue
Block a user