This is just curiosity talking. It seems like almost every action in kinetic in cloud is saving after each “action” on almost any given page. Is this the case or no? If so, is there a way to disable it?
All screens are configured differently, there’s not a universal setup for this behavior. Some screens will save the record when you click into a combobox for example, as the results of the combobox are dependent on other input into the record.
My experience with Cloud is, the 80/20 rule applies to saving only when you explicitly hit save (or leave the page), and saving per-field only applies to certain modules/fields. (the 20%)
Thanks for the response. I guess every time I see that blue line go across the top I assume it is saving; or at least processing something. I’d like to keep that behavior to a minimum as it definitely doesn’t help user acceptance. Any ideas there?
The blue line will show up any time App Studio is processing an “Event” - you will see the blue line until the Event chain completes processing, and App Studio goes back to waiting for user input. So the blue progress bar is an indicator of activity/background processing, rather than saving.
I don’t think that there is a way to suppress the progress bar, so it would be a user training “thing”
The progress bar isn’t necessarily the issue. It’s the stutter that comes from the processing. Just one of those things I guess. I appreciate your help!