While researching #1455, I discovered that launching the visual builder for flows does not correctly instantiate a new flow to work on. The UI appears to:
Therefore, every time I try to "add a flow" using the visual builder button, I create a "dummy" flow, then work on the flow listed above, never editing the new flow.
The behavior here should be changed in the following ways:
The flow should not be "created" until saving the visual builder; it currently creates a flow on launching the builder, and even if the user then exits out without saving, the flow is persisted
Load the correct flow into the visual builder when launched: the referenced flow when launched from an existing flow, or a set of "dummy" data that does NOT include an ID when launched to create a new flow
sachmerz
commented
2 years ago
While researching #1455, I discovered that launching the visual builder for flows does not correctly instantiate a new flow to work on. The UI appears to:
Therefore, every time I try to "add a flow" using the visual builder button, I create a "dummy" flow, then work on the flow listed above, never editing the new flow.
The behavior here should be changed in the following ways:
dummyDataandinitialFlowin https://github.com/openintegrationhub/openintegrationhub/blob/master/services/web-ui/src/component/flows/index.js