ed56df2398
Add WorkflowTemplate GET endpoint
...
[MAILPOET-4538]
2022-08-23 14:03:24 +02:00
ca308321fd
Rename step runner to handler (free the name to step runner interface)
...
[MAILPOET-4515]
2022-08-08 13:23:57 +02:00
e3fbf2421d
Move action scheduler initialization to Initializer as one of first actions
...
[MAILPOET-4274]
2022-08-03 10:36:57 +02:00
7df8342a18
Define manage automation capability in automation code
...
[MAILPOET-4465]
2022-07-12 13:36:58 +02:00
d6633efef2
Add workflows PUT endpoint for workflow updating
...
[MAILPOET-4454]
2022-07-04 14:09:00 +02:00
98b01f46e0
Move workflow creation POST endpoint to Premium
...
[PREMIUM-180]
2022-06-09 13:30:54 +02:00
25b9f3a876
Create a workflow from a PHP template
...
MAILPOET-4264
2022-06-08 13:14:11 +02:00
6b1c6929d1
Migrate existing endpoints to the new structure
...
[MAILPOET-4207]
2022-04-20 15:30:50 +02:00
fc16bacadc
Add "core" automation integration & implement wait action
...
The "core" integration will provide triggers, actions, and subjects
that are not specific to any 3rd party integration.
[MAILPOET-4136]
2022-03-14 09:36:21 +01:00
0c8c86c0a8
Add basic workflow step runner service
...
[MAILPOET-4136]
2022-03-14 09:36:21 +01:00
a191c691f5
Add hook and basic handler for automation triggers
...
For now trigger keys are stored in the workflow as a JSON array.
This is not optimal in case someone has many workflows but as
workflows are user-created it's unlinkely someone will have thousands
of them. We can consider adding a workflow_triggers table as well.
[MAILPOET-4136]
2022-03-14 09:36:21 +01:00
933ee0c8c8
Call "registerHooks" method for all triggers of all active workflows
...
This is needed so the triggers actually work – their hooks need to be
registered when the triggers are in some active workflows.
[MAILPOET-4136]
2022-03-14 09:36:21 +01:00
55a25427fc
Add initialize hook to register automation integrations
...
Those need to be registered after Automation engine is initialized.
[MAILPOET-4136]
2022-03-14 09:36:21 +01:00
da2621230d
Move automation engine code under "Engine" namespace
...
This is to separate the engine itself from "integrations" that will be
built on top of the engine.
[MAILPOET-4136]
2022-03-14 09:36:21 +01:00
