Docs Updates - submitOnChange and other changes

A couple relatively minor docs updates to share -

We’ve added documentation around the submitOnChange attribute for input elements. This should be used in place of refreshOnSelection in your SmartApps.

Read about it here and see a brief example here.

We also made some tweaks to the Cloud and LAN-connected device guide. These are mainly minor organizational and and high-level changes and bugs fixes (we know there’s so much more to document in this particular area), but wanted to clean up some bugs found and add clarity during @unixbeast’s review of this documentation set. It includes some nice diagrams for understanding the LAN and Cloud-connected patterns (see here for cloud-connected devices, and here for LAN-connected devices).

Since @unixbeast made these changes, it’s only fair that any credit goes to me, and any complaints go to him. :stuck_out_tongue_winking_eye:


Not sure if I should post this here or create a new thread, but I’ll give it a shot.

In the documentation for this feature it states:


When a submitOnChange input is changed, the whole page will be saved. Then a refresh is triggered with the saved page state. This means that all of the methods will execute each time you change a submitOnChange input.

This led me to believe that the refresh would only happen if input is changed as stated. However, I’m seeing the page refresh even if the user clicks the selection list, doesn’t make any chances and then clicks Done. Is this the expected behavior? If so, then the documentation should be updated to make this clear. Otherwise, is this a known issue?

1 Like

Pinging @Jim and @unixbeast on this one since it probably slipped way off your radars after 7 months of posting.

There are some issues with dynamic pages right now especially with android. Is this on ios or android?

I’m not sure if it is intended behavior to always refresh and if it will remain that way across all platforms. If we can get confirmation that is the case the docs can be updated like you suggest.


Sorry, this is on iOS.