Latest Contributions by Jianxia

Above pop up issues with web map, measure and draw widgets have been fixed in the coming AGOL release and Developer Edition 1.1 in March. Thanks, Jianxia ... View more

This is a known issue. The sample-configs folder will be added back in the next release. The workaround is to make a copy of config.json file, and name it “config-demo.json”, then perform all the operations in the steps referring to config-demo.json with the new file. To see the changes you made in the custom widget, replace the url in the sample http://[your host name:3344]/webapp/?config=sample-configs/config-demo.json with new url: http://[your host name:3344]/webapp/?config=config-demo.json Thanks, Jianxia ... View more

Frank, As public gallery only contains Esri Featured Content and the app created by Web AppBuilder belongs to an org, It is not available in the public gallery. ... View more

Rene, The visibility of hyperlinks on the banner should have nothing to do with the org link. I assume the hyperlinks are set through the Attributes tab->Links. As a test, I created following app and was able to see the hyperlink (org) on the banner which is accessed only by the org link. App: http://www.arcgis.com/apps/webappviewer/index.html?id=5d597c22b0214368b9d1c8a5bf04b4fe  Hyperlink (org) on the banner (http://esridevbeijing.maps.arcgis.com/home/item.html?id=5b9a674043ca4ec783b7eb85037aefa8 I may not understand your workflow. It would be great if you can provide us details or share your app. Thanks, Jianxia ... View more

Rene, This is not true. It depends on how the public app is accessed. If everything is shared with the public, the app is available through public link www.arcgis.com/apps/webappviewer, then everyone should be able to view it. However, if it is available through the org link (custom link), such as http://esridevbeijing.maps.arcgis.com/apps/webappviewer, then login is required regardless it is public or not. We are reviewing current pubic share pattern. Let's know if you have any suggestions regarding this. Thanks, Jianxia ... View more

Good to know. Thanks! ... View more

The public app sharing issue has been fixed. Could you let us know if it works for you? Thanks, Jianxia ... View more

This is a bug and we will fix it asap. The workaround is to enable "Allow anonymous access to your organization's website." We will keep you updated. Thanks, Jianxia ... View more

Thanks for the info. We are looking into it. Jianxia ... View more

David, From my understanding, you made a public app with a public web map. All the layers inside the map are public too. You were able to access the app created by Web AppBuilder last week but not today. For trouble shooting, Could you let us know how you access the app, through your organizational url such as http://energy.maps.arcgis.com/ or by www.arcgis.com? if it is through your org, does the org allow anonymous access? If possbile, could you share the app url with us? Thanks, Jianxia ... View more

I see. As documented in the known issue list in beta community, IWA / PKI portal is not supported at beta 2. We will try to address it in beta 3. ... View more

Lucas, This thread may help. Working with WebAppBuilder behind a corporative http proxy‌ Jianxia ... View more

Steve, Beta1 does not require ArcGIS organization account to access WAB. This is a new feature in beta2. As a result, beta2 requires 3 consecutive ports to open other than 1 port in beta 1. For example, if beta2 uses port 3344 then next two ports (3345 and 3346) are also needed to open. You can use other ports for wab as long as 3 consecutive ports are open, such as 1122, 1123 and 1124, etc. One exception is port 80. If 80 is used for WAB, then only 443 port is required to open. Since beta1 works for you, it may have something to do with ports. By default, wab uses 3344 for tcp, 3345 for http and 3346 for https. Please bring these to your IT department. Hope this helps, Jianxia ... View more

Nodejs comes with wab zip file. You don't need to install it. Two options: 1. run startup.bat file as administrator. 2.  if option 1 is not working, set node server.js to a different port such as 3355 in command prompt:      enter server directory, run node sever.js -port=3355 Jianxia ... View more

Ok, It is not a browser issue then. Is Web AppBuilder installed on the local drive? or is it from a network? ... View more