topic Re: LocalLayerWidget and AccessifizrWidget in Web AppBuilder Custom Widgets Questions

LocalLayerWidget Version 2.5 and AccessifizrWidget Layer - 09/28/2017

AdamDrackley — Thu, 08 Jan 2015 15:55:35 GMT

I've been having a blast playing around with the new Web AppBuilder, and have taken a few cracks at putting together some custom Widgets that I'd like to share with the community. I hope these can assist in everyone's future Mappmaking endeavours!

LocalLayerWidget

LocalLayerWidget v 2.5

September 28 2017 : LocalLayerWidget v2.5 released: This major release includes the following enhancements for the widget. Thanks to everyone who's donated!:

Release LocalLayerWidget 2.5 · cmndrbensisko/LocalLayer · GitHub

Support for 2.5 Release of ArcGIS Web App Builder
Support for Custom Layers via Transformers
Demos and sample apps
Prototype 3D Widget
Dynamic GUI changes at runtime and css insertion via odds.json/odds.css
And more!

November 14, 2016: LocalLayerWidget v2.2 released: This major release includes the following enhancements for the widget:

Release LocalLayer v2.2 · cmndrbensisko/LocalLayer · GitHub

Related Table Viewing and Editing
ImageService Viewing and Popups
WMS Service Viewing and Popups
Ability to integrate with the IncidentAnalysis widget
Hide Layer In Legend capability added
Dynamic mode added, allowing for URL-fed configuration files
And more!

May 18, 2016: LocalLayerWidget v.2.0 released: This substantial change for Web App Builder v.2.0. removes the need to edit any core files in the Web App Builder, unlike previous versions. A slight change will still be necessary for the AttributeTable widget to work properly with LocalLayerWidget layers.

https://github.com/cmndrbensisko/LocalLayer/releases/tag/v2.0
Enhancements:
- Added autorefresh capability for dynamic layers, and sub-minute decimal values can be specified for time.
- Added support for non-consecutive sublayer numbering to support 10.3.1 mapservices
- Editor Tracking via an organizational Active Directory instead of ArcGIS Online User now supported
Bug Fixes:
- View Attachments now works for Dynamic Layers
- Addition of GeoJson layers fixed
- Fix to MapService sublayer visibility when no sublayers are selected to display by default.

Mar 29, 2016: LocalLayerWidget v.1.3.1 released; Contains bugfixes to v.1.3. related to custom rendering for Feature Layers and toggling sublayer visibility in the LayerList widget.

https://github.com/cmndrbensisko/LocalLayer

Mar 22, 2016: LocalLayerWidget v.1.3 is now available! (Note the version naming change; Version 1.3 refers to its compatibility with v1.3 of the WAB - This is indeed the latest version of the widget as of March 22, 2016). Be sure to read the github page to see what tweaks need to be made to ensure that everything continues running smoothly in version 1.3 of the Web AppBuilder.

Includes support for GeoJSON and WebTileLayers
Custom Symbology and Labelling Options for Feature Layers
- Currently requires the use of playground to generate custom json layer and label styling for Feature Layers. For more information, please follow the instructions on the Github page.

Feb 10, 2015: LocalLayerWidget v.1.5 is now available! This release contains full support for adding Tiled layers to your application directly from ArcGIS Server, in addition to the Basemap, Dynamic, and Feature layers available before. Feel free to grab the widget from our Release page located at https://github.com/cmndrbensisko/LocalLayer/releases.

Feb 2, 2015: LocalLayerWidget v.1.2 is now available! This release provides a great GUI developed by Robert Scheitlin to more easily add Feature, Dynamic, and Basemap layers to your ArcGIS Web AppBuilder Applications. Take it for a spin, and please keep us informed of any bugs or desired enhancements through our Github Issue Tracker located at https://github.com/cmndrbensisko/LocalLayerWidget/issues.

Jan 12, 2015: Note that LocalLayerWidget v.1.1 is now available, which provides Click-To-Identify support and the option to add Feature and Basemap layers in addition to Dynamic layers.

The LocalLayer Widget is intended to allow the direct addition of MapServices to an ArcGIS Web AppBuilder application, without needing to wrap the desired services in an ArcGIS Online/Portal Web Map.

https://github.com/cmndrbensisko/LocalLayerWidget

Basically, your basemap will still need to come from Portal/AGOL, but otherwise you just provide direct URLs to your own MapServices in the widget's configuration settings. The MapServices should load and display as usual in the map, and cooperate with the Legend, LayerList, and Attribute Table widgets. Click-To-Identify functionality won't work currently, though, because the current WAB implementation relies on Portal for all the popup info. As stated in the January 12th 2015 release, popups are fully customizable. Note that it's not an in-panel widget, so you'll need to follow a few extra steps in the project's Readme file.

AccessifizrWidget

Let's make Mapps accessible for everyone! With an eye on WCAG compliance, the Accessifizr Widget is designed to help make web applications keyboard navigable without having to modify core application code and UI.

https://github.com/cmndrbensisko/AccessifizrWidget

Information about how to configure this widget is available in the core Accessifizr.js library project available here‌, but the gist is that you create a JSON-based 'roadmap' detailing the keyboard navigation of your web application, and how it should change in response to users entering modal menus, hitting the escape button, etc. For applying descriptive alternate text to page elements, the widget leverages dojo's built-in internationalization support to specify multilingual alternate text strings. The end result is a web app that, hopefully, is a bit easier to use for people with mobility or visual challenges.

Re: LocalLayerWidget and AccessifizrWidget

BarnabyRockwell — Fri, 09 Jan 2015 23:39:49 GMT

Hi Adam,

Your widget is working GREAT for me so far!!!!!!!!!!!!!!!!

I have just Server 10.3, Web Adaptor, and WAB Dev installed, not Portal.

I added the widget to the WAB Dev edition, and now I see it when editing an app, and my locally-hosted service has been added. All is good. Excellent work!

The only thing in your instructions which I don't understand is this:

"Under the Settings option in the Builder, add a JSON array containing the names and URLs of the MapServices that you want included in your Application."

What Settings option? I don't see such an option anywhere.

Best regards,

Barnaby

Re: LocalLayerWidget and AccessifizrWidget

AdamDrackley — Mon, 12 Jan 2015 14:19:36 GMT

Thanks for the great feedback, Barnaby. The Settings option I'm referring to is in the Builder app when you're customizing your application. Under the Widgets Tab, you'll see an icon for each widget available to include in your application. You should see a small pencil icon on the bottom left of each of these icons. When you click the pencil icon for the LocalLayer Widget, a dialog menu will open up wherein you can paste the layer configuration that you've developed for your application in the LayerJSON textbox. This removes having to manually manage your config.json files for multiple applications. I hope this is a bit clearer!

Re: LocalLayerWidget and AccessifizrWidget

RobertScheitlin__GISP — Mon, 12 Jan 2015 14:32:47 GMT

Adam,

I wonder what your reasoning for manually configuring the proxy is. I thought that all the proxy needs were handled by WAB when defining the proxy there? Did you run into a situation where you tested and needed to add the proxy rule the way that you are doing it?

Re: LocalLayerWidget and AccessifizrWidget

AdamDrackley — Mon, 12 Jan 2015 14:48:35 GMT

Hey Robert,

The manual proxy configuration just arose out of my own testing when I was developing the widget. I wanted to use some offsite services, but my local machine didn't have cross-site access to the host server. When I put the code together to handle this via a simple local reverse web proxy, I thought it might be something handy to extend out through configuration for users with similar requirements.

I should probably specify, but the proxy that the widget refers to is a simple reverse web proxy, not one that passes any oAuth2 credentials around. Does this help to answer your question?

Re: LocalLayerWidget and AccessifizrWidget

RobertScheitlin__GISP — Mon, 12 Jan 2015 15:03:02 GMT

Adam,

Was the offsite service a secured service?

Are you interested in accepting pull requests? I am working on the settings UI right now to get away from manually writing the JSON . I have also added a few other layer configuration options like imageFormat, visibility, and opacity.

Re: LocalLayerWidget and AccessifizrWidget

AdamDrackley — Mon, 12 Jan 2015 15:28:07 GMT

No, I haven't tested the widget with secured services yet, but I'd be interested to see if any issues are encountered.

Awesome news about the settings; A better UI for generating the config was definitely on the project's to-do's. It would be my first kick collaborating with Git; Can we roll your enhancements into the core Widget, or are you interested in taking it off in your own direction? As a note, the configuration has changed somewhat in Version 1.1, with support for Popups and Feature/Basemap layers.

Re: LocalLayerWidget and AccessifizrWidget

RobertScheitlin__GISP — Mon, 12 Jan 2015 15:55:14 GMT

Adam,

I did see V1.1 and have grabbed those changes. I have forked your widget and I am adding my enhancements to your core widget. There are some standard convention/preference changes I have made though, like the config.json would not contain LocalLayerWidget as the parent json element and normally you do not include "widget" in your widgets folder name.

Using Git once I submit a pull request you can pull my changes into your widget, or if you see a change you do not like you can reject it.

Re: LocalLayerWidget and AccessifizrWidget

AdamDrackley — Mon, 12 Jan 2015 16:37:25 GMT

Sounds great, Robert. Pull away!

Re: LocalLayerWidget and AccessifizrWidget

GISDev1 — Mon, 12 Jan 2015 17:38:16 GMT

Well done Adam, LocalLayer is a great widget.

Thanks for sharing with the community and great idea to share it using github.

Re: LocalLayerWidget and AccessifizrWidget

BarnabyRockwell — Mon, 12 Jan 2015 18:36:42 GMT

Hi Adam,

Thanks, I now understand what you mean by the Settings option in WAB builder. I had already added my dynamic layer services from my local server that way.

But here is a stupid question that I bet you or Robert could easily answer:

I do not have Portal installed. I started WAB Dev by hooking it to my AGOL group account and a registered app there. I then made my WAB app using your widget and my local services. It looks great in a browser on the server, and I can can even see the app in a browser on another system. However, when I close WAB Dev on the server, I can no longer see the app from a remote system. So I can only view the WAB app if WAB Dev is running on a browser on the server. This is odd. How can I access the WAB app from another system on the network if WAB Dev is closed on the server? Or must I install Portal on the server to have user access my WAB apps hosted on that server?

Thanks,

Barnaby

Edit: The link to the app is in this form:

http://myserver:3344/webappbuilder/apps/8/

If I use a different port number, would I be able to see the app from another system when WAB Dev is closed on the server?

Re: LocalLayerWidget and AccessifizrWidget

RobertScheitlin__GISP — Mon, 12 Jan 2015 18:59:50 GMT

Barnaby,

WAB Developer version is for building your Viewer App. Once you have it configured the way you want then you have to export/download it to your web server that you will use for production.

Deploy app—Web AppBuilder for ArcGIS (Developer Edition) | ArcGIS for Developers

Re: LocalLayerWidget and AccessifizrWidget

BarnabyRockwell — Mon, 12 Jan 2015 19:06:04 GMT

See, I told you it was a stupid question!!!!!

As usual, many thanks!

Best regards,

Barnaby

Re: LocalLayerWidget and AccessifizrWidget

BarnabyRockwell — Mon, 12 Jan 2015 19:32:37 GMT

Adam,

When specifying a dynamic layer in your widget's settings, how does one specify if it should be on or off when the app is first displayed?

[{"type":"Dynamic","name":"Landsat8","url":"http://myServer/arcgis/rest/services/up/Landsat8/MapServer"}]

Best regards,

Barnaby

Edit: Another related question is that when I add a dynamic service as a layer, and turn it on in the app, all the contained layers in the service are turned on automatically, even though none are on by default in the service (as specified in the mxd which I published). Is there a way to not have all the contained layers in a service turned on by default when the overlying service is turned on?

Re: LocalLayerWidget and AccessifizrWidget

BillSpiking__GISP — Wed, 14 Jan 2015 19:57:26 GMT

Great job on the widget Adam! It's working excellent for me in WAB Dev. I know it's early in development, but is there a way to get your widget to interact with other out of the box WAB widgets....the Attribute Table for instance.

Thank you,

Bill

Re: LocalLayerWidget and AccessifizrWidget

AdamDrackley — Wed, 14 Jan 2015 23:08:25 GMT

Hey William, I'm glad the widget is working for you. In my experience, the Attribute Table widget is able to work properly with layers imported using the LocalLayer widget. Are you seeing something different in your environment? What type of layer are you importing, and what kind of behaviour are you experiencing when you try to open the Attribute Table widget?

Re: LocalLayerWidget and AccessifizrWidget

BillSpiking__GISP — Thu, 15 Jan 2015 17:16:17 GMT

Yeah, I haven't been able to get the Attribute Table to populate with any data and when I open the Attribute Table configuration window the layers aren't showing up to allow for configuration. I'm using secure services from AGS 10.1. I'll do some testing and try services that aren't secured.

Thank you,

Bill

Re: LocalLayerWidget and AccessifizrWidget

BillSpiking__GISP — Thu, 15 Jan 2015 18:31:07 GMT

Yep, works fine with layers that aren't secured.

Re: LocalLayerWidget and AccessifizrWidget

AnthonyDaniels — Thu, 15 Jan 2015 21:30:01 GMT

Adam,

Here is another stupid question. I have just started with Web AppBuilder and read the docs.

I followed you instructions but still I get the LocalLayerWidget to show up in the builder?

What am I doing Wrong.

I added the widget to the \client\stemapp\widgets directory

I added the code to the configuration file C:\arcgis-web-appbuilder-1.0\client\builder\predefined-apps\default2DApp\config.json

"widgetOnScreen": {

"widgets": [{

"uri": "widgets\LocalLayerWidget/Widget"

}, {

"uri": "themes/FoldableTheme/widgets/HeaderController/Widget",

"positionRelativeTo": "browser",

"position": {

"left": 0,

"top": 0,

"right": 0,

"height": 40

"version": "1.1"

}, { ...

I made changes to the line 433 in the C:\arcgis-web-appbuilder-1.0\client\stemapp\jimu.js\LayerInfos\LayerInfoForMapService.js file

I add a basemap to the C:\arcgis-web-appbuilder-1.0\client\stemapp\widgets\LocalLayerWidget\config.json file

{

"LocalLayerWidget":{

"layerJson": [

{

"type": "Basemap",

"name": "2010 Aerial Imagery",

"url": "http://mymapserver/arcgis/rest/services/Orthos_2010/ImageServer"

}

]

}

I didn't use the mymapserver but my server URL

Thanks

Skip

Re: LocalLayerWidget and AccessifizrWidget

AdamDrackley — Fri, 16 Jan 2015 01:47:15 GMT

Hey Anthony, it looks like you're following the right steps. Two quick questions to get started;

1) The "\stemapp\widgets" directory is located in the same "c:\arcgis-web-appbuilder-1.0\client.." directory you mention below it, yes?

2) In the "default2DApp\config.json", for the widget entry for the LocalLayerWidget, are both the slashes in the "uri" param the same? Also, is it still called LocalLayerWidget in your environment, or have you changed any widget/directory names anywhere?

3) When you create a new app, in the Node.js console that logs all the backend work, do you see a line similar to the following?

[2015-01-15 20:34:50.223] [INFO] app - copy widget LocalLayerWidget to app 15

Hopefully we can piece apart the problem!