...
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 right away, which is very fast and easy during app 's development, BUT bring lots of extra work for AFTER apps were released. development but makes it cumbersome to deploy many changes at once to several places within the app. 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 to re-link link to the new screen all over their app to link to a new screen. Each of those was cumbersome and error-prone. Both of these routes were time-consuming and could lead to errors.
NOW
As of December 30th, a new flexible deploy system is released to all accounts and all servers.
A more detailed description of this mechanism is located in the Deploy Changes page of the General Intros section in this help Docs.
As usual - Looking forward to your questions and comments in the Support channels.