[16.0][ADD] automation_oca

[etobella]

Initial approach of marketing automation but with a broader scope.

TODO:

• [x] Complete definition of automation flows, including
  • [x] name
  • [x] tag
  • [x] target model (contact, event attendees, etc.)
  • [x] uniqueness filter field
  • [x] initial application criteria (domain).
• [x] Graphic possibility to represent and define different automation stages within that flow, with hierarchical relationship, which requires building a custom OWL widget.
• [x] Capability to define the type of action to be performed in that task in an extensible manner. By default, email sending based on a template, or a server action for custom code.
• [x] Ability to define the trigger for that stage, with a customized time interval, and based on extensible criteria, including at least the following standards:
  • [x] From the beginning of the automation flow.
  • [x] After another activity.
  • [x] After opening or not opening the email.
  • [x] After responding or not responding to the email.
  • [x] After clicking or not clicking on a link in the email.
  • [x] After bouncing.
• [x] Extensibility for other forms of communication (SMS, Telegram, WhatsApp, etc.) must be prepared horizontally, so that if there is a trigger that is "Message opened", it works for all possible forms of communication. There should also be a mechanism to inhibit triggers based on the availability of the communication form. --> That would require a module, but it is feasible
• [x] Ability to set expiration for stages.
• [x] Ability to apply additional filter criteria at the stage.
• [x] Integrated visualization of statistics in the flow widget.
• [x] Management of favorite filters to avoid repeating criteria each time.
• [x] Specific security group to display and manage the section.
• [x] Improve Readme
• [x] Add some demo data

[legalsylvain]

Hi @etobella. What is the utility of this tool ? (Sorry, i'm not sure to understand what are the use cases) If I understand, I can propose a PR to write a readme, like for the spreadsheet module :-) Thanks !

[etobella]

I will write the readme. It is an OSS inspiration of marketing automation tool. However it is intended to be used in more enviroments

[etobella]

Thanks for your comments @legalsylvain :smile:

[etobella]

Configuration view

Record View

[marcelsavegnago]

ping @WesleyOliveira98

[mileo]

@etobella always rocking! :rocket:

[simahawk]

Great work mate :) Early feedback: are we sure the name is appropriated? "automation" seems to broad while this module is explicitly focusing on "marketing automation". In fact, before skimming trough the code I was expecting a sort of replacement or extension for base_automation which is about automating things in general.

[etobella]

It is not focused on marketing automation. It takes the idea, but could be used for managing automatic emails on invoices that are not paid (obviously not marketing). Review maintenance tasks that were forgotten by the team and other ideas.

[etobella]

Also, using the name marketing is like "this tools is used only for marketing purposes", but this is not true, like account_edi of odoo. We created a tool (edi_oca with similar ideas and different approach) to do a similar job for account and a lot of other things. Here, I have the same idea. Automation for marketing is great, but we can do automation for different kind of records. Right now, I implemented mailing and server tools, but I wanted to add other options like creating tasks and what happens when the task is closed and this is useful for a lot of things.

[etobella]

@celm1990 Testing capability is here now!

Actions will work as usual, but emails are not sent (template is generated in order to ensure that everything is right)

[etobella]

I added a way for managing activities and when they are done, if they are closed (removed, the activity_done will never be called)

[codeagencybe]

@etobella are there any plans yet for releasing a v17 version too?

[etobella]

@codeagencybe Right now, it is not in my scope to migrate it, as no customers of mine asked me to do that. If some of my customers wants to migrate it, I will propose my migration

[OCA-git-bot]

This PR has the approved label and has been created more than 5 days ago. It should therefore be ready to merge by a maintainer (or a PSC member if the concerned addon has no declared maintainer). 🤖

[etobella]

History has been cleaned and squashed in 2 commits (one by author)

[liebana]

Quick test, I found an error.

If you set a field in the domain filter area, you need to delete the whole row and can't edit the current one.

An error arises then:

Uncaught Javascript Error > Cannot read properties of undefined (reading 'writeText')

[etobella]

Did you test on runboat? I am unable to get the same error there :thinking:

[galborch]

Hello @etobella Great job 👏 Have you considered implementing a fixed target? For example, not using a dynamic filter and the possibility of uploading an email list in csv, for example a fixed mass mailing list type.

[etobella]

You can use Mailing Contacts (and filter on a list). I don't know if that would work for you :smile:

[gurneyalex]

/ocabot merge nobump

[OCA-git-bot]

Hey, thanks for contributing! Proceeding to merge this for you. Prepared branch 16.0-ocabot-merge-pr-1-by-gurneyalex-bump-nobump, awaiting test results.

[OCA-git-bot]

Congratulations, your PR was merged at a825957551d11b118bf350c200b44b9052a26652. Thanks a lot for contributing to OCA. ❤️

[gregory-moka]

Awesome job ! I'm working on french translation.

I see that the plurals need to be managed (1 week // 2 weeks). I'll manage it with an (s) (1 week(s) // 2 week(s)) Do you plan to improve this behaviour @etobella ?

[etobella]

@gregory-moka Thanks for your comments.

You just need to change this lines

https://github.com/OCA/automation/blob/16.0/automation_oca/models/automation_configuration_step.py#L97

and leave them as [("days", "Day(s)"), ("weeks", "Week(s)"), ("months", "Month(s)")], I will add a small PR just for this