(I use WAB 1.3)
What is the 'best practice' in terms of WAB Application Life Cycle - we do development work for a client that would receive the 'product' once completed.
Our current process are:
- Develop web maps under our own AGOL account
- Develop WAB apps based on these web maps under our own AGOL account. (During development, WAB run authenticated against our AGOL account)
- Widget development follow file & source control management steps more or less like described here; http://proceedings.esri.com/library/userconf/devsummit15/papers/dev_int_69.pdf (it work very well)
- We use the ArcGIS Online Assistant tool to migrate web maps between AGOL accounts. (it work well)
My question/problem are related to moving the WAB apps to a different AGOL account/url. I want to point the finished WAB app to use the 'production' version of the web map on a different AGOL account. The problem is that my WAB apps are not listed if WAB runs against the production AGOL account. How do I changes this? - I can see the settings and relationship(s) between app and portal url are stored in the '~arcgis-web-appbuilder-1.3\server\db\apps' file, but I cant edit that manually/with a text editor.
Any advice please. It would have been great to have this as an option in WAB.