6f125de01b
Since odoo/documentation#903, the guideline for the location of new resource (images, downloadable files, RST includes...) files is to place those inside the directory of the RST page that references them. For example, if `doc1.rst` has a reference to `image.png` and to `download.zip`, the file structure should look like this: ├── parent_doc/ │ └── doc1/ │ │ └── image.png │ │ └── download.zip │ └── doc1.rst │ └── doc2.rst ├── parent_doc.rst Before this commit, most of the resource files were still located inside 'media' directories holding all the resource files referenced by RST pages located at the same level as these directories. In the example above, a single 'media' directory would hold all the resource files referenced by both `doc1.rst` and `doc2.rst`. Doing so prevented us from figuring out easily which resource file was referenced by which RST page and, thus, lead to unused resource files piling up in the repository. It also made it more complicated to define codeowners regex rules because a team could not simply be assigned to `/some_page.*` but needed to be assigned to both `/some_page\.rst` and to the location of 'media'. In order to help new content writers figure out the guideline when taking examples from other RST pages, this commit retroactively applies the guideline to existing resource files and 'media' directories. The left-over resource files that are not referenced by any RST page are removed. task-2497965 closes odoo/documentation#2006 Signed-off-by: Antoine Vandevenne (anv) <anv@odoo.com>
67 lines
1.9 KiB
ReStructuredText
67 lines
1.9 KiB
ReStructuredText
=================================
|
|
Segment the Database with Filters
|
|
=================================
|
|
Filters let you reach a granular level of detail in your records.
|
|
|
|
How to work with filters
|
|
========================
|
|
When working with filters, you will see that some of the rules have an arrow button next to it,
|
|
informing you that the parameter has more variables within it.
|
|
|
|
|
|
.. image:: segment/filters1.png
|
|
:align: center
|
|
:height: 350
|
|
:alt: Filters in Odoo Marketing Automation
|
|
|
|
|
|
| More than one parameter line - *node* (+) - can be added under what is called a *branch* (...).
|
|
| To exclude a *node* or a *branch*, click on *Delete node* (x).
|
|
|
|
|
|
.. image:: segment/filters2.png
|
|
:align: center
|
|
:alt: Filters in Odoo Marketing Automation
|
|
|
|
|
|
Every time a new branch is created, you can choose if you would like the records to match *all*
|
|
criteria of the upcoming rules, or *any*, meaning one rule or the other.
|
|
|
|
|
|
Use cases
|
|
=========
|
|
|
|
- **Scenario**: narrow the target down to new opportunities in the pipeline.
|
|
|
|
.. image:: segment/filters3.png
|
|
:alt: Filters in Odoo Marketing Automation
|
|
|
|
- **Scenario**: narrow the target down to suppliers.
|
|
|
|
.. image:: segment/filters4.png
|
|
:alt: Filters in Odoo Marketing Automation
|
|
|
|
- **Scenario**: narrow the leads down to the ones that contain a certain tag name.
|
|
|
|
.. image:: segment/filters5.png
|
|
:alt: Filters in Odoo Marketing Automation
|
|
|
|
- **Scenario**: narrow the target down to the attendees of a specific event that purchase a specific
|
|
category of ticket.
|
|
|
|
.. image:: segment/filters6.png
|
|
:alt: Filters in Odoo Marketing Automation
|
|
|
|
- **Scenario**: narrow the target down to the employees who have kids.
|
|
|
|
.. image:: segment/filters7.png
|
|
:alt: Filters in Odoo Marketing Automation
|
|
|
|
- **Scenario**: narrow the target down to records with a helpdesk ticket solved.
|
|
|
|
.. image:: segment/filters8.png
|
|
:alt: Filters in Odoo Marketing Automation
|
|
|
|
.. seealso::
|
|
- :doc:`automate_actions`
|