0.0.9-alpha ✔️
Build time: 2024-01-28T17:52:15+02:00
Commit Ref: 3cbcc75
Docker tag: sirveo/sirveo-alpha:0.0.9-alpha
Summary
This release;
- Makes significant enhancements to the flow engine internals, which are required to support future capabilities on the roadmap
- Adds a new status node in graph and task flows, with which users can make the server and flow engine “understand” the execution status of their flows
- Adds an “output” option to webhooks, to control whether and which flow output data appears in webhook HTTP response bodies
- Makes webhooks use the HTTP response status code that is configured with a status node in their target flow, if any, or use pre-
0.0.9-alpha
default behaviour - Adds a new input metadata store, available in nodes
Breaking Changes
- Remove backwards compatibility for the
0.0.7-alpha
link and webhook URL format. - Webhooks would previously include flow output data by default in their HTTP response bodies.
0.0.9-alpha
changes this default behaviour such that webhooks responses do not contain any flow output data. To enable previous behaviour, configure the new “output” setting of webhooks as required.
Features
- ⚡☑️ implement time limit on Javascript execution (1000 milliseconds)
- ⚡💠 a new status node can specify the execution status of a graph or task flow, with an optional message, and HTTP response status code (used by webhooks)
- ⚡🔥 flows have user-defined execution status, message and HTTP status code
- ⚡🔥 webhooks will use the http status code from flows, if specified via the status node
- ⚡🔥 webhook configuration has an “output” to control if, and which flow output data appears in it’s HTTP response body
- ⚡ add a new store input metadata that exposes details about input data to nodes
Fixes
- 🐞 engine: fix that when running task flow nodes in parallel, the
$meta
store’snode_id
andnode_name
properties could contain incorrect values - 🐞 ui: fix that editing a copy-pasted node could modify it’s source node settings
Enhancements
- 🔼 ui: flow editor - when flows execute within a few nanoseconds, the testing tab displays “very fast” instead of “0 seconds”, which is not technically accurate
- 🔼 ui: flow editor - display flow status when running flows
- 🔼
trigger.event.*
system events now include keysstatus
andstatus_msg
, from the new status node - 🔼
trigger.schedule.*
system events now include keysstatus
andstatus_msg
, from the new status node - 🔼😀 the subflow node has new deep trace setting. If disabled (now the default), the flow editor will not show subflow internal inputs/outputs when running flows in the editor.
Engine
- flow engine: Internal enhancements to prepare for future features.
- flow engine: the metadata store has new keys
status
,status_message
,status_http