Idea Summary:
Implement a feature in Experience Builder that allows users to create multiple drafts for the same map project, similar to version states and virtual copies in Adobe Lightroom. This would enable users to test different configurations, revert to the current published version, and manage multiple drafts seamlessly.
Current Limitations:
Proposal for Experience Builder:
Inspired by Adobe Lightroom’s version control(i), Experience Builder should incorporate a system that allows for the creation and management of multiple drafts of the same project. Each draft version would reference the same AGOL item ID, eliminating the need to notify stakeholders of link changes when a copy draft becomes the authoritative version. This system would provide the ability to revert to the current published state or previous versions if a draft proves unsatisfactory.
Functionality Details:
Draft Creation and Management:
Version Control:
Reversion Capability:
Seamless Integration:
Benefits:
Conclusion: By incorporating a feature akin to virtual drafts and version states found in Adobe Lightroom, Experience Builder can greatly enhance its flexibility, consistency, and efficiency. This improvement would empower users to manage their projects more effectively, freely experiment with different configurations, and reduce the risk associated with making changes to critical applications.
i - Adobe Lightroom Footnote:
In Adobe Lightroom, users can create multiple version states for an image and revert to any state at any time. They can also create virtual copies of the same image, each with its own version history, while only one actual image file exists on the computer. Each virtual copy generates a new text file that dictates Lightroom on how to apply the edits for that copy.
Hi @DanMakridakis,
Great and well documented suggestion. Essentially it takes my idea, and extends it to allow for multiple versions to be edited for the same ExB application, rather than simply reverting the "editable draft version" to the published copy.
I think being able to create multiple versions of a single app would be incredibly useful as you may want to take an app in one or another direction (e.g. different section/view configurations), while referencing the same content, which would be simplified if not creating multiple clones of the same app, with different IDs. Great idea.
I had my experience all finished for larger views, and was working perfectly. I published it a couple of days ago, and today I did the optimization for the smaller screens, by changing from the default to custom structures for each of my pages and moving things around so that they would fit better. I though that by doing this, the changes I made would be reflected only in the tablet and phone views of my experience. After doing all that work, I went then back to the larger screen size view, and oh surprise, things had moved around there too, in a very bad way.
Now I need to revert the changes I made and go back to the version I last published to my experience. So, please please esri, please implement this idea, it'd be much appreciated. Thanks!
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.