Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 3 Next »


A highly requested function of our Constructor!  However, we did take some time to understand how to make it right for most use cases scenarios that we hear from our clients.


WAS

The issue was that every time you press Save in Constructor - our system deploys changes into the screen and every user who has that screen available in his app will immediately see those changes. This instant "Save" is Fast and easy during app's development, BUT  bring lots of extra work for AFTER apps were released. Most users duplicated screens that needed changes, tested updated functionality of their apps on those screens and then either manually updated the original screen, or choose to change links all over their app to link to a new screen. Each of those was cumbersome and error-prone. 


NOW

As of December 30th a new flexible deploy system is released to all accounts.




A more detailed description of this mechanism is located in How to Section of this help Docs


As usual - Looking forward to your questions and comments in the Support channels.

  • No labels