topic Initiate a behavior on application launch in Web AppBuilder Custom Widgets Questions

Initiate a behavior on application launch

SvivaManager — Mon, 16 May 2016 11:30:08 GMT

Hello,

I'm trying to realize how can I highlight a polygon or a point on a specific layer (just like the search widget does) as the application loads. I'm getting tangled with how it's best to do this.

My first thought was to inject the code somewhere in the js files after the map was loaded.

After a second thought I came up with the idea of adding a custom behavour inside a custom widget and just execute that widget on load.. So far I couldn't find the best spot where I know for certain the map and all of its content were fully loaded. Anyone ever done such thing before?

Thanks,

Shay.

Re: Initiate a behavior on application launch

RobertScheitlin__GISP — Mon, 16 May 2016 12:55:38 GMT

Shay,

This is already built into WAB 2.0.

Use URL parameters—Web AppBuilder for ArcGIS | ArcGIS

Use URL parameters—Web AppBuilder for ArcGIS | ArcGIS | Query Features

Re: Initiate a behavior on application launch

SvivaManager — Mon, 16 May 2016 13:19:06 GMT

Ugh! Thank you for pointing that out.. I'll read it

Re: Initiate a behavior on application launch

SvivaManager — Mon, 16 May 2016 15:19:34 GMT

It seems that the built-in query in parameters works only for feature layers but most if not all of my layers are published as dynamic map services. Any thoughts on that issue? As I see it, I need to develope my own query ability

Re: Initiate a behavior on application launch

RobertScheitlin__GISP — Mon, 16 May 2016 15:57:45 GMT

Sviva,

For a sublayer in a group of map services, use <layer id_sublayer id> as the layer ID.

In the documentation it states querying a sub layer is supported.

Re: Initiate a behavior on application launch

SvivaManager — Mon, 16 May 2016 16:38:29 GMT

THANK YOU! It took me quite a while to understand what you mean but I finally did

Apparently my problem was using a map service with a complex name that contains too many special characters.

Those characters flunks the query. Solved by changing the name or using its special id name