The November 2015 ArcGIS.com update has a new feature listed for Web AppBuilder where the app automatically saves your last location and layer visibility for the next time you open the app. HOW DO I TURN THIS OFF? This seems to be causing issues with map layers not loading that are coming from our internal server. Plus, I want all the layers to go back to the map default each time on map open.
Thanks
Dan
The app state feature also applies for apps created by Developer Edition and deployed to web server. Thanks for your reminder. We will document it in developers site.
Thanks,
Jianxia
Jianxia Song, will an option for saving the app state also be available outside of AGOL through the developer and/or Portal versions?
Cole,
WAB Developer is always released after the latest AGOL update. So eight now it is scheduled for Dec time frame the release of WAB Dev will include the save app state and hopefully they will make that configurable for that release.
Robert and Cole,
Unfortunately due to string freeze, we are not able to add the configuration option in dev edition and portal 10.4 release. It will be available in March.
Thanks,
Jianxia
By string freeze to you mean that coding changes have been frozen until the Dev release? I thought in the past when issues were found in the AGOL version some were fixed before the Dev version was released.
Robert,
String freeze is for localization, which ties to AGOL release. For developer edition, we cannot add or update any strings but can fix critical issues as long as they do not require any string changes. Since the option setting for app state requires UI strings, we are not able to do it until March.
Junshan shows how to disable it in code. This is a workaround. Hopefully, it helps.
Thanks,
Jianxia
Jianxia,
Thanks for the explanation. I will use the workaround when Dev version is released
Good one Dan! Seems that any parameters tacked on the link trigger the original state of the app. I just added an ampersand "&" without any parameters and it seems to trigger the original state without executing any parameters.
One thing that has not be answered is about how the save app state on exit is turning off all the layers inside of a grouped layer that were defaulted to being checked on in the table of contents. Is this a bug, or by design? Is anyone else seeing this behavior after the November update?