[IMP] studio: toctree (#719)

- created how_to folder to include rainbow_man.rst + export_import.rst + reports.rst - corrected typo
2020-07-09 09:21:04 +02:00
parent dbf6a2c8b5
commit 971fc7c145
17 changed files with 15 additions and 7 deletions
@@ -1,28 +0,0 @@
-=========================
-Export and Import Modules
-=========================
-
-When you do customizations in Odoo Studio, a new module is created in your database, making it easy
-to use Studio for prototyping.
-
-To export these customizations, activate Studio on the main dashboard and, under the menu
-*Customizations*, click on *Export*. The default filename is *customizations.zip*.
-
-.. image:: media//export_import/customizations_menu.png
-   :align: center
-   :alt: View of the menu customizations in Odoo Studio
-
-| The module created contains the definition of custom models and fields, as well as the UI elements
-  of any customization in an XML format.
-| To import and install the customizations in another instance, connect to the destination database,
-  activate Studio and, under *Customizations*, click on *Import*.
-
-.. image:: media/export_import/import_modules.png
-   :align: center
-   :alt: View of the import modules window for Odoo Studio
-
-.. warning::
-   Studio does not know which apps are customized (because the same view can be modified on
-   different apps), therefore, it *does not* add the underlying modules as dependencies of the
-   exported module. In other words, the applications installed on the source database should be
-   installed on the destination database.
@@ -1,23 +0,0 @@
-===========================
-Customizing the Rainbow Man
-===========================
-
-The Rainbow Man in Odoo is an animation shown once the user completes certain tasks and clicks on
-certain buttons. It is a way to make the software fun to use, and rewarding, for employees.
-
-.. image:: media/rainbow/crm_rainbow.png
-   :align: center
-   :alt: View of a sales form and the tab properties and its rainbow man field in Odoo Studio
-
-| On most buttons in Odoo, such as *Send by Email*, *Confirm* or *Cancel*, once they are selected in
-  Studio, under their *Properties*, the *Rainbow Man* effect can be applied.
-| By default, the feature is active:
-
- when opportunities are marked as won;
- when users empty their inboxes;
- when the user finishes a tour;
- when the user finishes doing reconciliations.
-
-.. image:: media/rainbow/properties_rainbow.png
-   :align: center
-   :alt: View of a sales form and the tab properties and its rainbow man field in Odoo Studio
@@ -1,72 +0,0 @@
-===================
-Customizing Reports
-===================
-
-| Odoo uses HTML and CSS technologies to create reports. HTML is a markup language that uses tags,
-  also called elements. It is the core of any webpage because it provides its basic structure.
-  CSS interacts with HTML elements to add style to the page, establishing how the HTML is shown to
-  the user. Odoo’s reports also use Bootstrap’s grid layout, which is the containers, rows, and
-  columns to align content, and support Odoo's website themes.
-| When creating a new report, choose the purpose of it and if you would like the report to include
-  header and footer (company logo, name, address, phone, email address, etc.).
-
-.. image:: media/reports/report_typing.png
-   :align: center
-   :alt: View of the types of new reports in Odoo Studio
-
-Under the tab **Add**, you find the fields to be dragged and dropped to the view. *Fields*, *Data
-tables*, *Subtotal & Total*, and *Address Book* are dynamic elements (meaning that they need a
-:doc:`one2many or a many2many <../concepts/understanding_general>` related object). *Text*, *Title
-Block*, *Image*, and *Text in Cell* are static elements.
-
-.. image:: media/reports/add_tab.png
-   :align: center
-   :alt: View of a report and the tab add in Odoo Studio
-
-Once the element is added to the view, select it to see its **Options**. The first section shows the
-hierarchy of the selected object and its properties, allowing you to individually edit
-them. Fields with related objects have their directives shown on *Field Expression*.
-
-.. image:: media/reports/options_tab.png
-   :align: center
-   :alt: View of a report and the tab options in Odoo Studio
-
-| Under **Visible if**, define the rule(s) to set visibility conditions to fields.
-| Example: if choosing to display a product image, you could set a visibility rule to only display
-  the ones that are *set* in the product form, avoiding having a plain icon when they are not set.
-| **Visible for** is used to set which :doc:`groups <../../general/odoo_basics/add_user>`
-  can have access to specific elements in the report. **Limit visibility to groups**, under
-  *Report*, sets the visibility of the report to specifics groups, meaning that users belonging to
-  other groups do not see the same final document.
-
-.. image:: media/reports/limit_visibility.png
-   :align: center
-   :alt: View of a report’s settings emphasizing the field limit visibility to groups in Odoo Studio
-
-Under the **Report** tab, name your report, choose the paper format, and if the report should be
-added to the *Print* menu list on its respective document form.
-
-.. image:: media/reports/print_menu.png
-   :align: center
-   :alt: View of an invoice form emphasizing the menu print for Odoo Studio
-
-If activating the :doc:`Developer mode <../../general/developer_mode/activate>`, additional fields
-such as *Class* under *Options*, and *Reload from attachment* under *Report*, become visible.
-
- *Class*: add custom CSS classes to the selected element (e.g. Bootstrap classes such as
-  *text-danger*).
-
- *Reload from attachment*: saves the report as an attachment of the document when printed. When the
-  report is reprinted, it re-downloads that attachment instead of re-printing it.
-  This means that if the underlying record (e.g. Invoice) changes when compared to the first
-  impression, the report does not reflect the changes because they were done after the attachment was
-  created. This is typically useful for reports linked to documents that should not change, such as
-  Invoices.
-
-.. tip::
-   Actions in Odoo Studio can be undone until you *Close* the toolbox. Once you have closed Studio,
-   changes can not be undone anymore.
-
-   .. image:: media/reports/undo_redo.png
-      :align: center
-      :alt: View of a report being built and emphasizing the undo and redo buttons in Odoo Studio
@@ -2,7 +2,7 @@
 Advanced Use Cases: Views
 =========================

- **Case Scenario 1: in Sales, show orders in a Kanban View instead of a List View.**
+- **Case scenario 1: in Sales, show orders in a Kanban View instead of a List View.**

 From the Sales page, access Studio and, under *Views*, set the *Kanban* option as the default one.