with() declarations refresh on any user action regardless of connection

Well i don't agree with Josh, Carlos, or Ashvin at all. Not using with() and instead using only saveInto makes the code many, many times more complex and increases the number of defects tremendously. If you have a SAIL form with 30 variables and 50 components, its nearly impossible to keep track of what components should update which variables using just the saveInto. This is just a generalization, but 30 variables/50 components is not a far stretch from most of the code I have seen others create. Not using with() is not a practical, good, or maintainable way to develop code. And what Josh mentioned makes no logical sense. Why would you have something get updated on every single interaction done on the screen, rather than only on actions related to that variable? Sounds like you need to re-think your implementation so that it is maintainable and logical, and regardless of whether with() is changed, you should change your approach to how you design SAIL forms.

Well i don't agree with Josh, Carlos, or Ashvin at all. Not using with() and instead using only saveInto makes the code many, many times more complex and increases the number of defects tremendously. If you have a SAIL form with 30 variables and 50 components, its nearly impossible to keep track of what components should update which variables using just the saveInto. This is just a generalization, but 30 variables/50 components is not a far stretch from most of the code I have seen others create. Not using with() is not a practical, good, or maintainable way to develop code. And what Josh mentioned makes no logical sense. Why would you have something get updated on every single interaction done on the screen, rather than only on actions related to that variable? Sounds like you need to re-think your implementation so that it is maintainable and logical, and regardless of whether with() is changed, you should change your approach to how you design SAIL forms.