Sometimes, I can be a late adopter, resistant to change... I learned the platform using the classic UI and I continue to use the classic UI to do scoped app development when I can, instead of using Studio or AES. Change is hard and why would I want to use a different UI when the old one works for me just fine? ¯\_(ツ)_/¯
BUT… in the case of Clone Admin Console, I look forward to using the new UI because it’s not just a new UI.
In case you missed it (ICYMI), there is actually a 🌟 new feature 🌟 in the Washington release that is only available in the new Clone Admin Console UI and not available in the classic UI. That feature is: On-demand Backup (as demoed in this Creator Toolbox video).
As I write this, Washington DC release is not yet out for General Availability (GA). As such, I’ve seen the UI for this option change. Here are three versions that come from my PDI (Washington DC Patch 0) and various YouTube videos. But the option looks something like these:
Without the On-Demand Backup option, my clone is created based on my latest nightly backup. For example, if my instance was backed up last night and I deployed a new update set this morning, that update set would not be part of the cloned data.
With the On-Demand Backup option, I can get the latest data from my production instance, including any recent/last minute changes that I made.
So, in this case, new UI means new and useful feature. Which means I’m sold on the Clone Admin Console! What do you think? Feel free to comment below 👇🏻
For more information:
