NextERP/documentation
5
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity
saas-18.2
documentation/locale/sources/studio.pot
Tiffany Chang (tic) c68ffc0b20 [I18N] *: re-export pot files 
As per usual, leave off developer.pot and contributing.pot since we
don't translate them (not useful, can't really contribute to/dev in
Odoo without knowing English)

closes odoo/documentation#12130

X-original-commit: aad8aa1314
Signed-off-by: Tiffany Chang (tic) <tic@odoo.com>
2025-02-21 09:42:54 +00:00

2226 lines
107 KiB
Plaintext
Raw Permalink Blame History

This file contains ambiguous Unicode characters

This file contains Unicode characters that might be confused with other characters. If you think that this is intentional, you can safely ignore this warning. Use the Escape button to reveal them.

# SOME DESCRIPTIVE TITLE.
# Copyright (C) Odoo S.A.
# This file is distributed under the same license as the Odoo package.
# FIRST AUTHOR <EMAIL@ADDRESS>, YEAR.
#
#, fuzzy
msgid ""
msgstr ""
"Project-Id-Version: Odoo 18.0\n"
"Report-Msgid-Bugs-To: \n"
"POT-Creation-Date: 2025-02-20 16:01+0000\n"
"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
"Language-Team: LANGUAGE <LL@li.org>\n"
"MIME-Version: 1.0\n"
"Content-Type: text/plain; charset=UTF-8\n"
"Content-Transfer-Encoding: 8bit\n"
#: ../../content/applications/studio.rst:6
msgid "Studio"
msgstr ""
#: ../../content/applications/studio.rst:18
msgid "Studio is a toolbox that allows you to customize Odoo without coding knowledge. For example, you can, in any app, add or modify:"
msgstr ""
#: ../../content/applications/studio.rst:21
msgid ":doc:`Fields <studio/fields>`"
msgstr ""
#: ../../content/applications/studio.rst:22
msgid ":doc:`Views <studio/views>`"
msgstr ""
#: ../../content/applications/studio.rst:23
msgid ":doc:`Models <studio/models_modules_apps>`"
msgstr ""
#: ../../content/applications/studio.rst:24
msgid ":doc:`Automation rules <studio/automated_actions>`"
msgstr ""
#: ../../content/applications/studio.rst:25
msgid ":doc:`PDF reports <studio/pdf_reports>`"
msgstr ""
#: ../../content/applications/studio.rst:26
msgid ":doc:`Approval rules <studio/approval_rules>`"
msgstr ""
#: ../../content/applications/studio.rst:27
msgid "Security rules"
msgstr ""
#: ../../content/applications/studio.rst:29
msgid "You can also :doc:`build an app from scratch <studio/models_modules_apps>`."
msgstr ""
#: ../../content/applications/studio.rst:33
msgid "To access Studio, navigate to the app and model you want to modify, then click the **Toggle Studio** button, or vice versa."
msgstr ""
#: ../../content/applications/studio.rst:36
msgid "To close Studio, click :guilabel:`Close` in the upper right corner."
msgstr ""
#: ../../content/applications/studio.rst:39
msgid "`Odoo Tutorials: Studio <https://www.odoo.com/slides/studio-31>`_"
msgstr ""
#: ../../content/applications/studio/approval_rules.rst:3
msgid "Approval rules"
msgstr ""
#: ../../content/applications/studio/approval_rules.rst:5
msgid "Approval rules are used to automate approval processes for actions. They allow you to define the criteria for when an approval is required before an action can be performed using a button."
msgstr ""
#: ../../content/applications/studio/approval_rules.rst:9
msgid "Configuration"
msgstr ""
#: ../../content/applications/studio/approval_rules.rst:11
msgid "To add approval rules with Studio, proceed as follows:"
msgstr ""
#: ../../content/applications/studio/approval_rules.rst:13
msgid ":ref:`Open Studio <studio/access>` and switch to the required :doc:`view <views>`."
msgstr ""
#: ../../content/applications/studio/approval_rules.rst:14
msgid "Select the button to which the rule should be applied."
msgstr ""
#: ../../content/applications/studio/approval_rules.rst:15
msgid "Click :icon:`fa-plus` :guilabel:`Add an approval step` in the :icon:`fa-server` :guilabel:`Properties` tab."
msgstr ""
#: ../../content/applications/studio/approval_rules.rst:17
msgid "Specify which users are responsible for approving the action by using one of the following fields or both:"
msgstr ""
#: ../../content/applications/studio/approval_rules.rst:20
msgid ":guilabel:`Approvers` to specify one or several users;"
msgstr ""
#: ../../content/applications/studio/approval_rules.rst:21
msgid ":guilabel:`Approver Group` to specify one user group."
msgstr ""
#: ../../content/applications/studio/approval_rules.rst:24
msgid "An activity is created for all users set as :guilabel:`Approvers` when their approval is requested."
msgstr ""
#: ../../content/applications/studio/approval_rules.rst:27
msgid "(*optional*) Select the :guilabel:`Users to Notify` via an internal note when the action is approved or rejected."
msgstr ""
#: ../../content/applications/studio/approval_rules.rst:29
msgid "(*optional*) Add a :guilabel:`Description` to be displayed on the button."
msgstr ""
#: ../../content/applications/studio/approval_rules.rst:32
msgid "You can specify under which condition(s) an approval step should be applied by clicking the :icon:`fa-filter` (:guilabel:`filter`) icon next to the :guilabel:`Approvers` field."
msgstr ""
#: ../../content/applications/studio/approval_rules.rst:35
msgid "To add another approval step, click :icon:`fa-plus` :guilabel:`Add an approval step`. When there are multiple steps, you can:"
msgstr ""
#: ../../content/applications/studio/approval_rules.rst:38
msgid "Enable :guilabel:`Exclusive Approval` on any step so that a user who approves a step cannot approve another step for the same record."
msgstr ""
#: ../../content/applications/studio/approval_rules.rst:40
msgid "Change the :guilabel:`Approval Order` of the steps by selecting a number, `1` being the first step, `2` the second step, and so on. A user responsible for a higher step can approve/reject previous step(s) unless :guilabel:`Exclusive Approval` is selected."
msgstr ""
#: ../../content/applications/studio/approval_rules.rst:44
msgid "Click the :icon:`fa-trash` (:guilabel:`trash`) icon next to the :guilabel:`Approvers` field to remove an approval step."
msgstr ""
#: ../../content/applications/studio/approval_rules.rst:48
msgid "You can create :ref:`user groups <access-rights/groups>` specifically for approvals."
msgstr ""
#: ../../content/applications/studio/approval_rules.rst:53
msgid "Use"
msgstr ""
#: ../../content/applications/studio/approval_rules.rst:55
msgid "Once an approval rule has been defined for a button, a **user avatar** icon is displayed next to the button's label for each approval step. Clicking an icon reveals the step(s)."
msgstr ""
#: ../../content/applications/studio/approval_rules.rst:-1
msgid "Confirm button with two approval steps"
msgstr ""
#: ../../content/applications/studio/approval_rules.rst:62
msgid "If an unauthorized user clicks the button, an error message is displayed and an activity is created for the users specified in the :guilabel:`Approvers` field, if any."
msgstr ""
#: ../../content/applications/studio/approval_rules.rst:65
msgid "Authorized users can:"
msgstr ""
#: ../../content/applications/studio/approval_rules.rst:67
msgid "Perform the action directly by clicking the button if it is the last/only approval step."
msgstr ""
#: ../../content/applications/studio/approval_rules.rst:68
msgid "Approve the action and let another user perform it - or move it to the next approval step - by clicking the **user avatar** icon next to the button's label, then clicking the :icon:`fa-check` (:guilabel:`approve`)."
msgstr ""
#: ../../content/applications/studio/approval_rules.rst:71
msgid "Reject the action by clicking the **user avatar** icon next to the button's label and then the :icon:`fa-times` (:guilabel:`reject`) button."
msgstr ""
#: ../../content/applications/studio/approval_rules.rst:73
msgid "(only for users selected under the :guilabel:`Approvers` field) Delegate their approval rights to one or several users for **all records** by:"
msgstr ""
#: ../../content/applications/studio/approval_rules.rst:76
msgid "Clicking the :icon:`oi-view-kanban` (:guilabel:`kanban view`) icon and then :guilabel:`Delegate`."
msgstr ""
#: ../../content/applications/studio/approval_rules.rst:78
msgid "Selecting one or several :guilabel:`Approvers`, :guilabel:`Until` when they will have approval rights (forever if left empty), and, optionally, the user(s) who should be notified via an internal note using the :guilabel:`Notify to` field."
msgstr ""
#: ../../content/applications/studio/approval_rules.rst:0
msgid "Delegate to dialog"
msgstr ""
#: ../../content/applications/studio/approval_rules.rst:86
msgid "A user who approves/rejects an action can revoke their decision by clicking the **user avatar** icon next to the button's label and then the :icon:`fa-undo` (:guilabel:`revoke`) button. They can also revoke the decision of other users for steps with a lower :guilabel:`Approval Order` unless :guilabel:`Exclusive Approval` is enabled."
msgstr ""
#: ../../content/applications/studio/approval_rules.rst:90
msgid "Approvals are tracked in the record's chatter. An approval entry is also created every time a Studio approval-related action is performed. To access approval entries, :doc:`activate the developer mode </applications/general/developer_mode>` and go to :menuselection:`Settings --> Technical --> Studio Approval Entries`."
msgstr ""
#: ../../content/applications/studio/automated_actions.rst:3
msgid "Automation rules"
msgstr ""
#: ../../content/applications/studio/automated_actions.rst:5
msgid "Automation rules are used to trigger automatic changes based on user actions (e.g., apply a modification when a field is set to a specific value), email events, time conditions (e.g., archive a record 7 days after its last update), or external events."
msgstr ""
#: ../../content/applications/studio/automated_actions.rst:9
msgid "To create an automation rule with Studio, proceed as follows:"
msgstr ""
#: ../../content/applications/studio/automated_actions.rst:11
msgid ":ref:`Open Studio <studio/access>` and click :guilabel:`Automations`, then :guilabel:`New`."
msgstr ""
#: ../../content/applications/studio/automated_actions.rst:12
msgid "Select the :ref:`studio/automated-actions/trigger` and, if necessary, fill in the fields that appear on the screen based on the chosen trigger."
msgstr ""
#: ../../content/applications/studio/automated_actions.rst:14
msgid "Click :guilabel:`Add an action`, then select the :guilabel:`Type` of :ref:`action <studio/automated-actions/action>` and fill in the fields that appear on the screen based on your selected action."
msgstr ""
#: ../../content/applications/studio/automated_actions.rst:17
msgid "Click :guilabel:`Save & Close` or :guilabel:`Save & New`."
msgstr ""
#: ../../content/applications/studio/automated_actions.rst:0
msgid "Example of an automated action on the Subscription model"
msgstr ""
#: ../../content/applications/studio/automated_actions.rst:25
msgid "To modify the :doc:`model <models_modules_apps>` of the automation rule, switch models before clicking :guilabel:`Automations` in Studio, or :ref:`activate the developer mode <developer-mode>`, create or edit an automation rule, and select the :guilabel:`Model` in the :guilabel:`Automation Rules` form."
msgstr ""
#: ../../content/applications/studio/automated_actions.rst:29
msgid "You can also create automation rules from any kanban stage by clicking the gear icon (:guilabel:`⚙` ) next to the kanban stage name, then selecting :guilabel:`Automations`. In this case, the :guilabel:`Trigger` is set to :guilabel:`Stage is set to` by default, but you can change it if necessary."
msgstr ""
#: ../../content/applications/studio/automated_actions.rst:0
msgid "Create automations from a kanban stage"
msgstr ""
#: ../../content/applications/studio/automated_actions.rst:40
msgid "Trigger"
msgstr ""
#: ../../content/applications/studio/automated_actions.rst:42
msgid "The :guilabel:`Trigger` is used to define when the automation rule should be applied. The available triggers depend on the :doc:`model <models_modules_apps>`. Five trigger categories are available overall:"
msgstr ""
#: ../../content/applications/studio/automated_actions.rst:46
msgid ":ref:`studio/automated-actions/trigger/values-updated`"
msgstr ""
#: ../../content/applications/studio/automated_actions.rst:47
msgid ":ref:`studio/automated-actions/trigger/email-events`"
msgstr ""
#: ../../content/applications/studio/automated_actions.rst:48
msgid ":ref:`studio/automated-actions/trigger/values-timing-conditions`"
msgstr ""
#: ../../content/applications/studio/automated_actions.rst:49
msgid ":ref:`studio/automated-actions/trigger/custom`"
msgstr ""
#: ../../content/applications/studio/automated_actions.rst:50
msgid ":ref:`studio/automated-actions/trigger/external`"
msgstr ""
#: ../../content/applications/studio/automated_actions.rst:53
msgid "You can also define a :guilabel:`Before Update Domain` to specify the conditions that must be met *before* the automation rule is triggered. In contrast, the conditions defined using the :ref:`Extra Conditions <studio/automated-actions/trigger/values-timing-conditions>` and :ref:`Apply on <studio/automated-actions/trigger/custom>` filters are checked *during* the execution of the automation rule."
msgstr ""
#: ../../content/applications/studio/automated_actions.rst:59
msgid "To define a :guilabel:`Before Update Domain`, :ref:`activate the developer mode <developer-mode>`, create or edit an automation rule, click :guilabel:`Edit Domain`, then click :guilabel:`New Rule`."
msgstr ""
#: ../../content/applications/studio/automated_actions.rst:63
msgid "For example, if you want the automated action to happen when an email address is set on a contact that did not have an address before (in contrast to modifying their existing address), define the :guilabel:`Before Update Domain` to :guilabel:`Email is not set`, and the :guilabel:`Apply on` domain to :guilabel:`Email is set`."
msgstr ""
#: ../../content/applications/studio/automated_actions.rst:0
msgid "Example of a trigger with a Before Update Domain"
msgstr ""
#: ../../content/applications/studio/automated_actions.rst:74
msgid "Values Updated"
msgstr ""
#: ../../content/applications/studio/automated_actions.rst:76
msgid "The triggers available in this category depend on the model and are based on common field changes, such as adding a specific tag (e.g., to a task) or setting the :guilabel:`User` field. Select the trigger, then select a value if required."
msgstr ""
#: ../../content/applications/studio/automated_actions.rst:-1
msgid "Example of a Values Updated trigger"
msgstr ""
#: ../../content/applications/studio/automated_actions.rst:86
msgid "Email Events"
msgstr ""
#: ../../content/applications/studio/automated_actions.rst:88
msgid "Trigger automated actions upon receiving or sending emails."
msgstr ""
#: ../../content/applications/studio/automated_actions.rst:93
msgid "Timing Conditions"
msgstr ""
#: ../../content/applications/studio/automated_actions.rst:95
msgid "Trigger automated actions based on a date field. The following triggers are available:"
msgstr ""
#: ../../content/applications/studio/automated_actions.rst:97
msgid ":guilabel:`Based on date field`: Select the field to be used next to the :guilabel:`Delay` field."
msgstr ""
#: ../../content/applications/studio/automated_actions.rst:98
msgid ":guilabel:`After creation`: The action is triggered when a record is created and saved."
msgstr ""
#: ../../content/applications/studio/automated_actions.rst:99
msgid ":guilabel:`After last update`: The action is triggered when an existing record is edited and saved."
msgstr ""
#: ../../content/applications/studio/automated_actions.rst:102
msgid "You can then define:"
msgstr ""
#: ../../content/applications/studio/automated_actions.rst:104
msgid "a :guilabel:`Delay`: Specify the number of minutes, hours, days, or months. To trigger the action before the trigger date, specify a negative number. If you selected the :guilabel:`Based on date field` trigger, you must also select the date field to be used to determine the delay."
msgstr ""
#: ../../content/applications/studio/automated_actions.rst:107
msgid ":guilabel:`Extra Conditions`: Click :guilabel:`Add condition`, then specify the conditions to be met to trigger the automation rule. Click :guilabel:`New Rule` to add another condition."
msgstr ""
#: ../../content/applications/studio/automated_actions.rst:110
msgid "The action is triggered when the delay is reached and the conditions are met."
msgstr ""
#: ../../content/applications/studio/automated_actions.rst:113
msgid "If you want to send a reminder email 30 minutes before the start of a calendar event, select the :guilabel:`Start (Calendar Event)` under :guilabel:`Trigger Date` and set the :guilabel:`Delay` to **-30** :guilabel:`Minutes`."
msgstr ""
#: ../../content/applications/studio/automated_actions.rst:0
msgid "Example of a Based on date field trigger"
msgstr ""
#: ../../content/applications/studio/automated_actions.rst:121
msgid "By default, the scheduler checks for trigger dates every 4 hours, meaning lower granularity in time-based automations may not always be honored."
msgstr ""
#: ../../content/applications/studio/automated_actions.rst:127
msgid "Custom"
msgstr ""
#: ../../content/applications/studio/automated_actions.rst:129
msgid "Trigger automated actions:"
msgstr ""
#: ../../content/applications/studio/automated_actions.rst:131
msgid ":guilabel:`On save`: When the record is saved;"
msgstr ""
#: ../../content/applications/studio/automated_actions.rst:132
msgid ":guilabel:`On deletion`: When a record is deleted;"
msgstr ""
#: ../../content/applications/studio/automated_actions.rst:133
msgid ":guilabel:`On UI change`: When a field's value is changed on the :ref:`Form view <studio/views/general/form>`, even before saving the record."
msgstr ""
#: ../../content/applications/studio/automated_actions.rst:136
msgid "For the :guilabel:`On save` and :guilabel:`On UI change` triggers, you **must** then select the field(s) to be used to trigger the automation rule in the :guilabel:`When updating` field."
msgstr ""
#: ../../content/applications/studio/automated_actions.rst:140
msgid "If no field is selected in the :guilabel:`When updating` field, the automated action may be executed multiple times per record."
msgstr ""
#: ../../content/applications/studio/automated_actions.rst:143
msgid "Optionally, you can also define additional conditions to be met to trigger the automation rule in the :guilabel:`Apply on` field."
msgstr ""
#: ../../content/applications/studio/automated_actions.rst:147
msgid "The :guilabel:`On UI change` trigger can only be used with the :ref:`studio/automated-actions/action/python-code` action and only works when a modification is made manually. The action is not executed if the field is changed through another automation rule."
msgstr ""
#: ../../content/applications/studio/automated_actions.rst:155
msgid "External"
msgstr ""
#: ../../content/applications/studio/automated_actions.rst:157
msgid "Trigger automated actions based on an external event using a webhook. A webhook is a method of communication between two systems where the source system sends an HTTP(S) request to a destination system based on a specific event. It usually includes a data payload containing information about the event that occurred."
msgstr ""
#: ../../content/applications/studio/automated_actions.rst:162
msgid "To configure the :guilabel:`On webhook` trigger, copy the :guilabel:`URL` generated by Odoo into the destination system (i.e., the system receiving the request). Then, in the :guilabel:`Target Record` field, enter the code to run to define the record(s) to be updated using the automation rule."
msgstr ""
#: ../../content/applications/studio/automated_actions.rst:167
msgid "The URL must be treated as **confidential**; sharing it online or without caution could potentially expose your system to malicious parties. Click the :guilabel:`Rotate Secret` button to change the URL's secret if necessary."
msgstr ""
#: ../../content/applications/studio/automated_actions.rst:172
msgid "The code defined by default in the :guilabel:`Target Record` field works for webhooks coming from another Odoo database. It is used to determine the record(s) to be updated using the information in the payload."
msgstr ""
#: ../../content/applications/studio/automated_actions.rst:175
msgid "If you wish to use the webhook's content for a purpose other than to find the record(s) (e.g., *create* a record), your only option is to use an :ref:`studio/automated-actions/action/python-code` action. In this case, the :guilabel:`Target record` field must contain any valid code, but its result doesn't have any effect on the automated action itself."
msgstr ""
#: ../../content/applications/studio/automated_actions.rst:179
msgid "The webhook content is available in the server action context as a `payload` variable (i.e., a dictionary that contains the GET parameters or POST JSON body of the incoming request)."
msgstr ""
#: ../../content/applications/studio/automated_actions.rst:182
msgid "You can also choose to :guilabel:`Log Calls` to record the payloads received, e.g., to make sure the data sent by the source system matches the expected format and content. This also helps identify and diagnose any issues that may arise. To access the logs, click the :guilabel:`Logs` smart button at the top of the :guilabel:`Automation rules` form."
msgstr ""
#: ../../content/applications/studio/automated_actions.rst:190
msgid "Actions"
msgstr ""
#: ../../content/applications/studio/automated_actions.rst:192
msgid "Once you have defined the automation rule's :ref:`trigger <studio/automated-actions/trigger>`, click :guilabel:`Add an action` to define the action to be executed."
msgstr ""
#: ../../content/applications/studio/automated_actions.rst:196
msgid "You can define multiple actions for the same trigger/automation rule. The actions are executed in the order they are defined. This means, for example, that if you define an :guilabel:`Update record` action and then a :guilabel:`Send email` action, the email uses the updated values. However, if the :guilabel:`Send email` action is defined before the :guilabel:`Update record` action, the email uses the values set *before* the update action is run."
msgstr ""
#: ../../content/applications/studio/automated_actions.rst:206
msgid "Update Record"
msgstr ""
#: ../../content/applications/studio/automated_actions.rst:208
msgid "This action allows to update one of the record's (related) fields. Click the :guilabel:`Update` field and, in the list that opens, select or search for the field to be updated; click the right arrow next to the field name to access the list of related fields if needed."
msgstr ""
#: ../../content/applications/studio/automated_actions.rst:212
msgid "If you selected a :ref:`many2many field <studio/fields/relational-fields/many2many>`, choose whether the field must be updated by :guilabel:`Adding`, :guilabel:`Removing`, or :guilabel:`Setting it to` the selected value or by :guilabel:`Clearing it`."
msgstr ""
#: ../../content/applications/studio/automated_actions.rst:217
msgid "If you want the automated action to remove a tag from the customer record, set the :guilabel:`Update` field to :guilabel:`Customer > Tags`, select :guilabel:`By Removing`, then select the tag."
msgstr ""
#: ../../content/applications/studio/automated_actions.rst:0
msgid "Example of an Update Record action"
msgstr ""
#: ../../content/applications/studio/automated_actions.rst:225
msgid "Alternatively, you can also set a record's field dynamically using Python code. To do so, select :guilabel:`Compute` instead of :guilabel:`Update`, then enter the code to be used for computing the field's value. For example, if you want the automation rule to compute a custom :ref:`datetime field <studio/fields/simple-fields/date-time>` when a task's priority is set to `High` (by starring the task), you can define the trigger :guilabel:`Priority is set to` to `High` and define the :guilabel:`Update Record` action as follows:"
msgstr ""
#: ../../content/applications/studio/automated_actions.rst:0
msgid "Compute a custom datetime field using a Python expression"
msgstr ""
#: ../../content/applications/studio/automated_actions.rst:236
msgid "Create Activity"
msgstr ""
#: ../../content/applications/studio/automated_actions.rst:238
msgid "This action is used to schedule a new activity linked to the record. Select an :guilabel:`Activity Type`, enter a :guilabel:`Title` and description, then specify when you want the activity to be scheduled in the :guilabel:`Due Date In` field, and select a :guilabel:`User type`:"
msgstr ""
#: ../../content/applications/studio/automated_actions.rst:242
msgid "To always assign the activity to the same user, select :guilabel:`Specific User` and add the user in the :guilabel:`Responsible` field;"
msgstr ""
#: ../../content/applications/studio/automated_actions.rst:244
msgid "To target a user linked to the record dynamically, select :guilabel:`Dynamic User (based on record)` and change the :guilabel:`User Field` if necessary."
msgstr ""
#: ../../content/applications/studio/automated_actions.rst:248
msgid "After a lead is turned into an opportunity, you want the automated action to set up a call for the user responsible for the lead. To do so, set the :guilabel:`Activity Type` to :guilabel:`Call` and the :guilabel:`User Type` to :guilabel:`Dynamic User (based on record)`."
msgstr ""
#: ../../content/applications/studio/automated_actions.rst:0
msgid "Example of a Create Activity action"
msgstr ""
#: ../../content/applications/studio/automated_actions.rst:256
msgid "Send Email and Send SMS"
msgstr ""
#: ../../content/applications/studio/automated_actions.rst:258
msgid "These actions are used to send an email or a text message to a contact linked to a specific record. To do so, select or create an :guilabel:`Email Template` or an :guilabel:`SMS Template`, then, in the :guilabel:`Send Email As` or :guilabel:`Send SMS As` field, choose how you want to send the email or text message:"
msgstr ""
#: ../../content/applications/studio/automated_actions.rst:263
msgid ":guilabel:`Email`: to send the message as an email to the recipients of the :guilabel:`Email Template`."
msgstr ""
#: ../../content/applications/studio/automated_actions.rst:265
msgid ":guilabel:`Message`: to post the message on the record and notify the record's followers."
msgstr ""
#: ../../content/applications/studio/automated_actions.rst:266
msgid ":guilabel:`Note`: to send the message as an internal note visible to internal users in the chatter."
msgstr ""
#: ../../content/applications/studio/automated_actions.rst:268
msgid ":guilabel:`SMS (without note)`: to send the message as a text message to the recipients of the :guilabel:`SMS template`."
msgstr ""
#: ../../content/applications/studio/automated_actions.rst:270
msgid ":guilabel:`SMS (with note)`: to send the message as a text message to the recipients of the :guilabel:`SMS template` and post it as an internal note in the chatter."
msgstr ""
#: ../../content/applications/studio/automated_actions.rst:272
msgid ":guilabel:`Note only`: to only post the message as an internal note in the chatter."
msgstr ""
#: ../../content/applications/studio/automated_actions.rst:277
msgid "Send WhatsApp"
msgstr ""
#: ../../content/applications/studio/automated_actions.rst:280
msgid "To automate the sending of WhatsApp messages, one or more :ref:`WhatsApp templates <productivity/whatsapp/templates>` must be created."
msgstr ""
#: ../../content/applications/studio/automated_actions.rst:283
msgid "This action is used to send a WhatsApp message to a contact linked to a specific record. To do so, select the appropriate :guilabel:`WhatsApp Template` from the drop-down menu."
msgstr ""
#: ../../content/applications/studio/automated_actions.rst:289
msgid "Add Followers and Remove Followers"
msgstr ""
#: ../../content/applications/studio/automated_actions.rst:291
msgid "Use these actions to (un)subscribe existing contacts to/from the record."
msgstr ""
#: ../../content/applications/studio/automated_actions.rst:294
msgid "Create Record"
msgstr ""
#: ../../content/applications/studio/automated_actions.rst:296
msgid "This action is used to create a new record on any model."
msgstr ""
#: ../../content/applications/studio/automated_actions.rst:298
msgid "Select the required model in the :guilabel:`Record to Create` field; it contains the current model by default. Specify a :guilabel:`Name` for the record, and then, if you want to create the record on another model, select a field in the :guilabel:`Link Field` field to link the record that triggered the creation of the new record."
msgstr ""
#: ../../content/applications/studio/automated_actions.rst:304
msgid "The dropdown list related to the :guilabel:`Link Field` field only contains :ref:`one2many fields <studio/fields/relational-fields/one2many>` existing on the current model that are linked to a :ref:`many2one field <studio/fields/relational-fields/many2one>` on the target model."
msgstr ""
#: ../../content/applications/studio/automated_actions.rst:309
msgid "You can create another automation rule with :ref:`studio/automated-actions/action/update-record` actions to update the fields of the new record if necessary. For example, you can use a :guilabel:`Create Record` action to create a new project task and then assign it to a specific user using an :guilabel:`Update Record` action."
msgstr ""
#: ../../content/applications/studio/automated_actions.rst:317
msgid "Execute Code"
msgstr ""
#: ../../content/applications/studio/automated_actions.rst:319
msgid "This action is used to execute Python code. You can write your code into the :guilabel:`Code` tab using the following variables:"
msgstr ""
#: ../../content/applications/studio/automated_actions.rst:322
msgid "`env`: environment on which the action is triggered"
msgstr ""
#: ../../content/applications/studio/automated_actions.rst:323
msgid "`model`: model of the record on which the action is triggered; is a void recordset"
msgstr ""
#: ../../content/applications/studio/automated_actions.rst:324
msgid "`record`: record on which the action is triggered; may be void"
msgstr ""
#: ../../content/applications/studio/automated_actions.rst:325
msgid "`records`: recordset of all records on which the action is triggered in multi-mode; this may be left empty"
msgstr ""
#: ../../content/applications/studio/automated_actions.rst:327
msgid "`time`, `datetime`, `dateutil`, `timezone`: useful Python libraries"
msgstr ""
#: ../../content/applications/studio/automated_actions.rst:328
msgid "`float_compare`: utility function to compare floats based on specific precision"
msgstr ""
#: ../../content/applications/studio/automated_actions.rst:329
msgid "`log(message, level='info')`: logging function to record debug information in ir.logging table"
msgstr ""
#: ../../content/applications/studio/automated_actions.rst:331
msgid "`_logger.info(message)`: logger to emit messages in server logs"
msgstr ""
#: ../../content/applications/studio/automated_actions.rst:332
msgid "`UserError`: exception class for raising user-facing warning messages"
msgstr ""
#: ../../content/applications/studio/automated_actions.rst:333
msgid "`Command`: x2many commands namespace"
msgstr ""
#: ../../content/applications/studio/automated_actions.rst:334
msgid "`action = {...}`: to return an action"
msgstr ""
#: ../../content/applications/studio/automated_actions.rst:337
msgid "The available variables are described both in the :guilabel:`Code` and :guilabel:`Help` tabs."
msgstr ""
#: ../../content/applications/studio/automated_actions.rst:340
msgid "Send Webhook Notification"
msgstr ""
#: ../../content/applications/studio/automated_actions.rst:342
msgid "This action allows to send a POST request with the values of the :guilabel:`Fields` to the URL specified in the :guilabel:`URL` field."
msgstr ""
#: ../../content/applications/studio/automated_actions.rst:345
msgid "The :guilabel:`Sample Payload` provides a preview of the data included in the request using a random record's data or dummy data if no record is available."
msgstr ""
#: ../../content/applications/studio/automated_actions.rst:351
msgid "Execute Existing Actions"
msgstr ""
#: ../../content/applications/studio/automated_actions.rst:353
msgid "The action is used to trigger multiple actions (linked to the current model) at the same time. To do so, click on :guilabel:`Add a line`, then, in the :guilabel:`Add: Child Actions` pop-up, select an existing action or click :guilabel:`New` to create a new one."
msgstr ""
#: ../../content/applications/studio/fields.rst:3
msgid "Fields and widgets"
msgstr ""
#: ../../content/applications/studio/fields.rst:5
msgid "Fields structure the models of a database. If you picture a model as a table or spreadsheet, fields are the columns where data is stored in the records (i.e., the rows). Fields also define the type of data that is stored within them. How the data is presented and formatted on the :abbr:`UI (User Interface)` is defined by their widget."
msgstr ""
#: ../../content/applications/studio/fields.rst:10
msgid "From a technical point of view, there are 15 field types in Odoo. However, you can choose from 20 fields in Studio, as some field types are available more than once with a different default widget."
msgstr ""
#: ../../content/applications/studio/fields.rst:14
msgid ":guilabel:`New Fields` can only be added to the :ref:`studio/views/general/form` and :ref:`studio/views/multiple-records/list` views. On other views, you can only add :guilabel:`Existing Fields` :dfn:`(fields already on the model)`."
msgstr ""
#: ../../content/applications/studio/fields.rst:21
msgid "Simple fields"
msgstr ""
#: ../../content/applications/studio/fields.rst:23
msgid "Simple fields contain basic values, such as text, numbers, files, etc."
msgstr ""
#: ../../content/applications/studio/fields.rst:26
#: ../../content/applications/studio/fields.rst:325
msgid "Non-default widgets, when available, are presented as bullet points below."
msgstr ""
#: ../../content/applications/studio/fields.rst:31
msgid "Text (`char`)"
msgstr ""
#: ../../content/applications/studio/fields.rst:33
msgid "The :guilabel:`Text` field is used for short text containing any character. One text line is displayed when filling out the field."
msgstr ""
#: ../../content/applications/studio/fields.rst:36
#: ../../content/applications/studio/fields.rst:220
msgid ":guilabel:`Badge`: displays the value inside a rounded shape, similar to a tag. The value cannot be edited on the UI, but a default value can be set."
msgstr ""
#: ../../content/applications/studio/fields.rst:38
#: ../../content/applications/studio/fields.rst:71
msgid ":guilabel:`Copy to Clipboard`: users can copy the value by clicking a button."
msgstr ""
#: ../../content/applications/studio/fields.rst:39
msgid ":guilabel:`E-mail`: the value becomes a clickable *mailto* link."
msgstr ""
#: ../../content/applications/studio/fields.rst:40
msgid ":guilabel:`Image`: displays an image using a URL. The value cannot be edited manually, but a default value can be set."
msgstr ""
#: ../../content/applications/studio/fields.rst:44
msgid "This works differently than selecting the :ref:`Image field <studio/fields/simple-fields/image>` directly, as the image is not stored in Odoo when using a :guilabel:`Text` field with the :guilabel:`Image` widget. For example, it can be useful if you want to save disk space."
msgstr ""
#: ../../content/applications/studio/fields.rst:49
msgid ":guilabel:`Phone`: the value becomes a clickable *tel* link."
msgstr ""
#: ../../content/applications/studio/fields.rst:52
msgid "Tick :guilabel:`Enable SMS` to add an option to send an SMS directly from Odoo next to the field."
msgstr ""
#: ../../content/applications/studio/fields.rst:55
msgid ":guilabel:`URL`: the value becomes a clickable URL."
msgstr ""
#: ../../content/applications/studio/fields.rst:0
msgid "Examples of Text fields with different widgets"
msgstr ""
#: ../../content/applications/studio/fields.rst:66
msgid "Multiline Text (`text`)"
msgstr ""
#: ../../content/applications/studio/fields.rst:68
msgid "The :guilabel:`Multiline Text` field is used for longer text containing any type of character. Two text lines are displayed on the UI when filling out the field."
msgstr ""
#: ../../content/applications/studio/fields.rst:0
msgid "Examples of Multiline Text fields with different widgets"
msgstr ""
#: ../../content/applications/studio/fields.rst:82
msgid "Integer (`integer`)"
msgstr ""
#: ../../content/applications/studio/fields.rst:84
msgid "The :guilabel:`Integer` field is used for all integer numbers (:dfn:`positive, negative, or zero, without a decimal`)."
msgstr ""
#: ../../content/applications/studio/fields.rst:87
msgid ":guilabel:`Percentage Pie`: displays the value inside a percentage circle, usually for a computed value. The value cannot be edited on the UI, but a default value can be set."
msgstr ""
#: ../../content/applications/studio/fields.rst:89
#: ../../content/applications/studio/fields.rst:118
msgid ":guilabel:`Progress Bar`: displays the value next to a percentage bar, usually for a computed value. The field cannot be edited manually, but a default value can be set."
msgstr ""
#: ../../content/applications/studio/fields.rst:91
msgid ":guilabel:`Handle`: displays a drag handle icon to order records manually in :ref:`List view <studio/views/multiple-records/list>`."
msgstr ""
#: ../../content/applications/studio/fields.rst:0
msgid "Examples of Integer fields with different widgets"
msgstr ""
#: ../../content/applications/studio/fields.rst:103
msgid "Decimal (`float`)"
msgstr ""
#: ../../content/applications/studio/fields.rst:105
msgid "The :guilabel:`Decimal` field is used for all decimal numbers (:dfn:`positive, negative, or zero, with a decimal`)."
msgstr ""
#: ../../content/applications/studio/fields.rst:109
msgid "Decimal numbers are displayed with two decimals after the decimal point on the UI, but they are stored in the database with more precision."
msgstr ""
#: ../../content/applications/studio/fields.rst:112
msgid ":guilabel:`Monetary`: it is similar to using the :ref:`Monetary field <studio/fields/simple-fields/monetary>`. It is recommended to use the later as it offers more functionalities."
msgstr ""
#: ../../content/applications/studio/fields.rst:115
msgid ":guilabel:`Percentage`: displays a percent character `%` after the value."
msgstr ""
#: ../../content/applications/studio/fields.rst:116
msgid ":guilabel:`Percentage Pie`: displays the value inside a percentage circle, usually for a computed value. The field cannot be edited manually, but a default value can be set."
msgstr ""
#: ../../content/applications/studio/fields.rst:120
msgid ":guilabel:`Time`: the value must follow the *hh:mm* format, with a maximum of 59 minutes."
msgstr ""
#: ../../content/applications/studio/fields.rst:0
msgid "Examples of Decimal fields with different widgets"
msgstr ""
#: ../../content/applications/studio/fields.rst:131
msgid "Monetary (`monetary`)"
msgstr ""
#: ../../content/applications/studio/fields.rst:133
msgid "The :guilabel:`Monetary` field is used for all monetary values."
msgstr ""
#: ../../content/applications/studio/fields.rst:136
msgid "When you first add a :guilabel:`Monetary` field, you are prompted to add a :guilabel:`Currency` field if none exists already on the model. Odoo offers to add the :guilabel:`Currency` field for you. Once it is added, add the :guilabel:`Monetary` field again."
msgstr ""
#: ../../content/applications/studio/fields.rst:0
msgid "Example of a Monetary field along with its Currency field"
msgstr ""
#: ../../content/applications/studio/fields.rst:149
msgid "Html (`html`)"
msgstr ""
#: ../../content/applications/studio/fields.rst:151
msgid "The :guilabel:`Html` field is used to add text that can be edited using the Odoo HTML editor."
msgstr ""
#: ../../content/applications/studio/fields.rst:153
msgid ":guilabel:`Multiline Text`: disables the Odoo HTML editor to allow editing raw HTML."
msgstr ""
#: ../../content/applications/studio/fields.rst:0
msgid "Examples of Html fields with different widgets"
msgstr ""
#: ../../content/applications/studio/fields.rst:164
msgid "Date (`date`)"
msgstr ""
#: ../../content/applications/studio/fields.rst:166
msgid "The :guilabel:`Date` field is used to select a date on a calendar."
msgstr ""
#: ../../content/applications/studio/fields.rst:168
msgid ":guilabel:`Remaining Days`: the remaining number of days before the selected date is displayed (e.g., *In 5 days*), based on the current date."
msgstr ""
#: ../../content/applications/studio/fields.rst:0
msgid "Examples of Date fields with different widgets"
msgstr ""
#: ../../content/applications/studio/fields.rst:180
msgid "Date & Time (`datetime`)"
msgstr ""
#: ../../content/applications/studio/fields.rst:182
msgid "The :guilabel:`Date & Time` field is used to select a date on a calendar and a time on a clock. The user's current time is automatically used if no time is set."
msgstr ""
#: ../../content/applications/studio/fields.rst:185
msgid ":guilabel:`Date`: used to record the time without displaying it on the UI."
msgstr ""
#: ../../content/applications/studio/fields.rst:186
msgid ":guilabel:`Remaining days`: displays the remaining number of days before the selected date (e.g., *In 5 days*), based on the current date and time."
msgstr ""
#: ../../content/applications/studio/fields.rst:0
msgid "Examples of Date & Time fields with different widgets"
msgstr ""
#: ../../content/applications/studio/fields.rst:198
msgid "Checkbox (`boolean`)"
msgstr ""
#: ../../content/applications/studio/fields.rst:200
msgid "The :guilabel:`Checkbox` field is used when a value should only be true or false, indicated by checking or unchecking a checkbox."
msgstr ""
#: ../../content/applications/studio/fields.rst:203
msgid ":guilabel:`Button`: displays a radio button. The widget works without switching to the edit mode."
msgstr ""
#: ../../content/applications/studio/fields.rst:204
msgid ":guilabel:`Toggle`: displays a toggle button. The widget works without switching to the edit mode."
msgstr ""
#: ../../content/applications/studio/fields.rst:0
msgid "Examples of Checkbox fields with different widgets"
msgstr ""
#: ../../content/applications/studio/fields.rst:215
msgid "Selection (`selection`)"
msgstr ""
#: ../../content/applications/studio/fields.rst:217
msgid "The :guilabel:`Selection` field is used when users should select a single value from a group of predefined values."
msgstr ""
#: ../../content/applications/studio/fields.rst:222
msgid ":guilabel:`Badges`: displays all selectable values simultaneously inside rectangular shapes, organized horizontally."
msgstr ""
#: ../../content/applications/studio/fields.rst:224
msgid ":guilabel:`Priority`: displays star symbols instead of values, which can be used to indicate an importance or satisfaction level, for example. This has the same effect as selecting the :ref:`Priority field <studio/fields/simple-fields/priority>`, although, for the latter, four priority values are already predefined."
msgstr ""
#: ../../content/applications/studio/fields.rst:228
#: ../../content/applications/studio/fields.rst:352
msgid ":guilabel:`Radio`: displays all selectable values at the same time as radio buttons."
msgstr ""
#: ../../content/applications/studio/fields.rst:231
msgid "By default, radio buttons are organized vertically. Tick :guilabel:`display horizontally` to switch the way they are displayed."
msgstr ""
#: ../../content/applications/studio/fields.rst:0
msgid "Examples of Selection fields with different widgets"
msgstr ""
#: ../../content/applications/studio/fields.rst:243
msgid "Priority (`selection`)"
msgstr ""
#: ../../content/applications/studio/fields.rst:245
msgid "The :guilabel:`Priority` field is used to display a three-star rating system, which can be used to indicate importance or satisfaction level. This field type is a :ref:`Selection field <studio/fields/simple-fields/selection>` with the :guilabel:`Priority` widget selected by default and four priority values predefined. Consequently, the :guilabel:`Badge`, :guilabel:`Badges`, :guilabel:`Radio`, and :guilabel:`Selection` widgets have the same effects as described under :ref:`Selection <studio/fields/simple-fields/selection>`."
msgstr ""
#: ../../content/applications/studio/fields.rst:253
msgid "To change the number of available stars by adding or removing values, click :guilabel:`Edit Values`. Note that the first value is equal to 0 stars (i.e., when no selection is made), so having four values results in a three-star rating system, for example."
msgstr ""
#: ../../content/applications/studio/fields.rst:0
msgid "Example of a Priority field"
msgstr ""
#: ../../content/applications/studio/fields.rst:266
msgid "File (`binary`)"
msgstr ""
#: ../../content/applications/studio/fields.rst:268
msgid "The :guilabel:`File` field is used to upload any type of file, or sign a form (:guilabel:`Sign` widget)."
msgstr ""
#: ../../content/applications/studio/fields.rst:271
msgid ":guilabel:`Image`: users can upload an image file, which is then displayed in :ref:`Form view <studio/views/general/form>`. This has the same effect as using the :ref:`Image field <studio/fields/simple-fields/image>`."
msgstr ""
#: ../../content/applications/studio/fields.rst:274
msgid ":guilabel:`PDF Viewer`: users can upload a PDF file, which can be then browsed from the :ref:`Form view <studio/views/general/form>`."
msgstr ""
#: ../../content/applications/studio/fields.rst:276
msgid ":guilabel:`Sign`: users can electronically sign the form. This has the same effect as selecting the :ref:`Sign field <studio/fields/simple-fields/sign>`."
msgstr ""
#: ../../content/applications/studio/fields.rst:0
msgid "Examples of File fields with different widgets"
msgstr ""
#: ../../content/applications/studio/fields.rst:288
msgid "Image (`binary`)"
msgstr ""
#: ../../content/applications/studio/fields.rst:290
msgid "The :guilabel:`Image` field is used to upload an image and display it in :ref:`Form view <studio/views/general/form>`. This field type is a :ref:`File field <studio/fields/simple-fields/file>` with the :guilabel:`Image` widget selected by default. Consequently, the :guilabel:`File`, :guilabel:`PDF Viewer`, and :guilabel:`Sign` widgets have the same effects as described under :ref:`File <studio/fields/simple-fields/file>`."
msgstr ""
#: ../../content/applications/studio/fields.rst:297
msgid "To change the display size of uploaded images, select :guilabel:`Small`, :guilabel:`Medium`, or :guilabel:`Large` under the :guilabel:`Size` option."
msgstr ""
#: ../../content/applications/studio/fields.rst:303
msgid "Sign (`binary`)"
msgstr ""
#: ../../content/applications/studio/fields.rst:305
msgid "The :guilabel:`Sign` field is used to sign the form electronically. This field type is a :ref:`File field <studio/fields/simple-fields/file>` with the :guilabel:`Sign` widget selected by default. Consequently, the :guilabel:`File`, :guilabel:`Image`, and :guilabel:`PDF Viewer` widgets have the same effects as described under :ref:`File <studio/fields/simple-fields/file>`."
msgstr ""
#: ../../content/applications/studio/fields.rst:311
msgid "To give users the :guilabel:`Auto` option when having to draw their signature, select one of the available :guilabel:`Auto-complete with` fields (:ref:`Text <studio/fields/simple-fields/text>`, :ref:`Many2One <studio/fields/relational-fields/many2one>`, and :ref:`Related Field <studio/fields/relational-fields/related-field>` on the model only). The signature is automatically generated using the data from the selected field."
msgstr ""
#: ../../content/applications/studio/fields.rst:320
msgid "Relational fields"
msgstr ""
#: ../../content/applications/studio/fields.rst:322
msgid "Relational fields are used to link and display the data from records on another model."
msgstr ""
#: ../../content/applications/studio/fields.rst:330
msgid "Many2One (`many2one`)"
msgstr ""
#: ../../content/applications/studio/fields.rst:332
msgid "The :guilabel:`Many2One` field is used to link another record (from another model) to the record being edited. The record's name from the other model is then displayed on the record being edited."
msgstr ""
#: ../../content/applications/studio/fields.rst:336
msgid "On the *Sales Order* model, the :guilabel:`Customer` field is a :guilabel:`Many2One` field pointing at the *Contact* model. This allows **many** sales orders to be linked to **one** contact (customer)."
msgstr ""
#: ../../content/applications/studio/fields.rst:0
msgid "Diagram showing a many2one relationship"
msgstr ""
#: ../../content/applications/studio/fields.rst:345
msgid "To prevent users from creating a new record in the linked model, tick :guilabel:`Disable creation`."
msgstr ""
#: ../../content/applications/studio/fields.rst:347
msgid "To prevent users from opening records in a pop-up window, tick :guilabel:`Disable opening`."
msgstr ""
#: ../../content/applications/studio/fields.rst:348
msgid "To help users only select the right record, click on :guilabel:`Domain` to create a filter."
msgstr ""
#: ../../content/applications/studio/fields.rst:350
msgid ":guilabel:`Badge`: displays the value inside a rounded shape, similar to a tag. The value cannot be edited on the UI."
msgstr ""
#: ../../content/applications/studio/fields.rst:357
msgid "One2Many (`one2many`)"
msgstr ""
#: ../../content/applications/studio/fields.rst:359
msgid "The :guilabel:`One2Many` field is used to display the existing relations between a record on the current model and multiple records from another model."
msgstr ""
#: ../../content/applications/studio/fields.rst:363
msgid "You could add a :guilabel:`One2Many` field on the *Contact* model to look at **one** customer's **many** sales orders."
msgstr ""
#: ../../content/applications/studio/fields.rst:0
msgid "Diagram showing a one2many relationship"
msgstr ""
#: ../../content/applications/studio/fields.rst:371
msgid "To use a :guilabel:`One2Many` field, the two models must have been linked already using a :ref:`Many2One field <studio/fields/relational-fields/many2one>`. One2Many relations do not exist independently: a reverse-search of existing Many2One relations is performed."
msgstr ""
#: ../../content/applications/studio/fields.rst:378
msgid "Lines (`one2many`)"
msgstr ""
#: ../../content/applications/studio/fields.rst:380
msgid "The :guilabel:`Lines` field is used to create a table with rows and columns (e.g., the lines of products on a sales order)."
msgstr ""
#: ../../content/applications/studio/fields.rst:384
msgid "To modify the columns, click on the :guilabel:`Lines` field and then :guilabel:`Edit List View`. To edit the form that pops up when a user clicks on :guilabel:`Add a line`, click on :guilabel:`Edit Form View` instead."
msgstr ""
#: ../../content/applications/studio/fields.rst:0
msgid "Example of a Lines field"
msgstr ""
#: ../../content/applications/studio/fields.rst:397
msgid "Many2Many (`many2many`)"
msgstr ""
#: ../../content/applications/studio/fields.rst:399
msgid "The :guilabel:`Many2Many` field is used to link multiple records from another model to multiple records on the current model. Many2Many fields can use :guilabel:`Disable creation`, :guilabel:`Disable opening`, :guilabel:`Domain`, just like :ref:`Many2One fields <studio/fields/relational-fields/many2one>`."
msgstr ""
#: ../../content/applications/studio/fields.rst:405
msgid "On the *Task* model, the :guilabel:`Assignees` field is a :guilabel:`Many2Many` field pointing at the *Contact* model. This allows a single user to be assigned to **many** tasks and **many** users to be assigned to a single task."
msgstr ""
#: ../../content/applications/studio/fields.rst:0
msgid "Diagram showing many2many relationships"
msgstr ""
#: ../../content/applications/studio/fields.rst:413
msgid ":guilabel:`Checkboxes`: users can select several values using checkboxes."
msgstr ""
#: ../../content/applications/studio/fields.rst:414
msgid ":guilabel:`Tags`: users can select several values appearing in rounded shapes, also known as *tags*. This has the same effect as selecting the :ref:`Tags field <studio/fields/relational-fields/tags>`."
msgstr ""
#: ../../content/applications/studio/fields.rst:421
msgid "Tags (`many2many`)"
msgstr ""
#: ../../content/applications/studio/fields.rst:423
msgid "The :guilabel:`Tags` field is used to display several values from another model appearing in rounded shapes, also known as *tags*. This field type is a :ref:`Many2Many field <studio/fields/relational-fields/many2many>` with the :guilabel:`Tags` widget selected by default. Consequently, the :guilabel:`Checkboxes` and :guilabel:`Many2Many` widgets have the same effects as described under :ref:`Many2Many <studio/fields/relational-fields/many2many>`."
msgstr ""
#: ../../content/applications/studio/fields.rst:430
msgid "To display tags with different background colors, tick :guilabel:`Use colors`."
msgstr ""
#: ../../content/applications/studio/fields.rst:0
msgid "Example of a Tags field"
msgstr ""
#: ../../content/applications/studio/fields.rst:441
msgid "Related Field (`related`)"
msgstr ""
#: ../../content/applications/studio/fields.rst:443
msgid "A :guilabel:`Related Field` is not a relational field per se; no relationship is created between models. It uses an existing relationship to fetch and display information from another record."
msgstr ""
#: ../../content/applications/studio/fields.rst:447
msgid "To display the email address of a customer on the *Sales Order* model, use the :guilabel:`Related Field` `partner_id.email` by selecting :guilabel:`Customer` and then :guilabel:`Email`."
msgstr ""
#: ../../content/applications/studio/fields.rst:453
msgid "Properties"
msgstr ""
#: ../../content/applications/studio/fields.rst:455
msgid ":guilabel:`Invisible`: When it is not necessary for users to view a field on the UI, tick :guilabel:`Invisible`. It helps clear the UI by only showing the essential fields depending on a specific situation."
msgstr ""
#: ../../content/applications/studio/fields.rst:460
msgid "On the *Form* view of the *Contact* model, the :guilabel:`Title` field only appears when :guilabel:`Individual` is selected, as that field would not be helpful for a :guilabel:`Company` contact."
msgstr ""
#: ../../content/applications/studio/fields.rst:465
msgid "The :guilabel:`Invisible` attribute also applies to Studio. To view hidden fields inside Studio, click on a view's :guilabel:`View` tab and tick :guilabel:`Show Invisible Elements`."
msgstr ""
#: ../../content/applications/studio/fields.rst:469
msgid ":guilabel:`Required`: If a field should always be completed by the user before being able to proceed, tick :guilabel:`Required`."
msgstr ""
#: ../../content/applications/studio/fields.rst:471
msgid ":guilabel:`Read only`: If users should not be able to modify a field, tick :guilabel:`Read only`."
msgstr ""
#: ../../content/applications/studio/fields.rst:474
msgid "You can choose to apply these three properties only for specific records by clicking on :guilabel:`Conditional` and creating a filter."
msgstr ""
#: ../../content/applications/studio/fields.rst:477
msgid ":guilabel:`Label`: The :guilabel:`Label` is the field's name on the UI."
msgstr ""
#: ../../content/applications/studio/fields.rst:480
msgid "This is not the same name as used in the PostgreSQL database. To view and change the latter, activate the :ref:`Developer mode <developer-mode>`, and edit the :guilabel:`Technical Name`."
msgstr ""
#: ../../content/applications/studio/fields.rst:483
msgid ":guilabel:`Help Tooltip`: To explain the purpose of a field, write a description under :guilabel:`Help Tooltip`. It is displayed inside a tooltip box when hovering with your mouse over the field's label."
msgstr ""
#: ../../content/applications/studio/fields.rst:486
msgid ":guilabel:`Placeholder`: To provide an example of how a field should be completed, write it under :guilabel:`Placeholder`. It is displayed in light gray in lieu of the field's value."
msgstr ""
#: ../../content/applications/studio/fields.rst:488
msgid ":guilabel:`Widget`: To change the default appearance or functionality of a field, select one of the available widgets."
msgstr ""
#: ../../content/applications/studio/fields.rst:490
msgid ":guilabel:`Default value`: To add a default value to a field when a record is created, use :guilabel:`Default value`."
msgstr ""
#: ../../content/applications/studio/fields.rst:492
msgid ":guilabel:`Limit visibility to groups`: To limit which users can see the field, select a user access group."
msgstr ""
#: ../../content/applications/studio/models_modules_apps.rst:3
msgid "Models, modules, and apps"
msgstr ""
#: ../../content/applications/studio/models_modules_apps.rst:5
msgid "Models determine the logical structure of a database and how data is stored, organized, and manipulated. In other words, a model is a table of information that can be linked with other tables. A model usually represents a business concept, such as a *sales order*, *contact*, or *product*."
msgstr ""
#: ../../content/applications/studio/models_modules_apps.rst:9
msgid "Modules and apps contain various elements, such as models, views, data files, web controllers, and static web data."
msgstr ""
#: ../../content/applications/studio/models_modules_apps.rst:13
msgid "All apps are modules. Larger, standalone modules are typically referred to as apps, whereas other modules usually serve as add-ons to said apps."
msgstr ""
#: ../../content/applications/studio/models_modules_apps.rst:19
msgid "Suggested features"
msgstr ""
#: ../../content/applications/studio/models_modules_apps.rst:21
msgid "When you create a new model or app with Studio, you can choose to add up to 14 features to speed up the creation process. These features bundle fields, default settings, and views that are usually used together to provide some standard functionality. Most of these features can be added later on, but adding them from the start makes the model creation process much easier. Furthermore, these features interact together in some cases to increase their usefulness."
msgstr ""
#: ../../content/applications/studio/models_modules_apps.rst:28
msgid "Creating a model with the :ref:`studio/models-modules-apps/suggested-features/picture` and :ref:`studio/models-modules-apps/suggested-features/pipeline-stages` features enabled adds the image in the card layout of the :ref:`Kanban view <studio/views/multiple-records/kanban>`."
msgstr ""
#: ../../content/applications/studio/models_modules_apps.rst:0
msgid "Combination of the Picture and Pipeline stages features on the Kanban view"
msgstr ""
#: ../../content/applications/studio/models_modules_apps.rst:39
msgid "Contact details"
msgstr ""
#: ../../content/applications/studio/models_modules_apps.rst:41
msgid "Selecting :guilabel:`Contact details` adds to the :ref:`Form view <studio/views/general/form>` a :ref:`Many2One field <studio/fields/relational-fields/many2one>` linked to the *Contact* model and two of its :ref:`Related Fields <studio/fields/relational-fields/related-field>`: :guilabel:`Phone` and :guilabel:`Email`. The :guilabel:`Contact` field is also added to the :ref:`List view <studio/views/multiple-records/list>`, and the :ref:`Map view <studio/views/multiple-records/map>` is activated."
msgstr ""
#: ../../content/applications/studio/models_modules_apps.rst:0
msgid "Contact details feature on the Form view"
msgstr ""
#: ../../content/applications/studio/models_modules_apps.rst:57
msgid "User assignment"
msgstr ""
#: ../../content/applications/studio/models_modules_apps.rst:59
msgid "Selecting :guilabel:`User assignment` adds to the :ref:`Form view <studio/views/general/form>` a :ref:`Many2One field <studio/fields/relational-fields/many2one>` linked to the *Contact* model, with the following :guilabel:`Domain`: `Share User is not set` to only allow the selection of *Internal Users*. In addition, the :guilabel:`many2one_avatar_user` widget is used to display the user's avatar. The :guilabel:`Responsible` field is also added to the :ref:`List view <studio/views/multiple-records/list>`."
msgstr ""
#: ../../content/applications/studio/models_modules_apps.rst:0
msgid "User assignment feature on the Form view"
msgstr ""
#: ../../content/applications/studio/models_modules_apps.rst:75
msgid "Date & Calendar"
msgstr ""
#: ../../content/applications/studio/models_modules_apps.rst:77
msgid "Selecting :guilabel:`Date & Calendar` adds to the :ref:`Form view <studio/views/general/form>` a :ref:`Date field <studio/fields/simple-fields/date>` and activates the :ref:`Calendar view <studio/views/timeline/calendar>`."
msgstr ""
#: ../../content/applications/studio/models_modules_apps.rst:84
msgid "Date range & Gantt"
msgstr ""
#: ../../content/applications/studio/models_modules_apps.rst:86
msgid "Selecting :guilabel:`Date range & Gantt` adds to the :ref:`Form view <studio/views/general/form>` two :ref:`Date fields <studio/fields/simple-fields/date>` next to each other: one to set a start date, the other to set an end date, using the :guilabel:`daterange` widget, and activates the :ref:`Gantt view <studio/views/timeline/gantt>`."
msgstr ""
#: ../../content/applications/studio/models_modules_apps.rst:94
msgid "Pipeline stages"
msgstr ""
#: ../../content/applications/studio/models_modules_apps.rst:96
msgid "Selecting :guilabel:`Pipeline stages` activates the :ref:`Kanban view <studio/views/multiple-records/kanban>`, adds several fields such as :ref:`Priority <studio/fields/simple-fields/priority>` and :guilabel:`Kanban State`, and three stages: :guilabel:`New`, :guilabel:`In Progress`, and :guilabel:`Done`. The :guilabel:`Pipeline status bar` and the :guilabel:`Kanban State` field are added to the :ref:`Form view <studio/views/general/form>`. The :guilabel:`Color` field is added to the :ref:`List view <studio/views/multiple-records/list>`."
msgstr ""
#: ../../content/applications/studio/models_modules_apps.rst:105
msgid "The :guilabel:`Pipeline stages` feature can be added at a later stage."
msgstr ""
#: ../../content/applications/studio/models_modules_apps.rst:110
msgid "Tags"
msgstr ""
#: ../../content/applications/studio/models_modules_apps.rst:112
msgid "Selecting :guilabel:`Tags` adds to the :ref:`studio/views/general/form` and :ref:`studio/views/multiple-records/list` views a :ref:`Tags field <studio/fields/relational-fields/tags>`, creating a *Tag* model with preconfigured access rights in the process."
msgstr ""
#: ../../content/applications/studio/models_modules_apps.rst:120
msgid "Picture"
msgstr ""
#: ../../content/applications/studio/models_modules_apps.rst:122
msgid "Selecting :guilabel:`Picture` adds to the top-right of the :ref:`Form view <studio/views/general/form>` an :ref:`Image field <studio/fields/simple-fields/image>`."
msgstr ""
#: ../../content/applications/studio/models_modules_apps.rst:126
msgid "The :guilabel:`Picture` feature can be added at a later stage."
msgstr ""
#: ../../content/applications/studio/models_modules_apps.rst:131
msgid "Lines"
msgstr ""
#: ../../content/applications/studio/models_modules_apps.rst:133
msgid "Selecting :guilabel:`Lines`: adds to the :ref:`Form view <studio/views/general/form>` a :ref:`Lines field <studio/fields/relational-fields/lines>` inside a :guilabel:`Tab` component."
msgstr ""
#: ../../content/applications/studio/models_modules_apps.rst:139
msgid "Notes"
msgstr ""
#: ../../content/applications/studio/models_modules_apps.rst:141
msgid "Selecting :guilabel:`Notes` adds to the :ref:`Form view <studio/views/general/form>` an :ref:`Html field <studio/fields/simple-fields/html>` using the full width of the form."
msgstr ""
#: ../../content/applications/studio/models_modules_apps.rst:147
msgid "Monetary value"
msgstr ""
#: ../../content/applications/studio/models_modules_apps.rst:149
msgid "Selecting :guilabel:`Monetary value` adds to the :ref:`studio/views/general/form` and :ref:`studio/views/multiple-records/list` views a :ref:`Monetary field <studio/fields/simple-fields/monetary>`. The :ref:`studio/views/reporting/graph` and :ref:`studio/views/reporting/pivot` views are also activated."
msgstr ""
#: ../../content/applications/studio/models_modules_apps.rst:155
msgid "A *Currency* field is added and hidden from the view."
msgstr ""
#: ../../content/applications/studio/models_modules_apps.rst:160
msgid "Company"
msgstr ""
#: ../../content/applications/studio/models_modules_apps.rst:162
msgid "Selecting :guilabel:`Company` adds to the :ref:`studio/views/general/form` and :ref:`studio/views/multiple-records/list` views a :ref:`Many2One field <studio/fields/relational-fields/many2one>` linked to the *Company* model."
msgstr ""
#: ../../content/applications/studio/models_modules_apps.rst:167
msgid "This is only useful if you work in a multi-company environment."
msgstr ""
#: ../../content/applications/studio/models_modules_apps.rst:172
msgid "Custom Sorting"
msgstr ""
#: ../../content/applications/studio/models_modules_apps.rst:174
msgid "Selecting :guilabel:`Custom Sorting` adds to the :ref:`List view <studio/views/multiple-records/list>` a drag handle icon to manually reorder records."
msgstr ""
#: ../../content/applications/studio/models_modules_apps.rst:0
msgid "Custom Sorting feature on the List view"
msgstr ""
#: ../../content/applications/studio/models_modules_apps.rst:186
msgid "Chatter"
msgstr ""
#: ../../content/applications/studio/models_modules_apps.rst:188
msgid "Selecting :guilabel:`Chatter` adds to the :ref:`Form view <studio/views/general/form>` Chatter functionalities (sending messages, logging notes, and scheduling activities)."
msgstr ""
#: ../../content/applications/studio/models_modules_apps.rst:192
msgid "The :guilabel:`Chatter` feature can be added at a later stage."
msgstr ""
#: ../../content/applications/studio/models_modules_apps.rst:0
msgid "Chatter feature on the Form view"
msgstr ""
#: ../../content/applications/studio/models_modules_apps.rst:203
msgid "Archiving"
msgstr ""
#: ../../content/applications/studio/models_modules_apps.rst:205
msgid "Selecting :guilabel:`Archiving` adds to the :ref:`studio/views/general/form` and :ref:`studio/views/multiple-records/list` views the :guilabel:`Archive` action and hides archived records from searches and views by default."
msgstr ""
#: ../../content/applications/studio/models_modules_apps.rst:212
msgid "Export and import customizations"
msgstr ""
#: ../../content/applications/studio/models_modules_apps.rst:214
msgid "When you do any customization with Studio, a new module named :guilabel:`Studio customizations` is added to your database."
msgstr ""
#: ../../content/applications/studio/models_modules_apps.rst:217
msgid "To export these customizations, go to :menuselection:`Main dashboard --> Studio --> Customizations --> Export` to download a ZIP file containing all customizations."
msgstr ""
#: ../../content/applications/studio/models_modules_apps.rst:220
msgid "To import and install these customizations in another database, connect to the destination database and go to :menuselection:`Main dashboard --> Studio --> Customizations --> Import`, then upload the exported ZIP file before clicking on the :guilabel:`Import` button."
msgstr ""
#: ../../content/applications/studio/models_modules_apps.rst:225
msgid "Before importing, make sure the destination database contains the same apps and modules as the source database. Studio does not add the underlying modules as dependencies of the exported module."
msgstr ""
#: ../../content/applications/studio/pdf_reports.rst:3
msgid "PDF reports"
msgstr ""
#: ../../content/applications/studio/pdf_reports.rst:5
msgid "With Studio, you can :ref:`edit existing PDF reports <studio/pdf-reports/edit>` (e.g., invoices, quotations, etc.) or :ref:`create new ones <studio/pdf-reports/edit>`."
msgstr ""
#: ../../content/applications/studio/pdf_reports.rst:11
msgid "Default layout"
msgstr ""
#: ../../content/applications/studio/pdf_reports.rst:13
msgid "The default layout of reports is managed outside Studio. Go to :menuselection:`Settings`, then, in the :guilabel:`Companies` section, click :guilabel:`Configure Document Layout`. Layout settings are company-specific but apply to all reports."
msgstr ""
#: ../../content/applications/studio/pdf_reports.rst:18
msgid "You can see how the different settings affect the report layout in the report preview on the right, or download a sample invoice PDF by clicking :guilabel:`Download PDF Preview`."
msgstr ""
#: ../../content/applications/studio/pdf_reports.rst:21
msgid "Use the following settings:"
msgstr ""
#: ../../content/applications/studio/pdf_reports.rst:25
msgid ":guilabel:`Layout`: Four layouts are available:"
msgstr ""
#: ../../content/applications/studio/pdf_reports.rst:29
msgid "Light"
msgstr ""
#: ../../content/applications/studio/pdf_reports.rst:0
msgid "Light report layout sample"
msgstr ""
#: ../../content/applications/studio/pdf_reports.rst:34
msgid "Boxed"
msgstr ""
#: ../../content/applications/studio/pdf_reports.rst:0
msgid "Boxed report layout sample"
msgstr ""
#: ../../content/applications/studio/pdf_reports.rst:39
msgid "Bold"
msgstr ""
#: ../../content/applications/studio/pdf_reports.rst:0
msgid "Bold report layout sample"
msgstr ""
#: ../../content/applications/studio/pdf_reports.rst:44
msgid "Striped"
msgstr ""
#: ../../content/applications/studio/pdf_reports.rst:0
msgid "Striped report layout sample"
msgstr ""
#: ../../content/applications/studio/pdf_reports.rst:51
msgid ":guilabel:`Font`: Seven fonts are available: Lato, Roboto, Open Sans, Montserrat, Oswald, Raleway, and Tajawal (which supports Arabic and Latin scripts). Go to the `Google Fonts website <https://fonts.google.com/>`_ to preview them."
msgstr ""
#: ../../content/applications/studio/pdf_reports.rst:57
msgid ":guilabel:`Company logo`: Click the :guilabel:`Edit` button to upload or change the logo. This adds the logo to the company’s record on the *Company* model, which you can access by going to :menuselection:`Settings` and then clicking :guilabel:`Update Info` in the :guilabel:`Companies` section."
msgstr ""
#: ../../content/applications/studio/pdf_reports.rst:64
msgid ":guilabel:`Colors`: Change the primary and secondary colors used to structure reports. The default colors are automatically generated based on the colors of the logo."
msgstr ""
#: ../../content/applications/studio/pdf_reports.rst:69
msgid ":guilabel:`Layout background`: The following backgrounds are available:"
msgstr ""
#: ../../content/applications/studio/pdf_reports.rst:71
msgid ":guilabel:`Blank`: nothing is displayed."
msgstr ""
#: ../../content/applications/studio/pdf_reports.rst:72
msgid ":guilabel:`Geometric`: an image featuring geometric shapes is displayed in the background."
msgstr ""
#: ../../content/applications/studio/pdf_reports.rst:73
msgid ":guilabel:`Custom`: upload a custom background image."
msgstr ""
#: ../../content/applications/studio/pdf_reports.rst:77
msgid ":guilabel:`Company tagline`: This is displayed in the header of :ref:`external reports <studio/pdf-reports/header-footer/external>`. You can add multiple lines of text."
msgstr ""
#: ../../content/applications/studio/pdf_reports.rst:82
msgid ":guilabel:`Company details`: These are displayed in the header of :ref:`external reports <studio/pdf-reports/header-footer/external>`. You can add multiple lines of text."
msgstr ""
#: ../../content/applications/studio/pdf_reports.rst:87
msgid ":guilabel:`Footer`: This text is used in the footer of :ref:`external reports <studio/pdf-reports/header-footer/external>`. You can add multiple lines of text. You can also edit the footer using the :ref:`report editor <studio/pdf-reports/edit>`."
msgstr ""
#: ../../content/applications/studio/pdf_reports.rst:93
msgid ":guilabel:`Paper format`: to define the default paper size of reports. You can select :guilabel:`A4` (21 cm x 29.7 cm), :guilabel:`US Letter` (21.59 cm x 27.54 cm), or :guilabel:`QR codes page`. This can also be defined for individual reports in the :guilabel:`Paper format` field in :ref:`Studio <studio/pdf-reports/create>`."
msgstr ""
#: ../../content/applications/studio/pdf_reports.rst:101
msgid "Creating new PDF reports"
msgstr ""
#: ../../content/applications/studio/pdf_reports.rst:103
msgid "To create a new report for a model, access the model, click the **Toggle Studio** button, then click :guilabel:`Reports`. Click :guilabel:`New` and, in the popup window that opens, select the type of report. This is solely used to determine what is displayed in the header and footer:"
msgstr ""
#: ../../content/applications/studio/pdf_reports.rst:109
msgid ":guilabel:`External`:"
msgstr ""
#: ../../content/applications/studio/pdf_reports.rst:111
msgid "The header displays the company's :ref:`logo <studio/pdf-reports/default-layout/logo>`, :ref:`tagline <studio/pdf-reports/default-layout/tagline>`, and :ref:`details <studio/pdf-reports/default-layout/details>`."
msgstr ""
#: ../../content/applications/studio/pdf_reports.rst:114
msgid "The footer displays the values set in the :ref:`Footer <studio/pdf-reports/default-layout/footer>` field and the page number."
msgstr ""
#: ../../content/applications/studio/pdf_reports.rst:117
msgid ":guilabel:`Internal`: The header displays the user's current date and time, :guilabel:`Company Name`, and page number. There is no footer."
msgstr ""
#: ../../content/applications/studio/pdf_reports.rst:120
msgid ":guilabel:`Blank`: There is neither a header nor a footer. Click in the upper left corner of the page to edit the report."
msgstr ""
#: ../../content/applications/studio/pdf_reports.rst:123
msgid "Once you have created the report, you can start :ref:`editing it <studio/pdf-reports/edit>`."
msgstr ""
#: ../../content/applications/studio/pdf_reports.rst:128
msgid "Editing PDF reports"
msgstr ""
#: ../../content/applications/studio/pdf_reports.rst:130
msgid "To access the reports available for a model, access the model (e.g., sales orders), click the **Toggle Studio** button, then click :guilabel:`Reports`. Select an existing report to open it or :ref:`create a new one <studio/pdf-reports/create>`."
msgstr ""
#: ../../content/applications/studio/pdf_reports.rst:135
msgid "Alternatively, you can also open Studio, click :guilabel:`Reports`, and search for a specific report or model."
msgstr ""
#: ../../content/applications/studio/pdf_reports.rst:139
msgid "It is strongly recommended to **duplicate** the standard report and perform changes in the duplicated version. To duplicate a report, hover the mouse pointer on the top right corner of the report, click the vertical ellipsis icon (:guilabel:`⋮`), and then select :guilabel:`Duplicate`."
msgstr ""
#: ../../content/applications/studio/pdf_reports.rst:0
msgid "Duplicating a PDF report"
msgstr ""
#: ../../content/applications/studio/pdf_reports.rst:148
msgid "Options"
msgstr ""
#: ../../content/applications/studio/pdf_reports.rst:150
msgid "Once you've selected or created a report, you can use the options in the left part of the screen to:"
msgstr ""
#: ../../content/applications/studio/pdf_reports.rst:152
msgid "Change the :guilabel:`Report name`. The new name is applied everywhere (in Studio, under the :guilabel:`Print` button, and in the PDF file name)."
msgstr ""
#: ../../content/applications/studio/pdf_reports.rst:154
msgid "Modify the :guilabel:`Paper format`. If no value is selected, the format defined in the :ref:`default layout <studio/pdf-reports/default-layout/paper>` is used."
msgstr ""
#: ../../content/applications/studio/pdf_reports.rst:156
msgid ":guilabel:`Show in print menu`: to add the report in the :guilabel:`Print` menu available from the record."
msgstr ""
#: ../../content/applications/studio/pdf_reports.rst:158
msgid ":guilabel:`Reload from attachment`: to save the report as an attachment on the record the first time it is generated and reload the original version of the report any subsequent time. This is legally required for invoices and is mainly used in this case."
msgstr ""
#: ../../content/applications/studio/pdf_reports.rst:161
msgid ":guilabel:`Limit visibility to groups`: to limit the availability of the PDF report to specific :doc:`user groups <../general/users/access_rights>`."
msgstr ""
#: ../../content/applications/studio/pdf_reports.rst:163
msgid ":guilabel:`Edit sources`: to modify the report directly in the :ref:`XML file <studio/pdf-reports/XML-editing>`."
msgstr ""
#: ../../content/applications/studio/pdf_reports.rst:165
msgid ":guilabel:`Reset report`: to discard all changes made to the report and reset it to its standard version."
msgstr ""
#: ../../content/applications/studio/pdf_reports.rst:167
msgid ":guilabel:`Print preview`: to generate and download a report preview."
msgstr ""
#: ../../content/applications/studio/pdf_reports.rst:170
msgid "Report editor"
msgstr ""
#: ../../content/applications/studio/pdf_reports.rst:172
msgid "The report editor allows you to modify the formatting and contents of the report."
msgstr ""
#: ../../content/applications/studio/pdf_reports.rst:175
msgid "You can :guilabel:`Undo` or :guilabel:`Redo` changes using the related buttons or the shortcuts `CTRL Z` and `CTRL Y`."
msgstr ""
#: ../../content/applications/studio/pdf_reports.rst:178
msgid "Changes are saved automatically when you leave the report or manually using the :guilabel:`Save` button."
msgstr ""
#: ../../content/applications/studio/pdf_reports.rst:181
msgid "You can reset the report to its standard version by clicking the :guilabel:`Reset report` button in the left part of the screen."
msgstr ""
#: ../../content/applications/studio/pdf_reports.rst:185
msgid "Editing the header and footer of a report impacts all standard and custom reports."
msgstr ""
#: ../../content/applications/studio/pdf_reports.rst:188
msgid "Conditional blocks"
msgstr ""
#: ../../content/applications/studio/pdf_reports.rst:190
msgid "The dashed rectangles represent **conditional blocks** (*if/else* statements). These are used to show/hide content based on specific conditions. Click on the block to view the conditions."
msgstr ""
#: ../../content/applications/studio/pdf_reports.rst:-1
msgid "View conditions applied to a block."
msgstr ""
#: ../../content/applications/studio/pdf_reports.rst:196
msgid "Select a value to preview its corresponding output and edit it if necessary."
msgstr ""
#: ../../content/applications/studio/pdf_reports.rst:-1
msgid "Preview the output of another condition."
msgstr ""
#: ../../content/applications/studio/pdf_reports.rst:202
msgid "Conditions can only be edited in :ref:`XML <studio/pdf-reports/XML-editing>`."
msgstr ""
#: ../../content/applications/studio/pdf_reports.rst:205
msgid "Other content"
msgstr ""
#: ../../content/applications/studio/pdf_reports.rst:207
msgid "There are two types of text content in reports:"
msgstr ""
#: ../../content/applications/studio/pdf_reports.rst:209
msgid "Static text, i.e., the text that's not highlighted in blue, which can be modified directly in the editor."
msgstr ""
#: ../../content/applications/studio/pdf_reports.rst:211
msgid "Dynamic text, i.e., the text that's highlighted in blue, which is replaced by field values when the report is generated, e.g., the SO number or the quotation date."
msgstr ""
#: ../../content/applications/studio/pdf_reports.rst:214
msgid "You can add content (e.g., fields, lists, tables, images, banners, etc.) to the report using commands. Type `/` to open the :ref:`powerbox <knowledge/powerbox>`, then type the command's name or select it from the list."
msgstr ""
#: ../../content/applications/studio/pdf_reports.rst:218
msgid "To add static text to the report, type the text where you want it."
msgstr ""
#: ../../content/applications/studio/pdf_reports.rst:220
msgid "For more advanced changes, you can :ref:`edit the report in the XML directly <studio/pdf-reports/XML-editing>`."
msgstr ""
#: ../../content/applications/studio/pdf_reports.rst:226
msgid "Add a field"
msgstr ""
#: ../../content/applications/studio/pdf_reports.rst:228
msgid "To add a field, type `/` and select the :guilabel:`Field` command. In the list that opens, select or search for the field; click the right arrow next to the field name to access the list of related fields if needed. Then, specify the default value and press `Enter`."
msgstr ""
#: ../../content/applications/studio/pdf_reports.rst:-1
msgid "Select a related field."
msgstr ""
#: ../../content/applications/studio/pdf_reports.rst:236
msgid "Add a data table"
msgstr ""
#: ../../content/applications/studio/pdf_reports.rst:238
msgid "Data tables are used to display :ref:`relational fields <studio/fields/relational-fields>`. To add a data table, type `/`, select the :guilabel:`Dynamic Table` command, and select the relation to be displayed in the table."
msgstr ""
#: ../../content/applications/studio/pdf_reports.rst:243
msgid "Only relations of type `one2many` or `many2many` can be displayed as data tables."
msgstr ""
#: ../../content/applications/studio/pdf_reports.rst:245
msgid "Once the table has been added, you can add columns using the table tools. Position the cursor on top of the column, then click the purple rectangle and select an option."
msgstr ""
#: ../../content/applications/studio/pdf_reports.rst:-1
msgid "Add a column in a dynamic table."
msgstr ""
#: ../../content/applications/studio/pdf_reports.rst:251
msgid "You can then insert the :ref:`field of your choice <studio/pdf-reports/add-field>` in the columns. The dialog box that opens shows the source object for the field (e.g., the *Tag* model) and the list of available fields."
msgstr ""
#: ../../content/applications/studio/pdf_reports.rst:-1
msgid "List of available fields for the Tag model."
msgstr ""
#: ../../content/applications/studio/pdf_reports.rst:259
msgid "The default row automatically iterates over the field's content, generating a row on the report for each field value (e.g., one row per tag). You can add static content rows above or below the generated rows using the table tools."
msgstr ""
#: ../../content/applications/studio/pdf_reports.rst:262
msgid "You can also add data tables by :ref:`modifying the report's XML <studio/pdf-reports/XML-editing>`."
msgstr ""
#: ../../content/applications/studio/pdf_reports.rst:265
msgid "Formatting"
msgstr ""
#: ../../content/applications/studio/pdf_reports.rst:267
msgid "To format text in the report, select it, then format it using the options in the :ref:`knowledge/text-editor`."
msgstr ""
#: ../../content/applications/studio/pdf_reports.rst:0
msgid "Format text using the text editor."
msgstr ""
#: ../../content/applications/studio/pdf_reports.rst:276
msgid "Editing the report's XML"
msgstr ""
#: ../../content/applications/studio/pdf_reports.rst:279
msgid "Modifying the XML directly may result in report issues during :doc:`upgrades <../../../administration/upgrade>`. If this happens, simply copy your changes from the old database into your upgraded database."
msgstr ""
#: ../../content/applications/studio/pdf_reports.rst:283
msgid "To edit the report's XML, click :guilabel:`Edit sources` in the left pane."
msgstr ""
#: ../../content/applications/studio/pdf_reports.rst:286
msgid "Examples"
msgstr ""
#: ../../content/applications/studio/pdf_reports.rst:290
msgid "Sometimes, tables are not properly recognized as such due to complex structures. In those cases, you can still modify them manually in the report XML. For example, with a sales order, you can find the following structure in the XML (simplified for documentation purposes):"
msgstr ""
#: ../../content/applications/studio/pdf_reports.rst:318
msgid "To modify a table, you must ensure that each row has the same number of data cells. For example, in the case above, you need to add a cell in the header section (with e.g., the column title) and another one in the body section with the field content (usually, with a `t-out` or `t-field` directive)."
msgstr ""
#: ../../content/applications/studio/pdf_reports.rst:344
msgid "Cells can span multiple rows or columns. For more information, go to the `Mozilla Developer Network website <https://developer.mozilla.org/en-US/docs/Learn/HTML/Tables/Basics>`_."
msgstr ""
#: ../../content/applications/studio/pdf_reports.rst:347
msgid "For example, you can modify the **Quotation/Order** report to add a column to display the product category in the main table:"
msgstr ""
#: ../../content/applications/studio/pdf_reports.rst:0
msgid "Add a Product Category column in a SO."
msgstr ""
#: ../../content/applications/studio/pdf_reports.rst:376
msgid "To add a table in XML, you need to know the names of the fields and objects you wish to access and display. As an example, let's add a table that details the tags on a sales order:"
msgstr ""
#: ../../content/applications/studio/pdf_reports.rst:0
msgid "Add a data table in XML"
msgstr ""
#: ../../content/applications/studio/pdf_reports.rst:407
msgid "When adding tables manually, style them using `Bootstrap classes <https://getbootstrap.com/docs/5.1/content/tables>`_, like the `table` class included in the example above."
msgstr ""
#: ../../content/applications/studio/pdf_reports.rst:413
msgid "If you want to show/hide content based on specific conditions, you can manually add `if/else` control statements in the report XML."
msgstr ""
#: ../../content/applications/studio/pdf_reports.rst:416
msgid "For example, if you want to hide a custom data table if there are no tags, you can use the `t-if` attribute to define the condition, which is then evaluated as `True` or `False`. The table will not be displayed if there are no tags in the quotation."
msgstr ""
#: ../../content/applications/studio/pdf_reports.rst:445
msgid "If you want to display another block in case the `t-if` statement is evaluated as `False`, you can specify it using the `t-else` statement. The `t-else` block must directly follow the `t-if` block in the document structure. There is no need to specify any condition in the `t-else` attribute. As an example, let's show a quick message explaining that there are no tags on the quotation:"
msgstr ""
#: ../../content/applications/studio/pdf_reports.rst:477
msgid "By using the `t-if/t-else` notation, the report editor recognizes that these sections are mutually exclusive and should be displayed as conditional blocks:"
msgstr ""
#: ../../content/applications/studio/pdf_reports.rst:0
msgid "Output preview if there are tags."
msgstr ""
#: ../../content/applications/studio/pdf_reports.rst:483
msgid "You can switch conditions using the editor to preview their output:"
msgstr ""
#: ../../content/applications/studio/pdf_reports.rst:0
msgid "Output preview if there are no tags."
msgstr ""
#: ../../content/applications/studio/pdf_reports.rst:488
msgid "If you wish to have multiple options, you can also use `t-elif` directives to add intermediary conditions. For example, this is how the title of sales order reports changes based on the condition of the underlying document."
msgstr ""
#: ../../content/applications/studio/pdf_reports.rst:501
msgid "The title *Pro-Forma Invoice* is used depending on some contextual conditions. If these conditions are not met and the state of the document is either `draft` or `sent`, then *Quotation* is used. If none of those conditions are met, the report's title is *Order*."
msgstr ""
#: ../../content/applications/studio/pdf_reports.rst:507
msgid "Working with images in a report can be challenging, as precise control over image size and behavior is not always obvious. You can insert image fields using the report editor (:ref:`by using the /Field command <studio/pdf-reports/add-field>`), but inserting them in XML using the `t-field` directive and accompanying `t-options` attributes provides better sizing and positioning control."
msgstr ""
#: ../../content/applications/studio/pdf_reports.rst:513
msgid "For example, the following code outputs the field `image_128` of the line's product as a 64px-wide image (with an automatic height based on the image's aspect ratio)."
msgstr ""
#: ../../content/applications/studio/pdf_reports.rst:520
msgid "The following options are available for image widgets:"
msgstr ""
#: ../../content/applications/studio/pdf_reports.rst:522
msgid "`width`: width of the image, usually in pixels or CSS length units (e.g., `rem`) (leave empty for auto-width)."
msgstr ""
#: ../../content/applications/studio/pdf_reports.rst:524
msgid "`height`: height of the image, usually in pixels or CSS length units (e.g., `rem`) (leave empty for auto-height)."
msgstr ""
#: ../../content/applications/studio/pdf_reports.rst:526
msgid "`class`: CSS classes applied on the `img` tag; `Bootstrap classes <https://getbootstrap.com/docs/5.1/content/tables>`_ are available."
msgstr ""
#: ../../content/applications/studio/pdf_reports.rst:528
msgid "`alt`: alternative text of the image"
msgstr ""
#: ../../content/applications/studio/pdf_reports.rst:529
msgid "`style`: style attribute; it allows you to override styles more freely than with `Bootstrap classes <https://getbootstrap.com/docs/5.1/content/tables>`_."
msgstr ""
#: ../../content/applications/studio/pdf_reports.rst:532
msgid "These attributes must contain strings, i.e., text enclosed within quotes within quotes, e.g., `t-options-width=\"'64px'\"` (or, alternatively, a valid Python expression)."
msgstr ""
#: ../../content/applications/studio/pdf_reports.rst:536
msgid "The image widget cannot be used on an `img` tag. Instead, set the `t-field` directive on a `span` (for inline content) or `div` (for block content) node."
msgstr ""
#: ../../content/applications/studio/pdf_reports.rst:539
msgid "For example, let's add a column with the product image in the quotation table:"
msgstr ""
#: ../../content/applications/studio/pdf_reports.rst:567
msgid "The `t-options-width` attribute restricts the image width to 64 pixels, and the Bootstrap classes used in `t-options-class` create a thumbnail-like border with rounded corners and a shadow."
msgstr ""
#: ../../content/applications/studio/pdf_reports.rst:0
msgid "Add a column with the product image in the quotation table."
msgstr ""
#: ../../content/applications/studio/views.rst:3
msgid "Views"
msgstr ""
#: ../../content/applications/studio/views.rst:5
msgid "Views are the interface that allows displaying the data contained in a :doc:`model <models_modules_apps>`. One model can have several views, which are simply different ways to show the same data. In Studio, views are organized into four categories: :ref:`general <studio/views/general>`, :ref:`multiple records <studio/views/multiple-records>`, :ref:`timeline <studio/views/timeline>`, and :ref:`reporting <studio/views/reporting>`."
msgstr ""
#: ../../content/applications/studio/views.rst:12
msgid "To change the default view of a model, :ref:`access Studio <studio/access>`, go to :guilabel:`Views`, click the :icon:`fa-ellipsis-v` (:guilabel:`ellipsis`) icon next to the desired view, and click :guilabel:`Set as Default`."
msgstr ""
#: ../../content/applications/studio/views.rst:15
msgid "You can modify views using the built-in XML editor: Activate the :ref:`Developer mode <developer-mode>`, go to the view you want to edit, select the :guilabel:`View` tab, and click :guilabel:`</> XML`."
msgstr ""
#: ../../content/applications/studio/views.rst:20
msgid "If you are editing a view using the XML editor, avoid making changes directly to standard and inherited views, as these would be reset and lost during updates or module upgrades. Always make sure you select the right Studio inherited views: When you modify a view in Studio by dragging and dropping a new field, for example, a specific Studio inherited view and its corresponding XPath, which defines the modified part of the view, are automatically generated."
msgstr ""
#: ../../content/applications/studio/views.rst:30
msgid "General views"
msgstr ""
#: ../../content/applications/studio/views.rst:33
#: ../../content/applications/studio/views.rst:106
#: ../../content/applications/studio/views.rst:207
#: ../../content/applications/studio/views.rst:322
msgid "The settings described below are found under the view's :guilabel:`View` tab unless specified otherwise."
msgstr ""
#: ../../content/applications/studio/views.rst:39
msgid "Form"
msgstr ""
#: ../../content/applications/studio/views.rst:41
msgid "The :guilabel:`Form` :icon:`fa-address-card` view is used when creating and editing records, such as contacts, sales orders, products, etc."
msgstr ""
#: ../../content/applications/studio/views.rst:44
msgid "To structure a form, drag and drop the :guilabel:`Tabs and Columns` element found under the :guilabel:`+ Add` tab."
msgstr ""
#: ../../content/applications/studio/views.rst:46
#: ../../content/applications/studio/views.rst:139
msgid "To prevent users from creating, editing, or deleting records, untick :guilabel:`Can Create`, :guilabel:`Can Edit`, or :guilabel:`Can Delete`."
msgstr ""
#: ../../content/applications/studio/views.rst:48
msgid "To add a button, click :guilabel:`Add a button` at the top of the form, enter a :guilabel:`Label`, and select the button's action:"
msgstr ""
#: ../../content/applications/studio/views.rst:51
#: ../../content/applications/studio/views.rst:155
msgid ":guilabel:`Run a Server Action`: select the :ref:`server action <reference/actions/server>` to be executed from the dropdown list;"
msgstr ""
#: ../../content/applications/studio/views.rst:53
#: ../../content/applications/studio/views.rst:157
msgid ":guilabel:`Call a method`: specify an existing Python method already defined in Odoo."
msgstr ""
#: ../../content/applications/studio/views.rst:55
msgid "To change a button's label or style, click the button and edit its :guilabel:`Label` or :guilabel:`Class` (either `btn-primary` or `btn-secondary`) in the :guilabel:`Properties` tab."
msgstr ""
#: ../../content/applications/studio/views.rst:57
msgid "To add a smart button, click the :icon:`fa-plus-square` (:guilabel:`plus`) icon in the top-right corner of the form. Enter a :guilabel:`Label`, choose an :guilabel:`Icon`, and select a :ref:`related field <studio/fields/relational-fields/related-field>`."
msgstr ""
#: ../../content/applications/studio/views.rst:0
msgid "Sales order model's Form view"
msgstr ""
#: ../../content/applications/studio/views.rst:69
msgid "Activity"
msgstr ""
#: ../../content/applications/studio/views.rst:71
msgid "The :guilabel:`Activity` :icon:`fa-clock-o` view is used to schedule and have an overview of activities (emails, calls, etc.) linked to records."
msgstr ""
#: ../../content/applications/studio/views.rst:75
msgid "This view can only be modified within Studio by editing the XML code."
msgstr ""
#: ../../content/applications/studio/views.rst:0
msgid "Lead/Opportunity model's Activity view"
msgstr ""
#: ../../content/applications/studio/views.rst:85
msgid "Search"
msgstr ""
#: ../../content/applications/studio/views.rst:87
msgid "The :guilabel:`Search` :icon:`oi-search` view is added on top of other views to filter, group, and search records."
msgstr ""
#: ../../content/applications/studio/views.rst:90
msgid "To add custom :guilabel:`Filters` and structure them using :guilabel:`Separators`, go to the :guilabel:`+ Add` tab and drag and drop them under :guilabel:`Filters`."
msgstr ""
#: ../../content/applications/studio/views.rst:92
msgid "To add an existing field under the search dropdown menu, go to the :guilabel:`+ Add` tab and drag and drop it under :guilabel:`Autocompletion Fields`."
msgstr ""
#: ../../content/applications/studio/views.rst:0
msgid "Project model's Search view on the Kanban view"
msgstr ""
#: ../../content/applications/studio/views.rst:103
msgid "Multiple records views"
msgstr ""
#: ../../content/applications/studio/views.rst:112
msgid "Kanban"
msgstr ""
#: ../../content/applications/studio/views.rst:114
msgid "The :guilabel:`Kanban` :icon:`oi-view-kanban` view is often used to support business flows by moving records across stages or as an alternative way to display records inside *cards*."
msgstr ""
#: ../../content/applications/studio/views.rst:118
msgid "If the :guilabel:`Kanban` view exists, it is used by default to display data on mobile devices instead of the :ref:`List view <studio/views/multiple-records/list>`."
msgstr ""
#: ../../content/applications/studio/views.rst:121
msgid "To prevent users from creating new records, untick :guilabel:`Can Create`."
msgstr ""
#: ../../content/applications/studio/views.rst:122
msgid "To create records directly within the view, in a minimalistic form, enable :guilabel:`Quick Create`."
msgstr ""
#: ../../content/applications/studio/views.rst:124
#: ../../content/applications/studio/views.rst:151
msgid "To set a default grouping for records, select a field under :guilabel:`Default Group By`."
msgstr ""
#: ../../content/applications/studio/views.rst:0
msgid "Project model's Kanban view"
msgstr ""
#: ../../content/applications/studio/views.rst:134
msgid "List"
msgstr ""
#: ../../content/applications/studio/views.rst:136
msgid "The :guilabel:`List` :icon:`oi-view-list` view is used to overview many records at once, look for records, and edit simple records."
msgstr ""
#: ../../content/applications/studio/views.rst:141
msgid "To create and edit records directly within the view, select either :guilabel:`Add record at the bottom`, :guilabel:`Add record on top` or :guilabel:`Open form view` under :guilabel:`When Creating Record`."
msgstr ""
#: ../../content/applications/studio/views.rst:146
msgid "This prevents users from opening records in :ref:`Form view <studio/views/general/form>` from the :guilabel:`List` view."
msgstr ""
#: ../../content/applications/studio/views.rst:149
msgid "To edit several records at once, tick :guilabel:`Enable Mass Editing`."
msgstr ""
#: ../../content/applications/studio/views.rst:150
msgid "To change the way records are sorted by default, select a field under :guilabel:`Sort By`."
msgstr ""
#: ../../content/applications/studio/views.rst:152
msgid "To add a button, click :guilabel:`Add a button` at the top of the list, enter a :guilabel:`Label`, and select the button's action:"
msgstr ""
#: ../../content/applications/studio/views.rst:160
msgid "To add a :icon:`oi-draggable` (:guilabel:`drag handle`) icon to reorder records manually, add an :ref:`Integer field <studio/fields/simple-fields/integer>` with the :guilabel:`Handle` widget."
msgstr ""
#: ../../content/applications/studio/views.rst:0
msgid "Drag handle icon enabling to sort records manually in List view"
msgstr ""
#: ../../content/applications/studio/views.rst:0
msgid "Sales order model's List view"
msgstr ""
#: ../../content/applications/studio/views.rst:174
msgid "Map"
msgstr ""
#: ../../content/applications/studio/views.rst:176
msgid "The :guilabel:`Map` :icon:`fa-map-marker` view is used to display records on a map. For example, it is used in the Field Service app to plan an itinerary between different tasks."
msgstr ""
#: ../../content/applications/studio/views.rst:180
msgid "A :ref:`Many2One field <studio/fields/relational-fields/many2one>` linked to the *Contact* model is required to activate the view, as the contact address is used to position records on the map."
msgstr ""
#: ../../content/applications/studio/views.rst:183
msgid "To select which kind of contact should be used on the map, select it under :guilabel:`Contact Field`."
msgstr ""
#: ../../content/applications/studio/views.rst:185
msgid "To hide the name or the address of the record, tick :guilabel:`Hide Name` or :guilabel:`Hide Address`."
msgstr ""
#: ../../content/applications/studio/views.rst:187
msgid "To add information from other fields, select them under :guilabel:`Additional Fields`."
msgstr ""
#: ../../content/applications/studio/views.rst:188
msgid "To have a route suggested between the different records, tick :guilabel:`Enable Routing` and select which field should be used to sort records for the routing."
msgstr ""
#: ../../content/applications/studio/views.rst:0
msgid "Task model's Map view"
msgstr ""
#: ../../content/applications/studio/views.rst:199
msgid "Timeline views"
msgstr ""
#: ../../content/applications/studio/views.rst:202
msgid "When you first activate one of the timeline views, you need to select which :ref:`Date <studio/fields/simple-fields/date>` or :ref:`Date & Time <studio/fields/simple-fields/date-time>` fields on your model should be used to define when the records start and stop in order to display them on the view. You can modify the :guilabel:`Start Date Field` and :guilabel:`Stop Date Field` after activating the view."
msgstr ""
#: ../../content/applications/studio/views.rst:213
msgid "Calendar"
msgstr ""
#: ../../content/applications/studio/views.rst:215
msgid "The :guilabel:`Calendar` :icon:`fa-calendar` view is used to overview and manage records inside a calendar."
msgstr ""
#: ../../content/applications/studio/views.rst:218
msgid "To create records directly within the view instead of opening the :ref:`Form view <studio/views/general/form>`, enable :guilabel:`Quick Create`."
msgstr ""
#: ../../content/applications/studio/views.rst:222
msgid "This only works on specific models that can be *quick-created* using only a *name*. However, most models do not support quick creation and open the :guilabel:`Form` view to fill in the required fields."
msgstr ""
#: ../../content/applications/studio/views.rst:226
msgid "To color records on the calendar, select a field under :guilabel:`Color`. All the records sharing the same value for that field are displayed using the same color."
msgstr ""
#: ../../content/applications/studio/views.rst:230
msgid "As the number of colors is limited, the same color can end up being assigned to different values."
msgstr ""
#: ../../content/applications/studio/views.rst:233
msgid "To display events lasting the whole day at the top of the calendar, select a :ref:`Checkbox field <studio/fields/simple-fields/checkbox>` that specifies if the event lasts the whole day."
msgstr ""
#: ../../content/applications/studio/views.rst:236
msgid "To choose the default time scale used to display events, select :guilabel:`Day`, :guilabel:`Week`, :guilabel:`Month`, or :guilabel:`Year` under :guilabel:`Default Display Mode`."
msgstr ""
#: ../../content/applications/studio/views.rst:240
msgid "You can also use a :guilabel:`Delay Field` to display the duration of the event in hours by selecting a :ref:`Decimal <studio/fields/simple-fields/decimal>` or :ref:`Integer <studio/fields/simple-fields/integer>` field on the model which specifies the duration of the event. However, if you set an :guilabel:`End Date Field`, the :guilabel:`Delay Field` will not be taken into account."
msgstr ""
#: ../../content/applications/studio/views.rst:0
msgid "Calendar Event model's Calendar view"
msgstr ""
#: ../../content/applications/studio/views.rst:254
msgid "Cohort"
msgstr ""
#: ../../content/applications/studio/views.rst:256
msgid "The :guilabel:`Cohort` :icon:`oi-view-cohort` view is used to examine the life cycle of records over a time period. For example, it is used in the Subscriptions app to view the subscriptions' retention rate."
msgstr ""
#: ../../content/applications/studio/views.rst:260
msgid "To display a measure (i.e., the aggregated value of a given field) by default on the view, select a :guilabel:`Measure Field`."
msgstr ""
#: ../../content/applications/studio/views.rst:262
msgid "To choose which time interval is used by default to group results, select :guilabel:`Day`, :guilabel:`Week`, :guilabel:`Month`, or :guilabel:`Year` under :guilabel:`Interval`."
msgstr ""
#: ../../content/applications/studio/views.rst:264
msgid "To change the cohort :guilabel:`Mode`, select either :guilabel:`Retention` :dfn:`the percentage of records staying over a period of time, it starts at 100% and decreases with time` or :guilabel:`Churn` :dfn:`the percentage of records moving out over a period of time - it starts at 0% and increases with time`."
msgstr ""
#: ../../content/applications/studio/views.rst:268
msgid "To change the way the :guilabel:`Timeline` (i.e., the columns) progresses, select either :guilabel:`Forward` (from 0 to +15) or :guilabel:`Backward` (from -15 to 0). For most purposes, the :guilabel:`Forward` timeline is used."
msgstr ""
#: ../../content/applications/studio/views.rst:0
msgid "Subscription model's Cohort view"
msgstr ""
#: ../../content/applications/studio/views.rst:280
msgid "Gantt"
msgstr ""
#: ../../content/applications/studio/views.rst:282
msgid "The :guilabel:`Gantt` :icon:`fa-tasks` view is used to forecast and examine the overall progress of records. Records are represented by a bar under a time scale."
msgstr ""
#: ../../content/applications/studio/views.rst:285
msgid "To prevent users from creating or editing records, untick :guilabel:`Can Create` or :guilabel:`Can Edit`."
msgstr ""
#: ../../content/applications/studio/views.rst:287
msgid "To fill cells in gray whenever a record should not be created there (e.g., on weekends for employees), tick :guilabel:`Display Unavailability`."
msgstr ""
#: ../../content/applications/studio/views.rst:291
msgid "The underlying model must support this feature, and support for it cannot be added using Studio. It is supported for the Project, Time Off, Planning, and Manufacturing apps."
msgstr ""
#: ../../content/applications/studio/views.rst:294
msgid "To show a total row at the bottom, tick :guilabel:`Display Total row`."
msgstr ""
#: ../../content/applications/studio/views.rst:295
msgid "To collapse multiple records in a single row, tick :guilabel:`Collapse First Level`."
msgstr ""
#: ../../content/applications/studio/views.rst:296
msgid "To choose which way records are grouped by default on rows (e.g., per employee or project), select a field under :guilabel:`Default Group by`."
msgstr ""
#: ../../content/applications/studio/views.rst:298
msgid "To define a default time scale to view records, select :guilabel:`Day`, :guilabel:`Week`, :guilabel:`Month`, or :guilabel:`Year` under :guilabel:`Default Scale`."
msgstr ""
#: ../../content/applications/studio/views.rst:300
msgid "To color records on the view, select a field under :guilabel:`Color`. All the records sharing the same value for that field are displayed using the same color."
msgstr ""
#: ../../content/applications/studio/views.rst:304
msgid "As the number of colors is limited, the same color can be assigned to different values."
msgstr ""
#: ../../content/applications/studio/views.rst:306
msgid "To specify with which degree of precision each time scale should be divided by, select :guilabel:`Quarter Hour`, :guilabel:`Half Hour`, or :guilabel:`Hour` under :guilabel:`Day Precision`, :guilabel:`Half Day` or :guilabel:`Day` under :guilabel:`Week Precision`, and :guilabel:`Month Precision`."
msgstr ""
#: ../../content/applications/studio/views.rst:0
msgid "Planning Shift model's Gantt view"
msgstr ""
#: ../../content/applications/studio/views.rst:319
msgid "Reporting views"
msgstr ""
#: ../../content/applications/studio/views.rst:328
msgid "Pivot"
msgstr ""
#: ../../content/applications/studio/views.rst:330
msgid "The :guilabel:`Pivot` :icon:`oi-view-pivot` view is used to explore and analyze the data contained in records in an interactive manner. It is especially useful to aggregate numeric data, create categories, and drill down the data by expanding and collapsing different levels of data."
msgstr ""
#: ../../content/applications/studio/views.rst:334
msgid "To access all records whose data is aggregated under a cell, tick :guilabel:`Access records from cell`."
msgstr ""
#: ../../content/applications/studio/views.rst:336
msgid "To divide the data into different categories, select field(s) under :guilabel:`Column grouping`, :guilabel:`Row grouping - First level`, or :guilabel:`Row grouping - Second level`."
msgstr ""
#: ../../content/applications/studio/views.rst:338
msgid "To add different types of data to be measured using the view, select a field under :guilabel:`Measures`."
msgstr ""
#: ../../content/applications/studio/views.rst:340
msgid "To display a count of records that made up the aggregated data in a cell, tick :guilabel:`Display count`."
msgstr ""
#: ../../content/applications/studio/views.rst:0
msgid "Purchase Report model's Pivot view"
msgstr ""
#: ../../content/applications/studio/views.rst:351
msgid "Graph"
msgstr ""
#: ../../content/applications/studio/views.rst:353
msgid "The :guilabel:`Graph` :icon:`fa-area-chart` view is used to showcase data from records in a bar, line, or pie chart."
msgstr ""
#: ../../content/applications/studio/views.rst:356
msgid "To change the default chart, select :guilabel:`Bar`, :guilabel:`Line`, or :guilabel:`Pie` under :guilabel:`Type`."
msgstr ""
#: ../../content/applications/studio/views.rst:358
msgid "To choose a default data dimension (category), select a field under :guilabel:`First dimension` and, if needed, another under :guilabel:`Second dimension`."
msgstr ""
#: ../../content/applications/studio/views.rst:360
msgid "To select a default type of data to be measured using the view, select a field under :guilabel:`Measure`."
msgstr ""
#: ../../content/applications/studio/views.rst:362
msgid "*For Bar and Line charts only*: To sort the different data categories by their value, select :guilabel:`Ascending` (from lowest to highest value) or :guilabel:`Descending` (from highest to lowest) under :guilabel:`Sorting`."
msgstr ""
#: ../../content/applications/studio/views.rst:365
msgid "*For Bar and Pie charts only*: To access all records whose data is aggregated under a data category on the chart, tick :guilabel:`Access records from graph`."
msgstr ""
#: ../../content/applications/studio/views.rst:367
msgid "*For Bar charts only*: When using two data dimensions (categories), display the two columns on top of each other by default by ticking :guilabel:`Stacked graph`."
msgstr ""
#: ../../content/applications/studio/views.rst:0
msgid "Sales Analysis Report model's Bar chart on Graph view"
msgstr ""
Reference in New Issue View Git Blame Copy Permalink