I don’t know if this is brand new, but I am seeing all of my “Change variable value” events are now deprecated.
I want to better understand what, if anything, would happen if I published my current state WITHOUT updating any of these events. I’ll update them eventually but trying to figure out if its a dependency on my other work.
If memory serves me well, there was a release in the distant past where “placeholder” events (events that had no logic but were used to improve readability of the workflow) caused the entire workflow to error, when it hadn’t prior to the change.
First of all, there is no impact on your application at all, you can publish safely and it will still work.
About the deprecated, yes it’s new, we wanted to do a change on this action. But changing it would affect all existing projects. So we decided to deprecate it and create a new one. The deprecated one will continue to work
Such a fundamental piece I dont want to go and change every single instance of this configuration. Sounds like it will be supported in the future. Can you clarify what is the “new and improved” in the non-deprecated version?
In the deprecated one, when you were doing a change variable value with a type array and “insert at end”, “insert at start” or “insert at index” it was only returning the value that has been inserted
With the new version, the non-deprecated one, we are returning the full array
And also we the new version we are now managing workflow variable. You can create variable in your workflow and change the value with the action
there are also some weird things happening with interface. I’ve had this now happen with loops and variables. For example this is what the change value looked like before i refreshed the page:
