a2948efc46
Rename namespace with defs for 3rd-party integrations to "Integration"
...
[MAILPOET-4659]
2022-10-13 11:58:11 +02:00
5920810ac6
Use step args for triggers
...
[MAILPOET-4629]
2022-09-23 12:42:03 +03:00
460cbd9e12
Construct and pass subject entries to step runners
...
[MAILPOET-4629]
2022-09-23 12:42:03 +03:00
e1e5749eca
Change isTriggeredBy signature for clarity
...
[MAILPOET-4587]
2022-09-21 10:38:17 +02:00
e2c9356f4c
Execute WorkflowRun only when trigger criteria are met
...
[MAILPOET-4587]
2022-09-21 10:38:17 +02:00
6d91251d6c
Update workflow execution control to the new format
...
[MAILPOET-4523]
2022-09-12 14:40:36 -05:00
02489a61a6
Add version_id to WorkflowRun
...
[MAILPOET-4430]
2022-08-10 16:57:25 +02:00
4aa323b612
Extract data-carrying classes to dedicated namespace
...
We need a separation of "Step" as an interface vs. "Step" as a serializable data structure.
[MAILPOET-4515]
2022-08-08 13:23:57 +02:00
494cc7b780
Allow multiple subjects of the same type
...
[MAILPOET-4465]
2022-07-12 13:36:58 +02:00
d7fe884452
Use subject loader in trigger handler
...
[MAILPOET-4454]
2022-07-04 14:09:00 +02:00
716050b7de
Save subject data in workflow runs
...
[MAILPOET-4136]
2022-03-14 09:36:21 +01:00
4a8f37172a
Enqueue next workflow step in trigger handler
...
[MAILPOET-4136]
2022-03-14 09:36:21 +01:00
e4b09ab6de
Create new workflow run in trigger handler
...
[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
