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>
53 lines
1.6 KiB
ReStructuredText
53 lines
1.6 KiB
ReStructuredText
==================================
|
|
Launch a Test and Start a Campaign
|
|
==================================
|
|
Before starting a campaign, launching a test allows you to run the workflow on a test contact and
|
|
view the sequence of events in action, avoiding mistakes.
|
|
|
|
Launch a test
|
|
=============
|
|
| Click on *Launch a test*.
|
|
| Once you have selected the test contact, *Run* the parent activity and the subsequent ones as
|
|
needed.
|
|
*Run* and *Stop* activities individually. To stop the whole workflow click on *Stop*.
|
|
|
|
|
|
.. image:: test/test1.png
|
|
:align: center
|
|
:height: 350
|
|
:alt: Create workflows in Odoo Marketing Automation
|
|
|
|
|
|
.. note::
|
|
Launching a test does not add data to your metrics with the purpose of not introducing wrong
|
|
inputs to reports.
|
|
|
|
|
|
Start and stop a workflow
|
|
=========================
|
|
Click on *Start* to run the workflow, and on *Stop* to interrupt it. The interruption and new start
|
|
can happen at any moment. The current status will be shown on the status bar.
|
|
|
|
|
|
.. image:: test/test2.png
|
|
:align: center
|
|
:alt: Create workflows in Odoo Marketing Automation
|
|
|
|
|
|
Participants and their specific workflow
|
|
========================================
|
|
*Participants* are all the records that have ever been involved in the campaign.
|
|
|
|
|
|
.. image:: test/test3.png
|
|
:align: center
|
|
:alt: Create workflows in Odoo Marketing Automation
|
|
|
|
|
|
If you click on *Participants* and open a record, you will find the specific activities the record
|
|
went/are/will go through, as well as when the workflow was triggered to him. If you wish to cancel
|
|
an activity click on *Cancel*.
|
|
|
|
.. seealso::
|
|
- :doc:`automate_actions`
|
|
- :doc:`segment` |