# SOME DESCRIPTIVE TITLE. # Copyright (C) Odoo S.A. # This file is distributed under the same license as the Odoo package. # FIRST AUTHOR , YEAR. # # Translators: # Martin Trigaux, 2021 # Collex100, 2021 # Irina Fedulova , 2021 # Ekaterina , 2021 # Ivan Yelizariev // IEL , 2021 # #, fuzzy msgid "" msgstr "" "Project-Id-Version: Odoo 14.0\n" "Report-Msgid-Bugs-To: \n" "POT-Creation-Date: 2021-05-18 07:12+0200\n" "PO-Revision-Date: 2021-05-18 05:18+0000\n" "Last-Translator: Ivan Yelizariev // IEL , 2021\n" "Language-Team: Russian (https://www.transifex.com/odoo/teams/41243/ru/)\n" "MIME-Version: 1.0\n" "Content-Type: text/plain; charset=UTF-8\n" "Content-Transfer-Encoding: 8bit\n" "Language: ru\n" "Plural-Forms: nplurals=4; plural=(n%10==1 && n%100!=11 ? 0 : n%10>=2 && n%10<=4 && (n%100<12 || n%100>14) ? 1 : n%10==0 || (n%10>=5 && n%10<=9) || (n%100>=11 && n%100<=14)? 2 : 3);\n" #: ../../content/applications/productivity.rst:3 msgid "Productivity" msgstr "Производительность" #: ../../content/applications/productivity/discuss.rst:4 msgid "Discuss" msgstr "Обсуждения" #: ../../content/applications/productivity/discuss/advanced.rst:3 msgid "Advanced" msgstr "Расширенный" #: ../../content/applications/productivity/discuss/advanced/email_servers.rst:3 msgid "How to Use my Mail Server to Send and Receive Emails in Odoo" msgstr "" #: ../../content/applications/productivity/discuss/advanced/email_servers.rst:6 msgid "If you are a user of Odoo Online or Odoo.sh..." msgstr "" #: ../../content/applications/productivity/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 "" #: ../../content/applications/productivity/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 "" #: ../../content/applications/productivity/discuss/advanced/email_servers.rst:16 msgid "Scope of this documentation" msgstr "Объем данной документации" #: ../../content/applications/productivity/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 `__ & `Odoo.sh " "`__." msgstr "" #: ../../content/applications/productivity/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 "" "Если ни один из вашей компании не используется для управления почтовыми " "серверами, мы настоятельно рекомендуем вам выбрать эти решения для хостинга " "Odoo. Их система электронной почты работает мгновенно и контролируется " "профессионалами. Тем не менее, вы все еще можете использовать собственные " "почтовые серверы, если хотите самостоятельно управлять вашим сервером " "электронной почты." #: ../../content/applications/productivity/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 "" "Ниже вы найдете некоторую полезную информацию о том, как интегрировать " "собственное решение электронной почты с Odoo." #: ../../content/applications/productivity/discuss/advanced/email_servers.rst:34 msgid "" "Office 365 email servers don't easily allow to send external emails from " "hosts like Odoo. Refer to `Microsoft's documentation " "`__ to make it work." msgstr "" #: ../../content/applications/productivity/discuss/advanced/email_servers.rst:39 msgid "How to manage outbound messages" msgstr "Как управлять исходящими сообщениями" #: ../../content/applications/productivity/discuss/advanced/email_servers.rst:40 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 "" "Как администратор системы, перейдите к :menuselection:`Settings --> General " "Settings` и проверьте * внешние серверы электронной почты *. Нажмите * " "Серверы исходящей почты *, чтобы создать и указать SMTP-данные вашего " "сервера электронной почты. Когда вся информация будет заполнена, нажмите " "кнопку * Проверить подключение *." #: ../../content/applications/productivity/discuss/advanced/email_servers.rst:45 msgid "Here is a typical configuration for a G Suite server." msgstr "Вот типичное настройки сервера G Suite." #: ../../content/applications/productivity/discuss/advanced/email_servers.rst:50 msgid "Then set your email domain name in the General Settings." msgstr "Затем установите имя домена электронной почты в общих настройках." #: ../../content/applications/productivity/discuss/advanced/email_servers.rst:53 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 " "`_." msgstr "" #: ../../content/applications/productivity/discuss/advanced/email_servers.rst:57 msgid "In addition to that, enable the IMAP setting on your Gmail account." msgstr "" #: ../../content/applications/productivity/discuss/advanced/email_servers.rst:61 msgid "Can I use an Office 365 server" msgstr "Можете ли вы использовать сервер Office 365" #: ../../content/applications/productivity/discuss/advanced/email_servers.rst:62 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 "" "Вы можете использовать сервер Office 365, если вы запускаете Odoo на " "собственном сервере. Реестры SMTP Office 365 несовместимы с Odoo Online." #: ../../content/applications/productivity/discuss/advanced/email_servers.rst:65 msgid "" "Please refer to `Microsoft's documentation `__ to configure" " a SMTP relay for your Odoo's IP address." msgstr "" "Пожалуйста, обратитесь к `документации Microsoft `__ для " "настройки ретранслятора SMTP для вашего IP-адреса Odoo." #: ../../content/applications/productivity/discuss/advanced/email_servers.rst:69 msgid "How to use a G Suite server" msgstr "Как использовать сервер G Suite" #: ../../content/applications/productivity/discuss/advanced/email_servers.rst:70 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 " "`__." msgstr "" "Вы можете использовать сервер G Suite для любого типа хостинга Odoo. Чтобы " "это сделать, вам необходимо установить обслуживания SMTP. Шаги настройки " "объясняются в документации `Google " " `__." #: ../../content/applications/productivity/discuss/advanced/email_servers.rst:77 msgid "Be SPF-compliant" msgstr "Будьте совместимыми с SPF" #: ../../content/applications/productivity/discuss/advanced/email_servers.rst:78 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 "" "Если вы используете SPF (Policy Framework для отправителей), чтобы увеличить" " производительность выходных электронных писем, не забудьте авторизовать " "Odoo как отправителя в настройках вашего доменного имени. Вот настройки для " "Odoo Online:" #: ../../content/applications/productivity/discuss/advanced/email_servers.rst:82 msgid "" "If no TXT record is set for SPF, create one with following definition: " "v=spf1 include:_spf.odoo.com ~all" msgstr "" "Если для SPF нет записи TXT, создайте его с последующим определением: v = " "spf1 include: _spf.odoo.com ~ all" #: ../../content/applications/productivity/discuss/advanced/email_servers.rst:84 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 "" "Если запрос SPF TXT уже установлено, добавьте "include: " "_spf.odoo.com". например, для доменного имени, которое направляет " "электронные письма через Odoo Online, и через G Suite это может быть: v = " "spf1 include: _spf.odoo.com include: _spf.google.com ~ all" #: ../../content/applications/productivity/discuss/advanced/email_servers.rst:88 msgid "" "Find `here `__ the exact procedure to " "create or modify TXT records in your own domain registrar." msgstr "" "Найдите `здесь `__ точную процедуру " "создания или изменения TXT-записи в собственном регистраторе доменов." #: ../../content/applications/productivity/discuss/advanced/email_servers.rst:91 msgid "" "Your new SPF record can take up to 48 hours to go into effect, but this " "usually happens more quickly." msgstr "" "Завершение вашего нового записи SPF может занять до 48 часов, но это, как " "правило, происходит быстрее." #: ../../content/applications/productivity/discuss/advanced/email_servers.rst:94 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 "" "Добавление нескольких записей SPF для домена может вызвать проблемы с " "доставкой почты и классификации спама. Вместо этого мы рекомендуем " "использовать только одна запись SPF, изменяя его, чтобы авторизовать Odoo." #: ../../content/applications/productivity/discuss/advanced/email_servers.rst:99 msgid "Allow DKIM" msgstr "Позвольте DKIM" #: ../../content/applications/productivity/discuss/advanced/email_servers.rst:100 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 "" "Вы должны делать то же самое, если на вашем сервере электронной почты " "включены DKIM (Domain Keys Identified Mail). В случае с Odoo Online и " "Odoo.sh, вы должны добавить DNS "odoo._domainkey" запись CNAME на " ""odoo._domainkey.odoo.com". Например, для "foo.com" они " "должны иметь запись "odoo._domainkey.foo.com", то есть CNAME со " "значением "odoo._domainkey.odoo.com"." #: ../../content/applications/productivity/discuss/advanced/email_servers.rst:108 msgid "Restriction" msgstr "" #: ../../content/applications/productivity/discuss/advanced/email_servers.rst:109 msgid "" "Please note that the port 25 is blocked for security reasons. Try using 587," " 465 or 2525." msgstr "" #: ../../content/applications/productivity/discuss/advanced/email_servers.rst:114 msgid "How to manage inbound messages" msgstr "Как управлять входящими сообщениями" #: ../../content/applications/productivity/discuss/advanced/email_servers.rst:116 msgid "Odoo relies on generic email aliases to fetch incoming messages." msgstr "" "Odoo возлагается на общие псевдонимы электронной почты, чтобы получать " "входящие сообщения." #: ../../content/applications/productivity/discuss/advanced/email_servers.rst:118 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 "" "** Ответы сообщений **, отправленных с Odoo, направляются в их оригинальный " "дискуссионный поток (и в папку "Входящие" всех его пиписникив) с " "помощью псевдонима catchall (** catchall @ **)." #: ../../content/applications/productivity/discuss/advanced/email_servers.rst:122 msgid "" "**Bounced messages** are routed to **bounce@** in order to track them in " "Odoo. This is especially used in `Odoo Email Marketing " "`__ to opt-out invalid " "recipients." msgstr "" "** Отсканированные сообщение ** направляются на отказ @, чтобы отслеживать " "их в Odoo. Это особенно используется в `Odoo Email Marketing, " " `__ чтобы отказаться от " "недействительных получателей." #: ../../content/applications/productivity/discuss/advanced/email_servers.rst:126 msgid "" "**Original messages**: Several business objects have their own alias to " "create new records in Odoo from incoming emails:" msgstr "" "** Оригинальные сообщение **: для некоторых бизнес-объектов является " "собственный псевдоним для создания новых записей в Odoo из входящих " "сообщений электронной почты:" #: ../../content/applications/productivity/discuss/advanced/email_servers.rst:129 msgid "" "Sales Channel (to create Leads or Opportunities in `Odoo CRM " "`__)," msgstr "" "Канал продаж (для создания лидов или возможностей в `Odoo CRM " " `__)," #: ../../content/applications/productivity/discuss/advanced/email_servers.rst:131 msgid "" "Support Channel (to create Tickets in `Odoo Helpdesk " "`__)," msgstr "" "Поддержка канала (для создания заявок в `Службе поддержки Odoo " " `__)," #: ../../content/applications/productivity/discuss/advanced/email_servers.rst:133 msgid "" "Projects (to create new Tasks in `Odoo Project `__)," msgstr "" "Проекты (для создания новых задач в `Проекте Odoo `__)," #: ../../content/applications/productivity/discuss/advanced/email_servers.rst:135 msgid "" "Job Positions (to create Applicants in `Odoo Recruitment " "`__)," msgstr "" "Вакансии (для создания заявок в `Рекрутинга Odoo " " `__)," #: ../../content/applications/productivity/discuss/advanced/email_servers.rst:137 msgid "etc." msgstr "и т.д." #: ../../content/applications/productivity/discuss/advanced/email_servers.rst:139 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 "" "В зависимости от вашего почтового сервера может существовать несколько " "способов получения сообщений электронной почты. Самый и наиболее " "рекомендуемый способ заключается в управлении одному адресу электронной " "почты на псевдонимы Odoo на вашем почтовом сервере." #: ../../content/applications/productivity/discuss/advanced/email_servers.rst:143 msgid "" "Create the corresponding email addresses in your mail server (catchall@, " "bounce@, sales@, etc.)." msgstr "" "Создайте соответствующие электронные адреса на своем почтовом сервере " "(catchall @, bounce @, sales @ и т.д.)." #: ../../content/applications/productivity/discuss/advanced/email_servers.rst:145 msgid "Set your domain name in the General Settings." msgstr "Установите свое доменное имя в общих настройках." #: ../../content/applications/productivity/discuss/advanced/email_servers.rst:150 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 "" "Если вы используете Odoo на собственном сервере, создайте * входной почтовый" " сервер * в Odoo для каждого псевдонима. Вы также можете это сделать в общих" " настройках. Заполните форму в соответствии с вашими настроек поставщика " "услуг электронной почты. Оставьте * действия, которые нужно выполнить * на " "входных письмах, пустыми. Когда вся информация будет заполнена, нажмите на *" " Проверка и подтверждение *." #: ../../content/applications/productivity/discuss/advanced/email_servers.rst:159 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 "" "Если вы используете Odoo Online или Odoo.sh, мы рекомендуем переадресовывать" " входящие сообщения на доменное имя Odoo, а не только использовать свой " "собственный сервер электронной почты. Таким образом вы получите входящие " "сообщения без задержки. Действительно, Odoo Online получает входящие " "сообщения внешних серверов только раз в час. Вы должны установить " "перенаправления для всех адресов электронной почты к доменному имени Odoo на" " своем сервере электронной почты (например, *catchall@mydomain.ext*, на " "*catchall@mycompany.odoo.com*)." #: ../../content/applications/productivity/discuss/advanced/email_servers.rst:169 msgid "All the aliases are customizable in Odoo." msgstr "" #: ../../content/applications/productivity/discuss/advanced/email_servers.rst:167 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 `." msgstr "" #: ../../content/applications/productivity/discuss/advanced/email_servers.rst:171 msgid "" "Then go to :menuselection:`Settings --> Technical --> Parameters --> System " "Parameters` to customize the aliases (*mail.catchall.alias* & * " "mail.bounce.alias*)." msgstr "" #: ../../content/applications/productivity/discuss/advanced/email_servers.rst:177 msgid "" "By default inbound messages are fetched every 5 minutes in Odoo on-premise. " "You can change this value in :doc:`Developer mode " "`. Go to :menuselection:`Settings --> " "Technical --> Automation --> Scheduled Actions` and look for *Mail: " "Fetchmail Service*." msgstr "" #: ../../content/applications/productivity/discuss/advanced/email_servers.rst:186 msgid "Set up different dedicated servers for transactional and mass mails" msgstr "" #: ../../content/applications/productivity/discuss/advanced/email_servers.rst:188 msgid "" "Odoo's e-mail server has the capability of sending 200 e-mails per day on " "Odoo SH Cloud Platform. However, if needed, you can use a separate Mail " "Transfer Agent (MTA) servers for transactional e-mails and mass mailings. " "Example: use Odoo's own mail server for transactional e-mails, and Sendgrid," " Amazon SES, or Mailgun for mass mailings. Another alternative is to use " "Postmark for transactional e-mails, and Amazon SES or Sendgrid for mass " "mailings." msgstr "" #: ../../content/applications/productivity/discuss/advanced/email_servers.rst:196 msgid "" "A default outgoing email server is already configured. You should not create" " an alternative one unless you want to use a specific external outgoing " "email server for technical reasons." msgstr "" #: ../../content/applications/productivity/discuss/advanced/email_servers.rst:199 msgid "" "To do this, you should first enable the :doc:`Developer mode " "` and then go to " ":menuselection:`Settings --> Technical --> Outgoing` e-mail servers. There " "you have to create two e-mail MTA server settings. One for transactional " "e-mails and one for mass mail servers. Be sure to mark the priority of " "transactional e-mail servers as low as the mass email servers." msgstr "" #: ../../content/applications/productivity/discuss/advanced/email_servers.rst:205 msgid "" "Now, go to :menuselection:`Email Marketing --> Settings` and enable " "*Dedicated Server*. With these settings, Odoo uses the server with the lower" " priority for transactional emails, and the server here selected for mass " "mails. Note that in this case, you have to set your domain's Sender Policy " "Framework (SPF) records to include both transactional and mass mail servers." " If your server resides with xxxx.odoo.com, the available options are " "Sendinblue and Mailchimp, as your e-mails would be originated from the " "xxxx.odoo.com domain." msgstr "" #: ../../content/applications/productivity/discuss/advanced/email_template.rst:3 msgid "Email Templates" msgstr "Шаблоны писем" #: ../../content/applications/productivity/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 "" #: ../../content/applications/productivity/discuss/advanced/email_template.rst:12 msgid "Enable it and understand a few concepts" msgstr "" #: ../../content/applications/productivity/discuss/advanced/email_template.rst:14 msgid "" "The :doc:`Developer mode ` must be " "activated. Then, go to :menuselection:`Settings --> Technical --> " "Templates`. A view of the existing templates is shown." msgstr "" #: ../../content/applications/productivity/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 "" #: ../../content/applications/productivity/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 "" #: ../../content/applications/productivity/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 "" #: ../../content/applications/productivity/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 "" #: ../../content/applications/productivity/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 "" #: ../../content/applications/productivity/discuss/advanced/email_template.rst:37 msgid "Writing content including placeholder expressions" msgstr "" #: ../../content/applications/productivity/discuss/advanced/email_template.rst:39 msgid "" "Under the tab *Dynamic Placeholder Generator*, look for the *Field* you " "would like to use." msgstr "" #: ../../content/applications/productivity/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 "" #: ../../content/applications/productivity/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 "" #: ../../content/applications/productivity/discuss/overview.rst:3 msgid "Overview" msgstr "Обзор" #: ../../content/applications/productivity/discuss/overview/get_started.rst:3 msgid "Get Started with Discuss" msgstr "" #: ../../content/applications/productivity/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 "" #: ../../content/applications/productivity/discuss/overview/get_started.rst:11 msgid "Choose your notifications preference" msgstr "" #: ../../content/applications/productivity/discuss/overview/get_started.rst:13 msgid "" "Access your *Preferences* and choose how you would like your notifications " "to be handled." msgstr "" #: ../../content/applications/productivity/discuss/overview/get_started.rst:21 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 "" #: ../../content/applications/productivity/discuss/overview/get_started.rst:22 msgid "Messages can then be *Marked as Todo*, *Replied*, or *Marked as Read*." msgstr "" #: ../../content/applications/productivity/discuss/overview/get_started.rst:28 msgid "" "The messages tagged as *Mark as Todo* are also shown in *Starred*, while the" " ones *Marked as Read* are moved to *History*." msgstr "" #: ../../content/applications/productivity/discuss/overview/get_started.rst:36 msgid "Start Chatting" msgstr "" #: ../../content/applications/productivity/discuss/overview/get_started.rst:38 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 "" #: ../../content/applications/productivity/discuss/overview/get_started.rst:48 msgid "" "To stop receiving desktop notifications, reset the notifications settings of" " your browser." msgstr "" #: ../../content/applications/productivity/discuss/overview/get_started.rst:50 msgid "" "To start a chat, click on *New Message* on the *Messaging Menu*, or go to " "*Discuss* and send a *Direct Message*." msgstr "" #: ../../content/applications/productivity/discuss/overview/get_started.rst:58 msgid "" "You can also create :doc:`public and private channels `." msgstr "" #: ../../content/applications/productivity/discuss/overview/get_started.rst:61 msgid "Mentions in the chat and on the Chatter" msgstr "" #: ../../content/applications/productivity/discuss/overview/get_started.rst:64 msgid "" "To mention a user within a chat or the chatter type *@user-name*; to refer " "to a channel, type *#channel-name*." msgstr "" #: ../../content/applications/productivity/discuss/overview/get_started.rst:66 msgid "" "A notification is sent to the user mentioned either to his *Inbox* or " "through email, depending on his settings." msgstr "" #: ../../content/applications/productivity/discuss/overview/get_started.rst:73 msgid "" "When a user is mentioned, the search list (list of names) suggests values " "first based on the task’s followers, 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 "" #: ../../content/applications/productivity/discuss/overview/get_started.rst:78 msgid "Chat status" msgstr "" #: ../../content/applications/productivity/discuss/overview/get_started.rst:80 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 "" #: ../../content/applications/productivity/discuss/overview/get_started.rst:84 msgid "Green = online" msgstr "" #: ../../content/applications/productivity/discuss/overview/get_started.rst:85 msgid "Orange = away" msgstr "" #: ../../content/applications/productivity/discuss/overview/get_started.rst:86 msgid "White = offline" msgstr "" #: ../../content/applications/productivity/discuss/overview/get_started.rst:87 msgid "Airplane = out of the office" msgstr "" #: ../../content/applications/productivity/discuss/overview/get_started.rst:95 #: ../../content/applications/productivity/discuss/overview/plan_activities.rst:65 msgid ":doc:`team_communication`" msgstr "" #: ../../content/applications/productivity/discuss/overview/get_started.rst:96 msgid ":doc:`../advanced/email_servers`" msgstr "" #: ../../content/applications/productivity/discuss/overview/plan_activities.rst:3 msgid "Get Organized by Planning Activities" msgstr "" #: ../../content/applications/productivity/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 "" #: ../../content/applications/productivity/discuss/overview/plan_activities.rst:10 msgid "Where do I see my schedule activities?" msgstr "" #: ../../content/applications/productivity/discuss/overview/plan_activities.rst:12 msgid "" "Access and manage your activities wherever you are in Odoo by the " "*Activities* menu." msgstr "" #: ../../content/applications/productivity/discuss/overview/plan_activities.rst:20 msgid "Plan activities" msgstr "" #: ../../content/applications/productivity/discuss/overview/plan_activities.rst:22 msgid "" "Activities can be planned and managed from the chatter by clicking on " "*Schedule activity*, or through Kanban views." msgstr "" #: ../../content/applications/productivity/discuss/overview/plan_activities.rst:31 msgid "Set your activity types" msgstr "Установите виды деятельности" #: ../../content/applications/productivity/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 "" #: ../../content/applications/productivity/discuss/overview/plan_activities.rst:42 msgid "" "If you need to create an activity type with an available calendar, make sure" " to create it with an *Action to Perform* set as *Meeting*." msgstr "" #: ../../content/applications/productivity/discuss/overview/plan_activities.rst:46 msgid "Recommend next activities" msgstr "" #: ../../content/applications/productivity/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 "" #: ../../content/applications/productivity/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 "" #: ../../content/applications/productivity/discuss/overview/plan_activities.rst:64 #: ../../content/applications/productivity/discuss/overview/team_communication.rst:115 msgid ":doc:`get_started`" msgstr "" #: ../../content/applications/productivity/discuss/overview/team_communication.rst:3 msgid "Efficiently Communicate Using Channels" msgstr "" #: ../../content/applications/productivity/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 "" #: ../../content/applications/productivity/discuss/overview/team_communication.rst:10 msgid "Public and Private channels" msgstr "" #: ../../content/applications/productivity/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 "" #: ../../content/applications/productivity/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 "" #: ../../content/applications/productivity/discuss/overview/team_communication.rst:26 msgid "Configuration options" msgstr "" #: ../../content/applications/productivity/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 "" #: ../../content/applications/productivity/discuss/overview/team_communication.rst:36 msgid "Privacy and Members" msgstr "" #: ../../content/applications/productivity/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 "" #: ../../content/applications/productivity/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 "" #: ../../content/applications/productivity/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 "" #: ../../content/applications/productivity/discuss/overview/team_communication.rst:55 msgid "Use a channel as a mailing list" msgstr "" #: ../../content/applications/productivity/discuss/overview/team_communication.rst:57 msgid "" "Choosing to *Send messages by email* configures the channel to behave as a " "mailing list." msgstr "" #: ../../content/applications/productivity/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 "" #: ../../content/applications/productivity/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 "" #: ../../content/applications/productivity/discuss/overview/team_communication.rst:67 msgid "" "Mark *Send guidelines to new subscribers* to automatically send instructions" " to newcomers." msgstr "" #: ../../content/applications/productivity/discuss/overview/team_communication.rst:73 msgid "" "Moderators can: *Accept*, *Reject*, *Discard*, *Always Allow* or *Ban* " "messages." msgstr "" #: ../../content/applications/productivity/discuss/overview/team_communication.rst:80 msgid "" "Members of a mailing channel receive messages through email regardless of " "their :doc:`notification preference `." msgstr "" #: ../../content/applications/productivity/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 "" #: ../../content/applications/productivity/discuss/overview/team_communication.rst:91 msgid "Quick search bar" msgstr "" #: ../../content/applications/productivity/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 "" #: ../../content/applications/productivity/discuss/overview/team_communication.rst:103 msgid "Finding channels" msgstr "" #: ../../content/applications/productivity/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 "" #: ../../content/applications/productivity/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 "" #: ../../content/applications/productivity/discuss/overview/team_communication.rst:116 msgid ":doc:`plan_activities`" msgstr "" #: ../../content/applications/productivity/iot.rst:4 msgid "Internet of Things (IoT)" msgstr "Интернет вещей (IoT)" #: ../../content/applications/productivity/iot/config.rst:3 msgid "Configuration" msgstr "Настройка" #: ../../content/applications/productivity/iot/config/connect.rst:3 msgid "Connect an IoT Box to your database" msgstr "Подключение IoT Box к вашей базе данных" #: ../../content/applications/productivity/iot/config/connect.rst:5 msgid "Install the Internet of Things (IoT) App on your Odoo Database." msgstr "Установите программу Интернет вещей (IoT) на базу данных Odoo." #: ../../content/applications/productivity/iot/config/connect.rst:10 msgid "Go in the IoT App and click on Connect on the IoT Boxes page." msgstr "" "Зайдите в приложение IoT и нажмите на Подключить на странице IoT Boxes." #: ../../content/applications/productivity/iot/config/connect.rst:15 msgid "Follow the steps to connect your IoT Box." msgstr "Следуйте инструкциям по подключению IoT Box." #: ../../content/applications/productivity/iot/config/connect.rst:21 msgid "Ethernet Connection" msgstr "подключение Ethernet" #: ../../content/applications/productivity/iot/config/connect.rst:23 msgid "" "Connect to the IoT Box all the devices that have to be connected with cables" " (ethernet, usb devices, etc.)." msgstr "" "Подключите к IoT Box все устройства, которые должны быть соединены кабелями " "(Ethernet, USB-устройства и т.д.)." #: ../../content/applications/productivity/iot/config/connect.rst:26 msgid "Power on the IoT Box." msgstr "Включите IoT Box." #: ../../content/applications/productivity/iot/config/connect.rst:28 msgid "" "Read the Pairing Code from a screen or a receipt printer connected to the " "IoT Box." msgstr "" #: ../../content/applications/productivity/iot/config/connect.rst:32 msgid "Input the Pairing Code and click on the Pair button." msgstr "" #: ../../content/applications/productivity/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 "" #: ../../content/applications/productivity/iot/config/connect.rst:40 msgid "WiFi Connection" msgstr "Соединение с WiFi" #: ../../content/applications/productivity/iot/config/connect.rst:42 msgid "Power on the IoT Box" msgstr "Включите IoT Box." #: ../../content/applications/productivity/iot/config/connect.rst:44 msgid "Copy the token" msgstr "Скопируйте токен" #: ../../content/applications/productivity/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 "" "Подключите WiFi до IoT Box (убедитесь, что в компьютере не подключены кабель" " Ethernet)." #: ../../content/applications/productivity/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 Box (если она не работает, " "подключитесь к IP-адреса коробки). Дайте название вашему IoT Box (не " "обязательно) и вставьте токен, а затем нажмите кнопку Далее." #: ../../content/applications/productivity/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 "" "Если вы на Runbot, не забудьте добавить -all или -base в токене (например, " "этот токен ** http: //375228-saas-11-5-iot-f3f920.runbot16.odoo.com \\ | " "4957098401 ** должен стать ** http: //375228-saas-11-5-iot-" "f3f920-all.runbot16.odoo.com \\ | 4957098401 **)." #: ../../content/applications/productivity/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 "" "Выберите сеть WiFi, которую вы хотите подключить (введите пароль, если " "таковой имеется) и нажмите кнопку Отправить. Подождите несколько секунд, " "прежде чем перенаправитися в базу данных." #: ../../content/applications/productivity/iot/config/connect.rst:72 msgid "You should now see the IoT Box." msgstr "Теперь вы можете видеть IoT Box." #: ../../content/applications/productivity/iot/config/connect.rst:78 msgid "IoT Box Schema" msgstr "Схема IoT Box" #: ../../content/applications/productivity/iot/config/flash_sdcard.rst:3 msgid "Flashing your SD Card" msgstr "Запись вашей SD карточки" #: ../../content/applications/productivity/iot/config/flash_sdcard.rst:5 msgid "" "In some case, you may need to reflash your IoT Box’s SD Card to benefit from" " our latest updates." msgstr "" "В некоторых случаях вам может понадобиться перепрошивка вашей SD карточки " "IoT Box, чтобы воспользоваться нашими последними обновлениями." #: ../../content/applications/productivity/iot/config/flash_sdcard.rst:9 msgid "Upgrade from the IoT Box homepage" msgstr "" #: ../../content/applications/productivity/iot/config/flash_sdcard.rst:11 msgid "" "Go to the IoT Box homepage, click on *Update*, next to the version number. " "If a new version of the IoT Box image is available, you will see a *Upgrade " "to ___* button a the bottom of the page, the IoT Box will then flash itself " "to the new version of the IoT Box. All of your configurations will be saved." msgstr "" #: ../../content/applications/productivity/iot/config/flash_sdcard.rst:18 msgid "" "This process can take more than 30 minutes. Do not turn off or unplug the " "IoT Box as it would leave it in an inconsistent state." msgstr "" #: ../../content/applications/productivity/iot/config/flash_sdcard.rst:25 msgid "Upgrade with Etcher" msgstr "" #: ../../content/applications/productivity/iot/config/flash_sdcard.rst:27 msgid "" "Go to Balena’s website and download `Etcher `__. " "It’s a free and open-source utility used for burning image files. Install " "and launch it. Download the latest image from `nightly " "`__." msgstr "" #: ../../content/applications/productivity/iot/config/flash_sdcard.rst:32 msgid "" "Then, open *Etcher* and select *Flash from file*, find the image you just " "downloaded. Insert the IoT Box SD card into your computer and select it. " "Click on *Flash* and wait for the process to finish." msgstr "" #: ../../content/applications/productivity/iot/config/pos.rst:3 msgid "Use the IoT Box for the PoS" msgstr "Применение IoT Box для точки продаж" #: ../../content/applications/productivity/iot/config/pos.rst:9 msgid "Prerequisites" msgstr "предпосылки" #: ../../content/applications/productivity/iot/config/pos.rst:11 msgid "Before starting, make sure you have the following:" msgstr "Прежде чем начать, убедитесь, что у вас есть:" #: ../../content/applications/productivity/iot/config/pos.rst:13 msgid "An IoT Box, with its power adapter." msgstr "" #: ../../content/applications/productivity/iot/config/pos.rst:15 msgid "A computer or tablet with an up-to-date web browser" msgstr "Компьютер или планшет с современным веб-браузером" #: ../../content/applications/productivity/iot/config/pos.rst:17 msgid "" "A running SaaS or Odoo instance with the Point of Sale and IoT apps " "installed" msgstr "" "Запущена версия SaaS или Odoo с установленными программами Точки продаж и " "IoT" #: ../../content/applications/productivity/iot/config/pos.rst:20 msgid "A local network setup with DHCP (this is the default setting)" msgstr "Настройка локальной сети с помощью DHCP (это настройки по умолчанию)" #: ../../content/applications/productivity/iot/config/pos.rst:22 msgid "An RJ45 Ethernet Cable (optional, WiFi is built in)" msgstr "Кабель RJ45 Ethernet (необязательно, встроенный WiFi)" #: ../../content/applications/productivity/iot/config/pos.rst:24 msgid "" "Any of the supported hardware (receipt printer, barcode scanner, cash " "drawer, payment terminal, scale, customer display, etc.). The list of " "supported hardware can be found on the `POS Hardware page " "`__" msgstr "" #: ../../content/applications/productivity/iot/config/pos.rst:30 msgid "Set Up" msgstr "установите" #: ../../content/applications/productivity/iot/config/pos.rst:32 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 `." msgstr "" #: ../../content/applications/productivity/iot/config/pos.rst:36 msgid "Then, you have to connect the peripheral devices to your IoT Box." msgstr "Затем, вы должны подключить периферийные устройства к вашему IoT Box." #: ../../content/applications/productivity/iot/config/pos.rst:38 msgid "" "**Printer**: Connect a supported receipt printer to a USB port or to the " "network and power it on." msgstr "" #: ../../content/applications/productivity/iot/config/pos.rst:41 msgid "" "**Cash drawer**: The cash drawer should be connected to the printer with an " "RJ25 cable." msgstr "" "** Кассовая ящик **: кассовая ящик должен быть подключена к принтеру с " "помощью кабеля RJ25." #: ../../content/applications/productivity/iot/config/pos.rst:44 msgid "" "**Barcode scanner**: Connect your barcode scanner. In order for your barcode" " scanner to be compatible it must end barcodes with an Enter character " "(keycode 28). This is most likely the default configuration of your barcode " "scanner." msgstr "" #: ../../content/applications/productivity/iot/config/pos.rst:49 msgid "**Scale**: Connect your scale and power it on." msgstr "** Весы **: подключите веса и включите их." #: ../../content/applications/productivity/iot/config/pos.rst:51 msgid "" "**Customer Display**: Connect a monitor to the IoT Box using an HDMI cable. " "You can also access the Customer Display from any other computer by " "accessing the IoT Box homepage and clicking on the *POS Display* button." msgstr "" #: ../../content/applications/productivity/iot/config/pos.rst:56 msgid "" "**Payment terminal**: The connection process depends on the terminal, please" " refer to the :doc:`payment terminals documentation " "`." msgstr "" #: ../../content/applications/productivity/iot/config/pos.rst:60 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 *IoT Box* and" " select the devices you want to use in this Point of Sale. Save the changes." msgstr "" #: ../../content/applications/productivity/iot/config/pos.rst:68 msgid "Set up is done, you can launch a new PoS Session." msgstr "Настройка завершена, вы можете запустить новую сессию Точки продаж." #: ../../content/applications/productivity/iot/config/troubleshooting.rst:3 msgid "Troubleshooting" msgstr "Решение проблем" #: ../../content/applications/productivity/iot/config/troubleshooting.rst:6 msgid "IoT Box Connection" msgstr "" #: ../../content/applications/productivity/iot/config/troubleshooting.rst:9 msgid "I can't find the pairing code to connect my IoT Box" msgstr "" #: ../../content/applications/productivity/iot/config/troubleshooting.rst:11 msgid "" "The pairing code should be printed on receipt printers connected to the IoT " "Box and should also be displayed on connected monitors." msgstr "" #: ../../content/applications/productivity/iot/config/troubleshooting.rst:14 msgid "The pairing code doesn't show under the following circumstances:" msgstr "" #: ../../content/applications/productivity/iot/config/troubleshooting.rst:16 msgid "The IoT Box is already connected to an Odoo database;" msgstr "" #: ../../content/applications/productivity/iot/config/troubleshooting.rst:18 msgid "The IoT Box is not connected to the Internet;" msgstr "" #: ../../content/applications/productivity/iot/config/troubleshooting.rst:20 msgid "" "The code is only valid for 5 minutes after the IoT Box has started. It's " "automatically removed from connected displays when this delay has expired;" msgstr "" #: ../../content/applications/productivity/iot/config/troubleshooting.rst:23 msgid "" "The version of the IoT Box image is too old. It should use version 20.06 or " "more recent. 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 (see " ":doc:`Flashing your SD Card `)" msgstr "" #: ../../content/applications/productivity/iot/config/troubleshooting.rst:28 msgid "" "If you are not in any of the cases listed above, make sure that the IoT Box " "has correctly started, by checking that a fixed green LED is showing next to" " the micro-USB port." msgstr "" #: ../../content/applications/productivity/iot/config/troubleshooting.rst:33 msgid "I've connected my IoT Box but it's not showing in my database" msgstr "" #: ../../content/applications/productivity/iot/config/troubleshooting.rst:35 msgid "" "When you connect an IoT Box to a database, the IoT Box might restart, if " "that is the case, it might take up to one minute before appearing in your " "database. If after some time the IoT is still not showing, make sure that " "your database can be reached from the IoT Box and that your server doesn't " "use a multi-database environment." msgstr "" #: ../../content/applications/productivity/iot/config/troubleshooting.rst:42 msgid "My IoT Box is connected to my database, but cannot be reached" msgstr "" #: ../../content/applications/productivity/iot/config/troubleshooting.rst:44 msgid "" "Make sure that the IoT Box and the device running the browser are located on" " the same network as the IoT Box cannot be reached from outside the local " "network." msgstr "" #: ../../content/applications/productivity/iot/config/troubleshooting.rst:49 msgid "Printer" msgstr "Принтер" #: ../../content/applications/productivity/iot/config/troubleshooting.rst:52 msgid "My printer is not detected" msgstr "" #: ../../content/applications/productivity/iot/config/troubleshooting.rst:54 msgid "" "If one of your printers doesn't show up in your devices list, go to the IoT " "Box homepage and make sure that it is listed under *Printers*." msgstr "" #: ../../content/applications/productivity/iot/config/troubleshooting.rst:60 msgid "" "If your printer is not present on the IoT Box homepage, hit *Printers " "Server*, go to the *Administration* tab and click on *Add Printer*. If you " "can't find your printer in the list, it's probably not connected properly." msgstr "" #: ../../content/applications/productivity/iot/config/troubleshooting.rst:66 msgid "My printer outputs random text" msgstr "" #: ../../content/applications/productivity/iot/config/troubleshooting.rst:68 msgid "" "For most printers, the correct driver should be automatically detected and " "selected. However, in some cases, the automatic detection mechanism might " "not be enough, and if no driver is found the printer might print random " "characters." msgstr "" #: ../../content/applications/productivity/iot/config/troubleshooting.rst:73 msgid "" "The solution is to manually select the corresponding driver. On the IoT Box " "homepage, click on *Printers Server*, go to the *Printers* tab and select " "the printer in the list. In the Administration dropdown, click on *Modify " "Printer*. Follow the steps and select the Make and Model corresponding to " "your printer." msgstr "" #: ../../content/applications/productivity/iot/config/troubleshooting.rst:83 msgid "" "Epson and Star receipt printers and Zebra label printers do not need a " "driver to work. Make sure that no driver is selected for those printers." msgstr "" #: ../../content/applications/productivity/iot/config/troubleshooting.rst:88 msgid "My Zebra Printer doesn't print anything" msgstr "" #: ../../content/applications/productivity/iot/config/troubleshooting.rst:90 msgid "" "Zebra printers are quite sensitive to the format of the ZPL code that is " "printed. If nothing comes out of the printer or blank labels are printed, " "try changing the format of the report that is sent to the printer by " "accessing :menuselection:`Settings ~~> Technical ~~> Views` in developer " "mode and look for the corresponding template." msgstr "" #: ../../content/applications/productivity/iot/config/troubleshooting.rst:97 msgid "Barcode Scanner" msgstr "Сканер штрих-кода" #: ../../content/applications/productivity/iot/config/troubleshooting.rst:100 msgid "The characters read by the barcode scanner don't match the barcode" msgstr "" #: ../../content/applications/productivity/iot/config/troubleshooting.rst:102 msgid "" "By default, we assume that your barcode scanner is configured in US QWERTY. " "This is the default configuration of most barcode readers. If your barcode " "scanner uses a different layout, please go to the form view of your device " "and select the correct one." msgstr "" #: ../../content/applications/productivity/iot/config/troubleshooting.rst:108 msgid "Nothing happens when a barcode is scanned" msgstr "" #: ../../content/applications/productivity/iot/config/troubleshooting.rst:110 msgid "" "Make sure that the correct device is selected in your Point of Sale " "configuration and that your barcode is configured to send an ENTER character" " (keycode 28) at the end of every barcode." msgstr "" #: ../../content/applications/productivity/iot/config/troubleshooting.rst:115 msgid "The barcode scanner is detected as a keyboard" msgstr "" #: ../../content/applications/productivity/iot/config/troubleshooting.rst:117 msgid "" "Some poorly built barcode scanners do not advertise themselves as barcode " "scanners but as a USB keyboard instead, and will not be recognized by the " "IoT Box." msgstr "" #: ../../content/applications/productivity/iot/config/troubleshooting.rst:121 msgid "" "You can manually change the device type by going to its form view and " "activating the *Is scanner* option." msgstr "" #: ../../content/applications/productivity/iot/config/troubleshooting.rst:128 msgid "Cashdrawer" msgstr "Денежный ящик" #: ../../content/applications/productivity/iot/config/troubleshooting.rst:131 msgid "The cashdrawer does not open" msgstr "Наличный расчет не открывается" #: ../../content/applications/productivity/iot/config/troubleshooting.rst:133 msgid "" "The cashdrawer should be connected to the printer and the *Cashdrawer* " "checkbox should be ticked in the POS configuration." msgstr "" #: ../../content/applications/productivity/iot/devices.rst:3 msgid "Devices" msgstr "Устройства" #: ../../content/applications/productivity/iot/devices/camera.rst:3 msgid "Connect a Camera" msgstr "Подключите камеру" #: ../../content/applications/productivity/iot/devices/camera.rst:5 msgid "" "When using your *IoT Box* in Odoo, you could need to use a camera. As it can" " be done in a few steps, this device is really easy to configure. Then, you " "can use it in your manufacturing process and link it to a control point. " "Doing so will allow you to take pictures when you reach the chosen quality " "control point." msgstr "" "При использовании * IoT Box * в Odoo, вам может потребоваться использование " "камеры. Это можно сделать в несколько шагов, ведь это устройство легкий в " "настройке. Затем вы можете использовать его в вашем производстве и " "объединять с пунктами контроля. Это позволит вам фотографировать в тот " "момент, когда вы достигаете пункта контроля качества." #: ../../content/applications/productivity/iot/devices/camera.rst:12 #: ../../content/applications/productivity/iot/devices/footswitch.rst:13 #: ../../content/applications/productivity/iot/devices/printer.rst:11 #: ../../content/applications/productivity/iot/devices/scale.rst:10 msgid "Connection" msgstr "подключение" #: ../../content/applications/productivity/iot/devices/camera.rst:14 msgid "" "To connect the camera to the *IoT Box*, simply connect the two by cable." msgstr "" #: ../../content/applications/productivity/iot/devices/camera.rst:17 msgid "" "If your camera is a `*supported one* `__, there is no need to set up anything as it will be detected as " "soon as it is connected." msgstr "" "Если ваша камера `* поддерживается * `__, тогда не нужно ничего устанавливать, поскольку она будет " "взначено, как только она будет подключена." #: ../../content/applications/productivity/iot/devices/camera.rst:25 msgid "Link a Camera to a Quality Control Point" msgstr "Объедините камеру с пунктом контроля качества" #: ../../content/applications/productivity/iot/devices/camera.rst:28 #: ../../content/applications/productivity/iot/devices/measurement_tool.rst:34 msgid "With the Manufacturing app" msgstr "С модулем производство" #: ../../content/applications/productivity/iot/devices/camera.rst:30 msgid "" "In your *Quality app*, you can setup the device on a *Quality Control " "Point*. Go to the *Control Points* menu, under *Quality Control* and open " "the control point you want to link with the camera." msgstr "" "В вашем * модули Качества * вы можете установить прибор на * Пункт контроля " "качества *. Перейдите в меню * Пункты контроля * под Контроль качества * и " "откройте пукт контроля, который вы хотите соединить с камерой." #: ../../content/applications/productivity/iot/devices/camera.rst:34 msgid "" "Now, you can edit the control point and select the device from the dropdown " "list. Now, hit save." msgstr "" "Теперь вы можете редактировать пункт контроля и выбирать прибор с " "выпадающего списка. Теперь сохраните." #: ../../content/applications/productivity/iot/devices/camera.rst:40 msgid "" "Then, your camera can be used with the picked *Control Point*. During the " "manufacturing process, reaching the *Quality Control Point* you chose before" " will allow you to take a picture." msgstr "" "Затем вашу камеру можно использовать с выбранным * Пунктом контроля *. В " "течение процесса производства, достигнув * Пункт контроля качества *, " "который вы выбирали, перед тем, как вам будет разрешено сделать фото." #: ../../content/applications/productivity/iot/devices/footswitch.rst:3 msgid "Connect a Footswitch" msgstr "Подключите нежный переключатель" #: ../../content/applications/productivity/iot/devices/footswitch.rst:5 msgid "" "When working, it is always better to have your two hands available. Using " "Odoo’s *IoT Box* and a footswitch will allow it." msgstr "" "Во время работы всегда лучше иметь обе руки свободными. Используя * IoT Box " "* Odoo и педаль, вы сможете этого достичь." #: ../../content/applications/productivity/iot/devices/footswitch.rst:8 msgid "" "In fact, you will be able to go from one screen to another and perform " "actions by using your foot and the footswitch. Really convenient, it can be " "configured in a few steps." msgstr "" #: ../../content/applications/productivity/iot/devices/footswitch.rst:15 msgid "" "Connecting the footswitch to the *IoT Box* is easy, you just have to connect" " the two by cable." msgstr "" #: ../../content/applications/productivity/iot/devices/footswitch.rst:18 msgid "" "If your footswitch is a `supported one `__, there is no need to set up anything since it will be " "automatically detected when connected." msgstr "" "Если ваша педаль `поддерживается " "`__, не нужно ничего устанавливать, как только она будет автоматически " "определена после подключения." #: ../../content/applications/productivity/iot/devices/footswitch.rst:26 msgid "Link a Footswitch to a Workcenter" msgstr "Соедините педаль с рабочим центром" #: ../../content/applications/productivity/iot/devices/footswitch.rst:28 msgid "" "To link the footswitch to an action, it needs to be configured on a " "workcenter. Go to the workcenter you want to use the footswitch in and add " "the device in the *IoT Triggers* tab. Then, you can link it to an action and" " also add a key to trigger it." msgstr "" "Чтобы соединить педаль с действием, необходимо настроить педаль в рабочем " "центре. Перейдите в рабочий центр, в котором вы хотите использовать педаль и" " добавьте устройство на вкладке * Запуски IoT *. Затем вы сможете соединить " "ее с действием, а также добавить ключ для ее запуска." #: ../../content/applications/productivity/iot/devices/footswitch.rst:36 msgid "" "Note that the one that is first in the list will be chosen. So, the order " "matters! In the picture above, using the footswitch will, for example, " "automatically skip the current part of the process you work on." msgstr "" "Запишите, что из списка будут выбраны первое устройство. Поэтому порядок " "имеет значение! Как показано на картинке ниже, используя педаль, будет " "автоматически пропущен текущую часть процесса, с которой вы работаете." #: ../../content/applications/productivity/iot/devices/footswitch.rst:41 msgid "" "When you are on the work order screen, a status button indicates if you are " "correctly connected to the footswitch." msgstr "" "Когда вы на форме рабочего заказ, кнопка статуса указывает, вы правильно " "подключили педаль." #: ../../content/applications/productivity/iot/devices/measurement_tool.rst:3 msgid "Connect a Measurement Tool" msgstr "Подключите инструмент измерения" #: ../../content/applications/productivity/iot/devices/measurement_tool.rst:5 msgid "" "With Odoo’s *IoT Box*, it is possible to connect measurement tools to your " "database. Find the list of supported devices here: `Supported devices " "`__,." msgstr "" "С * IoT Box * Odoo возможно подключить инструменты измерения к вашей базе " "данных. Найдите список поддерживаемых устройств здесь: `Поддерживаемые " "устройства `__ ,." #: ../../content/applications/productivity/iot/devices/measurement_tool.rst:10 msgid "Connect in USB" msgstr "Подключите через USB" #: ../../content/applications/productivity/iot/devices/measurement_tool.rst:12 msgid "" "To add a device connected by USB, just plug the USB cable in the *IoT Box*, " "and the device should appear in your Odoo database." msgstr "" #: ../../content/applications/productivity/iot/devices/measurement_tool.rst:19 msgid "Connect in Bluetooth" msgstr "Подключитесь через Bluetooth" #: ../../content/applications/productivity/iot/devices/measurement_tool.rst:21 msgid "" "Activate the Bluetooth on your device (see your device manual for further " "explanation) and the IoT Box will automatically try to connect to the " "device." msgstr "" "Активируйте Bluetooth на вашем устройстве (см. Руководство по устройству для" " дальнейшего объяснения) и IoT Box автоматически попытается подключиться к " "устройствам." #: ../../content/applications/productivity/iot/devices/measurement_tool.rst:25 msgid "Here is an example of what it should look like:" msgstr "Вот пример, как это должно выглядеть:" #: ../../content/applications/productivity/iot/devices/measurement_tool.rst:31 msgid "Link a measurement tool to a quality control point" msgstr "Соедините инструмент измерения пункту контроля качества" #: ../../content/applications/productivity/iot/devices/measurement_tool.rst:36 msgid "" "In your *Quality app*, you can setup a device on your *Quality Control " "Points*. To do so, go to the *Control Points* menu, under *Quality Control* " "and open the control point to which you want to assign a measurement tool." msgstr "" "В вашем * модули Качества *, вы можете установить устройство в ваши * Пункты" " контроля качества *. Чтобы сделать это, перейдите в меню * Пункты контроля " "* под * Контролем качества * и откройте пункт контроля, в который вы хотите " "назначить инструмент измерения." #: ../../content/applications/productivity/iot/devices/measurement_tool.rst:41 msgid "" "Now, you can edit the control point and choose the device from the dropdown " "list. Then, hit save." msgstr "" "Теперь вы можете редактировать пункт контроля и выбирать устройство из " "выпадающего списка. Сохраните настройки." #: ../../content/applications/productivity/iot/devices/measurement_tool.rst:47 msgid "" "Now, your measurement tool is linked to the chosen *Control Point*. The " "value, which needs to be changed manually, will be automatically updated " "while the tool is being used." msgstr "" "Теперь ваш инструмент измерения соединены с избранным * Пунктом контроля *. " "Значение, которое требует изменений вручную, автоматически обновлен, пока " "используется инструмент." #: ../../content/applications/productivity/iot/devices/printer.rst:3 msgid "Connect a Printer" msgstr "Подключите принтер" #: ../../content/applications/productivity/iot/devices/printer.rst:5 msgid "" "When using your *IoT Box* in Odoo, you could need to use a printer. Doing so" " is easy and convenient as it can be done in a few steps. Then, you can use " "it to print receipts, orders or even reports in different Odoo apps." msgstr "" "Используя * IoT Box * в Odoo, вам может понадобиться принтер. Сделать это " "можно легко и просто всего за несколько шагов. ПТМ вы сможете использовать " "принтер для печати чеков, заказов или даже отчетов в различных модулях Odoo." #: ../../content/applications/productivity/iot/devices/printer.rst:13 msgid "" "The IoT Box supports printers connected through USB, network or Bluetooth. " "`Supported printers `__ will be " "detected automatically and will appear in the *Devices* list of your IoT " "app." msgstr "" #: ../../content/applications/productivity/iot/devices/printer.rst:18 msgid "The printer can take up to two minutes to appear in your devices list." msgstr "Принтер может появляться в списке устройств в течение двух минут." #: ../../content/applications/productivity/iot/devices/printer.rst:24 msgid "Link the Printer" msgstr "Подключите принтер" #: ../../content/applications/productivity/iot/devices/printer.rst:27 msgid "To Work Orders" msgstr "К рабочим заказов" #: ../../content/applications/productivity/iot/devices/printer.rst:29 msgid "" "You can link *Work Orders* to printers via a *Quality Control Point* to " "print labels for manufactured products." msgstr "" "Вы можете соединить * Рабочие заказ * с принтерами через * Пункт контроля " "качества * для печати этикеток изготовленных товаров." #: ../../content/applications/productivity/iot/devices/printer.rst:32 msgid "" "To do so, you need to create a *Quality Control Point* from the *Quality* " "app. Then, you can select the correct manufacturing operation and the work " "order operation. In type, choose *Print Label* and hit save." msgstr "" "Для этого вам необходимо создать * Пункт контроля качества * из модуля * " "Качество *. Затем вы можете выбрать корректировать производственную операцию" " и операцию рабочего заказ. В типе выберите * Печать этикет * и сохраните." #: ../../content/applications/productivity/iot/devices/printer.rst:40 msgid "" "Now, each time you reach the quality control point for the chosen product, a" " *Print Label* button will appear." msgstr "" "Теперь каждый раз, когда вы достигаете пункта контроля качества для " "выбранного товара, будет появляться кнопка * Печать этикетки *." #: ../../content/applications/productivity/iot/devices/printer.rst:47 msgid "To Reports" msgstr "отчетам" #: ../../content/applications/productivity/iot/devices/printer.rst:49 msgid "" "You can also link a type of report to a certain printer. In the *IoT* app, " "go to the *Devices* menu and select the printer you want to set up." msgstr "" "Вы также можете соединить тип отчета по определенным принтером. В модуле * " "IoT * перейдите в меню * Устройства * и выберите принтер, который вы хотите " "установить." #: ../../content/applications/productivity/iot/devices/printer.rst:56 msgid "Now, go to the *Printer Reports* tab." msgstr "Теперь перейдите на вкладку * Отчеты принтера *." #: ../../content/applications/productivity/iot/devices/printer.rst:61 msgid "" "Hit edit and then, click on *Add a line*. In the window that shows up, check" " all the types of reports that should be linked to this printer. Click on " "select and save." msgstr "" "Нажмите редактировать и на * Добавить строку *. В открывшемся окне, " "проверьте все типы отчетов, которые будут связаны с этим принтером. Нажмите " "выбрать и сохранить." #: ../../content/applications/productivity/iot/devices/printer.rst:68 msgid "" "Now, each time you click on *Print* in the control panel, instead of " "downloading a PDF, it will send it to the selected printer and automatically" " print it." msgstr "" "Теперь каждый раз, когда вы нажимаете на * Печать * в контрольной панели, " "вместо загрузки PDF, система пришлет файл на выбранный принтер и " "автоматически распечатает его." #: ../../content/applications/productivity/iot/devices/printer.rst:73 msgid "Print Receipts from the PoS" msgstr "Печатайте чеки с Точки продаж" #: ../../content/applications/productivity/iot/devices/printer.rst:75 msgid "" "You can link a printer to your *Point of Sale* app so you can print receipts" " directly from your *PoS*." msgstr "" "Вы можете соединить принтер с вашим модулем * Точка продажи *, поэтому вы " "можете печатать чеки прямо с вашего * Точки продаж *." #: ../../content/applications/productivity/iot/devices/printer.rst:78 msgid "" "Doing so is really easy. Go to your *Point of Sale* app and open your *Point" " of Sale* settings, under *Configuration*. There, click on *Edit* and check " "the *IoT Box* feature. Then, choose your *Receipt Printer* from the " "dropdown." msgstr "" #: ../../content/applications/productivity/iot/devices/printer.rst:86 msgid "" "Now, you will be able to print different kinds of tickets from your *POS*: " "**receipts**, **sale details** and **bills**." msgstr "" #: ../../content/applications/productivity/iot/devices/printer.rst:89 msgid "" "Receipts are printed once the order is validated. The process is automated " "when you enable the feature in your *PoS* configuration." msgstr "" #: ../../content/applications/productivity/iot/devices/printer.rst:92 msgid "" "Sales details can be printed by clicking on the printer icon on the navbar " "at the top of the *PoS*. It will print the details of the sales of the " "current day." msgstr "" "Детали продаже можно распечатать, когда вы нажимаете на иконку печати на " "верхней панели * Точки продаж *. Она распечатает детали продажи текущего " "дня." #: ../../content/applications/productivity/iot/devices/printer.rst:99 msgid "" "As for the bill, it is only available in restaurant mode. In your restaurant" " settings, activate *Print Bills* and a *Bill* button will appear in the " "left panel of the *PoS*." msgstr "" #: ../../content/applications/productivity/iot/devices/printer.rst:107 msgid "Print Orders in the kitchen" msgstr "Печатайте заказ на кухне" #: ../../content/applications/productivity/iot/devices/printer.rst:109 msgid "In restaurant mode, you can send order tickets to the kitchen." msgstr "В режиме ресторана вы можете присылать квитанции заказ на кухню." #: ../../content/applications/productivity/iot/devices/printer.rst:111 msgid "" "To do so, go to the *PoS* app and open your *PoS* settings. Then, tick " "*Order Printer*." msgstr "" "Для этого перейдите в модуль * Точки продаж * и откройте ваши настройки * " "Точки продаж *. Отметив * Принтеры заказов *." #: ../../content/applications/productivity/iot/devices/printer.rst:117 msgid "" "Now, go to the *Printers* menu. Hit create, select the printer from the " "dropdown and, in the *Printer Product Categories* field, choose all the " "categories of products that should be printed on this printer." msgstr "" #: ../../content/applications/productivity/iot/devices/printer.rst:124 msgid "" "In the *PoS*, when you add or remove a product from one of the selected " "categories, the button *Order* will be green. If you click on it, the IoT " "Box will print a receipt on the corresponding printer." msgstr "" #: ../../content/applications/productivity/iot/devices/scale.rst:3 msgid "Connect a Scale" msgstr "" #: ../../content/applications/productivity/iot/devices/scale.rst:5 msgid "" "When using your **IoT Box** in Odoo, you could need to use a scale. Doing so" " is easy and convenient as it can be done in a few steps. Then, you can use " "it in your **Point of Sale app** to weigh your products, which is helpful if" " their price are based on it." msgstr "" #: ../../content/applications/productivity/iot/devices/scale.rst:12 msgid "To link the scale to the **IoT Box**, connect them with a cable." msgstr "" #: ../../content/applications/productivity/iot/devices/scale.rst:15 msgid "In some cases, a serial to USB adapter may be needed." msgstr "В некоторых случаях может понадобиться USB-адаптер." #: ../../content/applications/productivity/iot/devices/scale.rst:17 msgid "" "If your scale is `compatibale with Odoo IoT Box `_, there is no need to set up anything because it will be " "automatically detected as soon as it is connected." msgstr "" #: ../../content/applications/productivity/iot/devices/scale.rst:24 msgid "" "You may need to restart the box and download your scales’ drivers from the " "box in some cases. To do so, go to the *IoT Box Home Page* and click on " "*drivers list*. Then, click on load drivers." msgstr "" #: ../../content/applications/productivity/iot/devices/scale.rst:32 msgid "Use a Scale in Point of Sale" msgstr "" #: ../../content/applications/productivity/iot/devices/scale.rst:34 msgid "" "To use the scale in your *Point of Sale* app, go to :menuselection:`Point of" " Sale --> Configuration --> Point of Sale`, open the one you want to " "configure, then click on *Edit* and enable the *IoT Box* feature." msgstr "" #: ../../content/applications/productivity/iot/devices/scale.rst:42 msgid "" "Now, choose the *IoT Box* in the dropdown menu and check the *Electronic " "Scale* option. Then, you hit save." msgstr "" #: ../../content/applications/productivity/iot/devices/scale.rst:49 msgid "" "The scale is now available in all your *PoS* sessions. Then, if a product " "has a price per weight set, clicking on it on the *PoS* screen opens the " "scale screen, where the cashier can weigh the product and add the correct " "price to the cart." msgstr "" #: ../../content/applications/productivity/studio.rst:3 msgid "Studio" msgstr "Студия" #: ../../content/applications/productivity/studio/concepts.rst:3 msgid "Concepts" msgstr "понятие" #: ../../content/applications/productivity/studio/concepts/understanding_automated_actions.rst:3 msgid "Understanding Automated Actions" msgstr "" #: ../../content/applications/productivity/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 "" #: ../../content/applications/productivity/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 "" #: ../../content/applications/productivity/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 "" #: ../../content/applications/productivity/studio/concepts/understanding_automated_actions.rst:18 msgid "" "The first step is to choose the :doc:`Model ` on " "which the action is applied." msgstr "" #: ../../content/applications/productivity/studio/concepts/understanding_automated_actions.rst:19 msgid "" "The **Trigger** field defines the event that causes the automated action to " "happen:" msgstr "" #: ../../content/applications/productivity/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 "" #: ../../content/applications/productivity/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 "" #: ../../content/applications/productivity/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 "" #: ../../content/applications/productivity/studio/concepts/understanding_automated_actions.rst:25 msgid "*On Deletion*: on the removal of a record under the condition set." msgstr "" #: ../../content/applications/productivity/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 "" #: ../../content/applications/productivity/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 "" #: ../../content/applications/productivity/studio/concepts/understanding_automated_actions.rst:34 msgid "For every Trigger option, **conditions** can be applied, such as:" msgstr "" #: ../../content/applications/productivity/studio/concepts/understanding_automated_actions.rst:36 msgid "" "*Before Update Domain*: if designated, this condition must be satisfied " "before the record is updated." msgstr "" #: ../../content/applications/productivity/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 "" #: ../../content/applications/productivity/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 "" #: ../../content/applications/productivity/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 "" #: ../../content/applications/productivity/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 "" #: ../../content/applications/productivity/studio/concepts/understanding_automated_actions.rst:47 msgid "*Create New Record*: a new record with new values is created." msgstr "" #: ../../content/applications/productivity/studio/concepts/understanding_automated_actions.rst:48 msgid "*Update a Record*: updates the record that triggered the action." msgstr "" #: ../../content/applications/productivity/studio/concepts/understanding_automated_actions.rst:49 msgid "" "*Execute several actions*: defines an action that triggers other server " "actions." msgstr "" #: ../../content/applications/productivity/studio/concepts/understanding_automated_actions.rst:50 msgid "" "*Send Email*: an automatic :doc:`email " "<../../discuss/advanced/email_template>` is sent." msgstr "" #: ../../content/applications/productivity/studio/concepts/understanding_automated_actions.rst:51 msgid "*Add Followers*: followers are notified of changes in the task." msgstr "" #: ../../content/applications/productivity/studio/concepts/understanding_automated_actions.rst:52 msgid "" "*Create Next Activity*: creates an activity such as: *Call*, *Email*, " "*Reminder*." msgstr "" #: ../../content/applications/productivity/studio/concepts/understanding_automated_actions.rst:53 msgid "" "*Send SMS Text Message*: sends an :doc:`SMS " "`." msgstr "" #: ../../content/applications/productivity/studio/concepts/understanding_automated_actions.rst:56 msgid "Example" msgstr "пример" #: ../../content/applications/productivity/studio/concepts/understanding_automated_actions.rst:58 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 "" #: ../../content/applications/productivity/studio/concepts/understanding_automated_actions.rst:65 msgid "The user creates the record without an email address set." msgstr "" #: ../../content/applications/productivity/studio/concepts/understanding_automated_actions.rst:66 msgid "The user updates the record defining an email address." msgstr "" #: ../../content/applications/productivity/studio/concepts/understanding_automated_actions.rst:67 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 "" #: ../../content/applications/productivity/studio/concepts/understanding_automated_actions.rst:69 msgid "" "If true, it checks if the record matches the *Before Update Domain* (for the" " example: *email is not set*)." msgstr "" #: ../../content/applications/productivity/studio/concepts/understanding_automated_actions.rst:71 msgid "" "If true, it checks (*after the update*) whether the record matches the " "*Apply on* domain (for the example: *email is set*)." msgstr "" #: ../../content/applications/productivity/studio/concepts/understanding_automated_actions.rst:73 msgid "If true, the chosen *Action To Do* is performed on the record." msgstr "" #: ../../content/applications/productivity/studio/concepts/understanding_automated_actions.rst:76 msgid ":doc:`understanding_general`" msgstr "" #: ../../content/applications/productivity/studio/concepts/understanding_automated_actions.rst:77 msgid ":doc:`../use_cases/automated_actions`" msgstr "" #: ../../content/applications/productivity/studio/concepts/understanding_general.rst:3 msgid "Understanding General Concepts" msgstr "" #: ../../content/applications/productivity/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 "" #: ../../content/applications/productivity/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 "" #: ../../content/applications/productivity/studio/concepts/understanding_general.rst:15 msgid "Getting started" msgstr "Начиная работу" #: ../../content/applications/productivity/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 "" #: ../../content/applications/productivity/studio/concepts/understanding_general.rst:22 msgid "What is a Module?" msgstr "" #: ../../content/applications/productivity/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 "" #: ../../content/applications/productivity/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 "" #: ../../content/applications/productivity/studio/concepts/understanding_general.rst:38 msgid "What is a Model (also called Object)?" msgstr "" #: ../../content/applications/productivity/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 "" #: ../../content/applications/productivity/studio/concepts/understanding_general.rst:45 msgid "What are Fields?" msgstr "" #: ../../content/applications/productivity/studio/concepts/understanding_general.rst:47 msgid "" "**Fields** compose models. It is where a record (a piece of data) is " "registered." msgstr "" #: ../../content/applications/productivity/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 "" #: ../../content/applications/productivity/studio/concepts/understanding_general.rst:50 msgid "" "There are 2 main types of fields in Odoo: *basic (or scalar) fields* and " "*relational fields*." msgstr "" #: ../../content/applications/productivity/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 "" #: ../../content/applications/productivity/studio/concepts/understanding_general.rst:56 msgid "Relational Fields in detail" msgstr "" #: ../../content/applications/productivity/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 "" #: ../../content/applications/productivity/studio/concepts/understanding_general.rst:60 msgid "" "In Odoo, relational field types are: *One2many*, *Many2one*, *Many2many*." msgstr "" #: ../../content/applications/productivity/studio/concepts/understanding_general.rst:66 msgid "" "An **One2many** field is a *one-way* direction of selecting *multiple* " "records from a table." msgstr "" #: ../../content/applications/productivity/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 "" #: ../../content/applications/productivity/studio/concepts/understanding_general.rst:69 msgid "" "A **Many2one** field is a *one-way* direction of selecting *one* record from" " a table." msgstr "" #: ../../content/applications/productivity/studio/concepts/understanding_general.rst:70 msgid "" "Example: you can have many product categories, but each product can only " "belong to one category." msgstr "" #: ../../content/applications/productivity/studio/concepts/understanding_general.rst:71 msgid "" "A **Many2many** field is a *two-way* direction of selecting records from a " "table." msgstr "" #: ../../content/applications/productivity/studio/concepts/understanding_general.rst:72 msgid "Example: multiple tags can be added to a lead’s form." msgstr "" #: ../../content/applications/productivity/studio/concepts/understanding_general.rst:75 msgid "An *One2many* field must have a *Many2one* related to it." msgstr "" #: ../../content/applications/productivity/studio/concepts/understanding_general.rst:78 msgid "What are Views?" msgstr "" #: ../../content/applications/productivity/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 "" #: ../../content/applications/productivity/studio/concepts/understanding_general.rst:85 msgid "What is a Menu?" msgstr "" #: ../../content/applications/productivity/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 "" #: ../../content/applications/productivity/studio/concepts/understanding_general.rst:95 msgid "`Studio Basics `_" msgstr "" #: ../../content/applications/productivity/studio/how_to.rst:3 msgid "How To" msgstr "" #: ../../content/applications/productivity/studio/how_to/export_import.rst:3 msgid "Export and Import Modules" msgstr "" #: ../../content/applications/productivity/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 "" #: ../../content/applications/productivity/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 "" #: ../../content/applications/productivity/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 "" #: ../../content/applications/productivity/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 "" #: ../../content/applications/productivity/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 "" #: ../../content/applications/productivity/studio/how_to/rainbow_man.rst:3 msgid "Customizing the Rainbow Man" msgstr "" #: ../../content/applications/productivity/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 "" #: ../../content/applications/productivity/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 "" #: ../../content/applications/productivity/studio/how_to/rainbow_man.rst:14 msgid "By default, the feature is active:" msgstr "" #: ../../content/applications/productivity/studio/how_to/rainbow_man.rst:16 msgid "when opportunities are marked as won;" msgstr "" #: ../../content/applications/productivity/studio/how_to/rainbow_man.rst:17 msgid "when users empty their inboxes;" msgstr "" #: ../../content/applications/productivity/studio/how_to/rainbow_man.rst:18 msgid "when the user finishes a tour;" msgstr "" #: ../../content/applications/productivity/studio/how_to/rainbow_man.rst:19 msgid "when the user finishes doing reconciliations." msgstr "" #: ../../content/applications/productivity/studio/how_to/reports.rst:3 msgid "Customizing Reports" msgstr "" #: ../../content/applications/productivity/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 "" #: ../../content/applications/productivity/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 "" #: ../../content/applications/productivity/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 "" #: ../../content/applications/productivity/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 "" #: ../../content/applications/productivity/studio/how_to/reports.rst:34 msgid "" "Under **Visible if**, define the rule(s) to set visibility conditions to " "fields." msgstr "" #: ../../content/applications/productivity/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 "" #: ../../content/applications/productivity/studio/how_to/reports.rst:40 msgid "" "**Visible for** is used to set which :doc:`groups " "` 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 "" #: ../../content/applications/productivity/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 "" #: ../../content/applications/productivity/studio/how_to/reports.rst:53 msgid "" "If activating the :doc:`Developer mode " "`, additional fields such as " "*Class* under *Options*, and *Reload from attachment* under *Report*, become" " visible." msgstr "" #: ../../content/applications/productivity/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 "" #: ../../content/applications/productivity/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 "" #: ../../content/applications/productivity/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 "" #: ../../content/applications/productivity/studio/use_cases.rst:3 msgid "Use Cases" msgstr "" #: ../../content/applications/productivity/studio/use_cases/automated_actions.rst:3 msgid "Advanced Use Cases: Automated Actions" msgstr "" #: ../../content/applications/productivity/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 "" #: ../../content/applications/productivity/studio/use_cases/automated_actions.rst:8 msgid "Under *Automations*, click on *Create* and set the following rules:" msgstr "" #: ../../content/applications/productivity/studio/use_cases/automated_actions.rst:10 msgid "*Model*: Lead/Opportunity" msgstr "" #: ../../content/applications/productivity/studio/use_cases/automated_actions.rst:11 msgid "*Active*: On" msgstr "" #: ../../content/applications/productivity/studio/use_cases/automated_actions.rst:12 msgid "*Trigger*: On Creation & Update" msgstr "" #: ../../content/applications/productivity/studio/use_cases/automated_actions.rst:13 msgid "*Apply on*: Country > Country Name = Belgium" msgstr "" #: ../../content/applications/productivity/studio/use_cases/automated_actions.rst:14 #: ../../content/applications/productivity/studio/use_cases/filters_status_bar.rst:53 msgid "*Action To Do*: Update the Record" msgstr "" #: ../../content/applications/productivity/studio/use_cases/automated_actions.rst:15 msgid "*Data to Write*: Lead/Opportunity > Value > 3" msgstr "" #: ../../content/applications/productivity/studio/use_cases/automated_actions.rst:22 msgid "" "Check :doc:`this doc ` in order to have another " "automated action example." msgstr "" #: ../../content/applications/productivity/studio/use_cases/automated_actions.rst:25 msgid ":doc:`../concepts/understanding_automated_actions`" msgstr "" #: ../../content/applications/productivity/studio/use_cases/automated_actions.rst:26 #: ../../content/applications/productivity/studio/use_cases/filters_status_bar.rst:61 #: ../../content/applications/productivity/studio/use_cases/models_fields.rst:138 #: ../../content/applications/productivity/studio/use_cases/views.rst:28 msgid ":doc:`../concepts/understanding_general`" msgstr "" #: ../../content/applications/productivity/studio/use_cases/filters_status_bar.rst:3 msgid "Advanced Use Cases: Filters and Status Bar" msgstr "" #: ../../content/applications/productivity/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 "" #: ../../content/applications/productivity/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 "" #: ../../content/applications/productivity/studio/use_cases/filters_status_bar.rst:15 msgid "" "On *Filter Rules* in Studio mode, select the respective filter and enable " "*Default Filter*." msgstr "" #: ../../content/applications/productivity/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 "" #: ../../content/applications/productivity/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 "" #: ../../content/applications/productivity/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 "" #: ../../content/applications/productivity/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 "" #: ../../content/applications/productivity/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 "" #: ../../content/applications/productivity/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 "" #: ../../content/applications/productivity/studio/use_cases/filters_status_bar.rst:46 msgid "" "Create an :doc:`automated action " "<../concepts/understanding_automated_actions>` with the selected values:" msgstr "" #: ../../content/applications/productivity/studio/use_cases/filters_status_bar.rst:49 msgid "*Model*: Product Template" msgstr "" #: ../../content/applications/productivity/studio/use_cases/filters_status_bar.rst:50 msgid "*Trigger*: On Update" msgstr "" #: ../../content/applications/productivity/studio/use_cases/filters_status_bar.rst:51 msgid "*First Domain*: Pipeline status bar = In use" msgstr "" #: ../../content/applications/productivity/studio/use_cases/filters_status_bar.rst:52 msgid "*Second Domain*: Pipeline status bar = Deprecated" msgstr "" #: ../../content/applications/productivity/studio/use_cases/filters_status_bar.rst:54 msgid "*Data to Write*: Cost (Product Template) > Value > 0" msgstr "" #: ../../content/applications/productivity/studio/use_cases/models_fields.rst:3 msgid "Advanced Use Cases: Creating Models and Adding Fields" msgstr "" #: ../../content/applications/productivity/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 "" #: ../../content/applications/productivity/studio/use_cases/models_fields.rst:8 msgid "" "On your leads’ form, add a *Related Field* to *Country > Country Name*." msgstr "" #: ../../content/applications/productivity/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 "" #: ../../content/applications/productivity/studio/use_cases/models_fields.rst:11 msgid "You can now hide the related field created (*Country*) if you wish." msgstr "" #: ../../content/applications/productivity/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 "" #: ../../content/applications/productivity/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 "" #: ../../content/applications/productivity/studio/use_cases/models_fields.rst:22 msgid "Again, hide the related field with the country’s ID if you prefer." msgstr "" #: ../../content/applications/productivity/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 "" #: ../../content/applications/productivity/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 "" #: ../../content/applications/productivity/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 "" #: ../../content/applications/productivity/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 "" #: ../../content/applications/productivity/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 "" #: ../../content/applications/productivity/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 "" #: ../../content/applications/productivity/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 "" #: ../../content/applications/productivity/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 "" #: ../../content/applications/productivity/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 "" #: ../../content/applications/productivity/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 "" #: ../../content/applications/productivity/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 "" #: ../../content/applications/productivity/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 "" #: ../../content/applications/productivity/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 "" #: ../../content/applications/productivity/studio/use_cases/models_fields.rst:96 msgid "Now, add a *Selection* field and the necessary values." msgstr "" #: ../../content/applications/productivity/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 "" #: ../../content/applications/productivity/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 "" #: ../../content/applications/productivity/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 "" #: ../../content/applications/productivity/studio/use_cases/models_fields.rst:117 msgid "**Case scenario 5: change the tooltip of a field for all views.**" msgstr "" #: ../../content/applications/productivity/studio/use_cases/models_fields.rst:119 msgid "" "Activate the :doc:`Developer mode " "` and open Studio." msgstr "" #: ../../content/applications/productivity/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 "" #: ../../content/applications/productivity/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 "" #: ../../content/applications/productivity/studio/use_cases/views.rst:3 msgid "Advanced Use Cases: Views" msgstr "" #: ../../content/applications/productivity/studio/use_cases/views.rst:5 msgid "" "**Case scenario 1: in Sales, show orders in a Kanban View instead of a List " "View.**" msgstr "" #: ../../content/applications/productivity/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 "" #: ../../content/applications/productivity/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 "" #: ../../content/applications/productivity/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 "" #: ../../content/applications/productivity/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 ""