Good to see the updates to ATF and Flow Designer. Any reason why versioning hasn't been added to flows as well? Would make sense to have it, especially as you alluded to the fact Chuck that old flow configs can easily be lost. Great video btw guys, just been digging into this new stuff in Paris over the last few days.
1. before all bigger reworks, copy the previous flow to have a restore/backup point - I've had a few flows become corrupt from moving the actions and steps in and out of previous logic, even when they passed the validation from the system 2. you can work around the lack of versioning (a bit) by monitoring the table sys_update_version for sys_hub_* record payloads, but hopefully a proper solution will come around Quebec or soon after 3. perhaps flows would include rollback action by that time - until then, it's hard to think of them as anything but a competitor solution to workflows
Cezary Mazarski Yea thanks, I learned the hard way but started making copies too once I realised I had no restore point. It just seems a no-brainier to add this in for me as it’s been there for so long in the legacy workflow app.
I am a bit confused here concerning the Upgrades and the Upgrade Monitor. Chuck mentioned that "Those changes are now captured". I assume that he e is talking about the "Disposition" of the skipped record for ex. whether it's Skipped, Reverted, etc. because before Paris, the user who is dealing with the upgrade was also able to create an update set and capture all of the changes.
I’ve removed my comment about intro being too long as you fully addressed my concern. Keep up the great work Chuck.
Loving the Podcasting for Dummies poster. I thought it was tongue-in-cheek but now can see it's a shameless plug! :-)
Great job finding that Easter Egg among my background.
Thanks Chuck! Love the now bow-tie
Good to see the updates to ATF and Flow Designer. Any reason why versioning hasn't been added to flows as well? Would make sense to have it, especially as you alluded to the fact Chuck that old flow configs can easily be lost.
Great video btw guys, just been digging into this new stuff in Paris over the last few days.
1. before all bigger reworks, copy the previous flow to have a restore/backup point - I've had a few flows become corrupt from moving the actions and steps in and out of previous logic, even when they passed the validation from the system
2. you can work around the lack of versioning (a bit) by monitoring the table sys_update_version for sys_hub_* record payloads, but hopefully a proper solution will come around Quebec or soon after
3. perhaps flows would include rollback action by that time - until then, it's hard to think of them as anything but a competitor solution to workflows
Cezary Mazarski Yea thanks, I learned the hard way but started making copies too once I realised I had no restore point. It just seems a no-brainier to add this in for me as it’s been there for so long in the legacy workflow app.
I am a bit confused here concerning the Upgrades and the Upgrade Monitor. Chuck mentioned that "Those changes are now captured". I assume that he e is talking about the "Disposition" of the skipped record for ex. whether it's Skipped, Reverted, etc. because before Paris, the user who is dealing with the upgrade was also able to create an update set and capture all of the changes.
You are correct. The disposition is captured in an update set.
Hi Guys, i would want to translate and repeat this talk to my german speaking colleges, so i wonder if the slide deck is available?
I have a deck available that we use for developer meetups. If you send me an email to chuck.tomasi@servicenow.com, I will send you a download link.