Automation State block #16605
Automation State block #16605
Conversation
|
QA Wolf here! As you write new code it's important that your test coverage is keeping up. |
| expect(successStep.outputs.success).toBe(true) | ||
| expect(successStep.outputs.value).toBe(5) | ||
|
|
||
| // The failure should not cause a total automation failure |
There was a problem hiding this comment.
Hey Sam, thanks for taking a look! What I meant was that, a failure in the state block shouldn't cause any unhandled exceptions and that any state data that was correctly processed should remain intact.
There was a problem hiding this comment.
Sorry for time taken to get to this - the code looks good! I had a play with it and it works the way I would expect, one thing I noticed though, the value is called "code"
I think Key and Value are better terms to mimic the experience we have as part of the button:
|
I also tried using a loop with the state block and it is just saying it throws an error which is a little odd - I'll investigate this further tomorrow! 
|
Description
Added a new
Stateblock to automations. Named variables can be now set in state and updated throughout the automations runtime.Statecategory has been added to the bindings surfacing all available state variables.FIX- Added the looping feature flag to the AI steps: Classify, Extract doc data, Generate text. In order to utilise the looping behaviour the steps will need to be recreated.FIX- Fix for looping UI so that it only shows when steps are configured with the feature flag.Screenshots
Below I have declared a variable called
myVar1. In my step,Sample Step 1, I initialise the value and then update it inSample Step 4. Before running the automation, all theStatesteps that modify a state variable will be listed.Launchcontrol
Added new state block to automations