[IMP] studio: adding link about accessing studio
Task-3761784
closes odoo/documentation#12032
X-original-commit: 5c72ee6f63
Signed-off-by: Xavier Platteau (xpl) <xpl@odoo.com>
Signed-off-by: Siobhan McGonigle (mcsi) <mcsi@odoo.com>
This commit is contained in:
parent
f3c3c31787
commit
c599d94588
@ -21,7 +21,7 @@ can, in any app, add or modify:
|
|||||||
- :doc:`Fields <studio/fields>`
|
- :doc:`Fields <studio/fields>`
|
||||||
- :doc:`Views <studio/views>`
|
- :doc:`Views <studio/views>`
|
||||||
- :doc:`Models <studio/models_modules_apps>`
|
- :doc:`Models <studio/models_modules_apps>`
|
||||||
- :doc:`Automated actions <studio/automated_actions>`
|
- :doc:`Automation rules <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
|
||||||
|
@ -2,13 +2,13 @@
|
|||||||
Approval rules
|
Approval rules
|
||||||
==============
|
==============
|
||||||
|
|
||||||
Studio approval rules allow you to require the approval of one or several users before an action can
|
Approval rules are used to automate approval processes for actions. They allow you to define
|
||||||
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 an approval rule:
|
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 to which the rule should be applied.
|
#. Select the button to which the rule should be applied.
|
||||||
|
@ -6,7 +6,8 @@ Automation rules are used to trigger automatic changes based on user actions (e.
|
|||||||
modification when a field is set to a specific value), email events, time conditions (e.g., archive
|
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.
|
a record 7 days after its last update), or external events.
|
||||||
|
|
||||||
To create an automation rule with Studio, proceed as follows:
|
To create an automated action with Studio, :ref:`open Studio <studio/access>`, then go to
|
||||||
|
:guilabel:`Automations` and click :guilabel:`New`.
|
||||||
|
|
||||||
#. Open Studio and click :guilabel:`Automations`, then :guilabel:`New`.
|
#. Open Studio and click :guilabel:`Automations`, then :guilabel:`New`.
|
||||||
#. Select the :ref:`studio/automated-actions/trigger` and, if necessary, fill in the fields that
|
#. Select the :ref:`studio/automated-actions/trigger` and, if necessary, fill in the fields that
|
||||||
|
Loading…
Reference in New Issue
Block a user