Automation Branching UX #14783
Merged
Automation Branching UX #14783
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
…ults for automations. Added fix for stacking currentItem loop bindings
Search filter typing
…omation-branching-ux
…Add a delete confirmation for branches
…/budibase into feature/automation-branching-ux
…ffset can sometimes not be initialised before moving the mouse
…omation-branching-ux
Fix issue with branch step bindings
… feedback were displaying in the wrong steps.
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
Adds the ability to create new branched automations in the builder.
FIX- loop block binding added multiple times. Consecutive loops will continue to addcurrentItembindings to the available bindings pool.FIX- error reporting in loop blocks would inadvertently overwrite the wrong results. If a loop failed it would update at the loop failure index and not the loop step index.Update- existing automations using step index runtime bindings (steps.2.myBindings), will be migrated automatically to usestep idbindings. This change was made to better accomodate branching as a feature but it also means that we don't have to continually parse steps when you alter the step order. No change is required by the user. Existing automations will continue to run without modificationAddresses
Screenshots
Incoming
Launchcontrol
Adds support for creating branched automations in the builder!
Feature branch env
Feature Branch Link