Drafting/Autosave on Workflows
under review
Kevin Cowgur
I would like to see Rewst incorporate a "Draft" functionality, where when modifying a workflow, unpublished changes are stored in a Draft.
This way if a user has been working on a workflow and forgets to publish at the end of the day, or they restart their computer, or accidentally close the tab, they won't encounter data loss and can resume where they left off.
Log In
D
Dan Knutson
under review
Aaron Bertsch
This would be a total game changer
D
Dan Knutson
Merged in a post:
Workflow Sandbox Mode
Lachlan Messner
It would be great to have a feature where you can switch a workflow over to a separate stream for development purposes.
As we all know, 99% of first-time changes result on some sort of a failure. As we are starting to have more and more workflows in production, there is a real risk in causing critical disruptions when changes need to be made. The only way to get around this currently is by copying workflows, making the changes and testing, then applying the changes to the live workflows. This is a very time-consuming process, messy, and can still result in mistakes.
I would propose some sort of feature that allows me to set a workflow or workflow group in 'sandbox mode' by clicking a button, such as 'Duplicate to Sandbox' where I can make changes, test and resolve issues, all without having to copy the workflow or affect production workloads. Once I had completed my changes and testing, I could click a 'Save to Production' button.
D
Danial Gagne
Logan Cook
Handling this with a toggle similar to Microsoft with Onedrive autosaves could be a good way to implement.
Possibly even a global toggle for "Default on/off"
Tre Eiler
That would be great, along with perhaps a revision history at the same time.
Say you push a sandboxed flow into production, but something was missed and its causing more harm than good, it would be nice if you could revert to previous versions that were published. A running 30-day revision history would be perfect.
Within this "Revision Log" you could enable or disable the requirement to add some notes in the "revision log" that can could store info about each revision, and who published that revision. That way you can keep track of the fixes implemented and why and revert back as required.
Kevin Clement
I'd like this extended to the live editor. Plenty of times I've worked on some jinja for a while and it clears out before I get to implement it into a workflow.