NextERP/documentation
5
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

[IMP] studio: adding link about accessing studio

Browse Source 
Task-3761784

closes odoo/documentation#11977

Signed-off-by: Xavier Platteau (xpl) <xpl@odoo.com>
This commit is contained in:
mcsi-odoo 2025-02-06 14:54:56 +01:00
parent 91165a7012
commit 7d45830ac8
3 changed files with 9 additions and 9 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

6
content/applications/studio.rst
View File

@ -18,10 +18,10 @@ Studio
Studio is a toolbox that allows you to customize Odoo without coding knowledge. For example, you Studio is a toolbox that allows you to customize Odoo without coding knowledge. For example, you
can, in any app, add or modify: can, in any app, add or modify:
- :doc:`Fields <studio/fields>` - :doc:`Fields and widgets <studio/fields>`
- :doc:`Views <studio/views>` - :doc:`Views <studio/views>`
- :doc:`Models <studio/models_modules_apps>` - :doc:`Models, modules and apps <studio/models_modules_apps>`
- :doc:`Automated actions <studio/automated_actions>` - :doc:`Automated actions (automations) <studio/automated_actions>`
- :doc:`PDF reports <studio/pdf_reports>` - :doc:`PDF reports <studio/pdf_reports>`
- :doc:`Approval rules <studio/approval_rules>` - :doc:`Approval rules <studio/approval_rules>`
- Security rules - Security rules

4
content/applications/studio/approval_rules.rst
View File

@ -2,13 +2,13 @@
Approval rules Approval rules
============== ==============
Studio approval rules are used to automate approval processes for actions. They allow you to define 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. the criteria for when an approval is required before an action can be performed using a button.
Configuration Configuration
============= =============
To add approval rules, proceed as follows: To add approval rules with Studio, proceed as follows:
#. :ref:`Open Studio <studio/access>` and switch to the required :doc:`view <views>`. #. :ref:`Open Studio <studio/access>` and switch to the required :doc:`view <views>`.
#. Select the button for which you want to add approval rules. #. Select the button for which you want to add approval rules.

8
content/applications/studio/automated_actions.rst
View File

@ -6,8 +6,8 @@ Automated actions are used to trigger automatic changes based on user actions (e
modification when a field is set to a specific value) or on time conditions (e.g., archive a record modification when a field is set to a specific value) or on time conditions (e.g., archive a record
7 days after its last update). 7 days after its last update).
To create an automated action with Studio, go to :guilabel:`Automations` from anywhere within To create an automated action with Studio, :ref:`open Studio <studio/access>`, then go to
Studio. :guilabel:`Automations` and click :guilabel:`New`.
For every automated action you create, the following elements should be defined: the For every automated action you create, the following elements should be defined: the
:ref:`studio/automated-actions/model`, the :ref:`studio/automated-actions/trigger`, the :ref:`studio/automated-actions/model`, the :ref:`studio/automated-actions/trigger`, the
@ -130,8 +130,8 @@ as when you apply filters on a model.
.. _studio/automated-actions/action: .. _studio/automated-actions/action:
Action Action To Do
====== ============
Determine what the automated action should do (server action). There are eight types of action to Determine what the automated action should do (server action). There are eight types of action to
choose from. choose from.