Enhanced Search Widget Version 2.23.1 - 11/22/22
Oh sorry I see what you mean. I am downloading I thought V1.3 but it isn't
Hi Robert,
Thanks for updating all your Custom Widgets to make them compatible with Web AppBuilder 1.3.
I started with a clean slate and created 7 new apps to showcase the 7 Themes in WAB 1.3 using your 10 Custom Widgets.
Enhanced Search Widget 1.3 12/14/2015
https://community.esri.com/docs/DOC-1731
Enhanced Basemap Gallery Widget 1.3 12/15/2015
https://community.esri.com/docs/DOC-2888
Google Street View Widget 1.3 12/15/2015
https://community.esri.com/docs/DOC-2991
Share Widget 1.3 12/15/2015
https://community.esri.com/docs/DOC-3247
Identify Widget 1.3 12/14/2015
https://community.esri.com/docs/DOC-3250
Elevation Profile Widget 1.3 12/15/2015
https://community.esri.com/docs/DOC-3342
Map Progress Indicator Widget 1.3 12/15/2015
https://community.esri.com/docs/DOC-6416
Enhanced Bookmark Widget 1.3 12/15/2015
https://community.esri.com/docs/DOC-6889
Enhanced Locate Widget 1.3 12/15/2015
https://community.esri.com/docs/DOC-7046
Popup Panel Widget 1.3 12/15/2015
https://community.esri.com/docs/DOC-7355
Other Widgets:
Add Service Widget 1.2 11/17/2015
https://community.esri.com/docs/DOC-6263
Add Shapefile Widget 9/18/2015
https://community.esri.com/docs/DOC-6907
Zoom PreviousNext Widget 1.1.1 5/13/2015
https://community.esri.com/docs/DOC-6111
I used the Community Buildings in Arizona to set up the test cases.
Foldable Theme:
http://www.tapasdas.com/wab/app1
Launchpad Theme:
http://www.tapasdas.com/wab/app2
Dart Theme:
http://www.tapasdas.com/wab/app3
Tab Theme:
http://www.tapasdas.com/wab/app4
Box Theme:
http://www.tapasdas.com/wab/app5
Jewelry Box Theme:
http://www.tapasdas.com/wab/app6
Billboard Theme:
http://www.tapasdas.com/wab/app7
They are all working like a well oiled machine. I will be using these as templates to create my web apps in WAB 1.3.
Thanks for the new draw_point.png that replaces:
\widgets\eSearch\css\images\draw_point.png
\widgets\identify\css\images\draw_point.png
I noticed that the manifest.json file under your eLocate 1.3 download is still showing:
"version": "1.2.0.3",
"wabVersion": "1.3",
I edited them to read:
"version": "1.3",
"wabVersion": "1.4",
The manifest.json file under MapProgress 1.3 download needs to be updated as well:
I like how my settings persists in WAB 1.3.
For example, I can turn on the ZIP Codes layer, and zoom to a new location.
If I reload the app, it remembers my settings in the Layer List Widget, and zooms me to my last map extent.
This will be a welcome feature in our apps that use 50 plus data layers.
You have created a solid WAB 1.3 release of all your Custom Widgets. I especially like how well Identify 1.3 works in tandem with eSearch 1.3 without ever raising any conflicts.
Each one of your Custom Widgets is a gem and performs an essential task not covered by the standard ESRI widgets.
I never thought I will ever see all the Flex functionality carried over to the JavaScript environment using the Web AppBuilder. You have made this happen in less than a year.
As an added bonus, these WAB apps are compatible with touch enabled devices, folds down gracefully to fit your smartphone or tablet, and does not require the end user to download a plug-in.
Thanks to your intuitive configuration wizards, any lay person can configure your widgets without ever having to write any code.
It looks like the Web AppBuilder has finally eclipsed the FlexViewer 
Hi,
I am trying to configure the esearch widget (version 1.3) but I am running into an issue that I think has something to do with some of my layers being related to other tables. Anyone getting an error when trying to configure the esearch widget for layers with relationship classes?
This is the error I get.
Good morning Robert Scheitlin, GISP and everyone.
I did a Search and did not see this question in the thread or forum unless I missed it.
(was not addressed in Re: Customize URL in query results of WAB or https://community.esri.com/docs/DOC-1731#comment-12964 ... but I can move this to one of these if you'd like)
I did monitor your replies to Barnaby Rockwell in your Identify thread regarding UNC paths. I already have a virtual directory to a folder set up. I had already observed what you pointed out, in that Internet Exploder, er, Explorer opens up "file://" links, despite this not being a proper browser design. Well, once I set up a Virtual Directory in IIS, this was solved and all browsers could open the links in the attribute field "Sketch" as below, on our legacy site (built much before WAB, and uses regular ESRI popups from the early 3.x API).
So... I'm putting a link on my eSearch popups:
Now, here's my scenario:
The "SKETCH" attribute field in this layer has a local server at the beginning of the link. Here is an example of a link: \\server-1.servername.local\GISDataFolderVirtualDir\hyperlinks\sav\ws_sketches\Valve Program\Sheet 9785\9785-268.pdf
Note that I changed the real servername above for security; it would be Robert-1.Robertserver.local for example.
Now, what I did on our old inhouse site was simply used Javascript to chop off the first 20 or so characters, so that the link became: GISDataFolderVirtualDir\hyperlinks\sav\ws_sketches\Valve Program\Sheet 9785\9785-268.pdf
Then, I added back on the internal site's name (mapping.internalWebServer.local) to the front of the link string:
mapping.internalWebServer.local\GISDataFolderVirtualDir\hyperlinks\sav\ws_sketches\Valve Program\Sheet 9785\9785-268.pdf
So after this two-step string manipulation in Javascript, it was good to go. A working link to a folder of data.
My Question: can eSearch modify the Link field? It would perhaps be useful to be able to use regular expressions in the Link box to alter the link and accomplish the above. Can it use regular expressions? Or is it treated just as a string?
I am beginning to poke around and look at the underlying code of eSearch. The other thought I had was since I have to get this to working one way or another, I may consider hardcoding this into your widget (altering eSearch code), with an If statement so any layer with a "SKETCH" attribute is sliced and diced with javascript to correct the link. What line in what file would I do this in if I did it this way?
Robert,
I'm also thanks like others for this great powerful eSearch widget. It has great functionality that I could do without the knowledge of a programmer.
I tested this new eSearch1.3 version and would like to inform you this strange thing that didn't happen in your last release (eSearch1.2.0.6).
Thanks,
Ha T.
I'm having trouble creating my expressions in eSearch 1.3. Every time I go into Update Expression Value, below is all that shows up:
The fields to search on aren't coming in and I can't choose how the search should be performed.
Also, I can't add links in 'Link Content'. I could do both in the last version 1.2.x.
Would anyone else think it would be useful to have a "select all" button for Popup Only in the layer config?
I have dozens of layers each with dozens of fields and I spend a lot of time clicking checkbox after checkbox to deselect from popup. I know I could edit it by hand but it would be much quicker for a Select all, and then just re-add the one or two items I need. For example: we have a parcel layer for each year going back to the 1990s. But all I want on the results on the right is Name and Property Address. Then I uncheck the other 25 fields for each layer.
Second question: It would be useful to have a third kind of symbology to show features found with eSearch query. Symbology from Server WITH HIGHLIGHT. For example, let's say I want to use server symbology for my address points. But the address point list is already on. I want to select just a few with the Search by Shape. I have no way of seeing on the map what features I just selected.
The reason one would want server symbology, is say the feature is a commonly understood icon. Like the black and white disc for monitoring wells. Or a fire hydrant for hydrants. My symbology Defaults in eSearch are just thick purple lines and points and a yellow background highlighting. But that kills any unique symbology, like hydrants, or colors for lines like utilities, etc by overriding it. So I propose this to be a distinct third option. It can be as simple as just using the already available standard cyan highlighting/halo, the one that happens already out of the box when you click on a feature on the map and get the popup infowindow. It would perhaps be useful to even allow us users to customize the symbology of the halo highlight for this third option but that would be icing on the cake, the standard static cyan highlight would be a great addition, at least for now, and would be fine for our site. Does this sound useful to everyone, and you see what I mean and why this would be important?
Thank you again Robert and everyone on the thread. We use this widget for its search by Shape as a super Identify. I don't use Identify for anything except its All Visible Layers functionality. When you pair these two together, it's an awesome Identify package. Just fantastic. Robert it's gotten very positive feedback from our municipal users. It's a huge step up from our old legacy viewer and its cumbersome querying and identify!!
Hi Kevin,
These are all excellent ideas!
These enhancements would help us a lot if implemented by Robert
Robert Scheitlin, GISP and everyone - it worked perfectly.
edit: this post isn't showing as a reply on GeoNet for me. In case anyone's wondering it's in reply to where I asked Robert about internal links at the top of this page. Don't know what happened to GeoNet's nested replies. Anyhow...
Here is my code for anyone else interested. I know it's pretty basic and fairly hard-coded but I thought I'd share in case it will help anyone else with internal link paths.
For me all links point to the same root directory, so I created a virtual directory (GISVirtualDir) pointing to the second level of each link (they will all be structured this way, like \\server-1.serv1.locall\GISVirtualDir\links\file.pdf), hacked off the first 22 chars, added the site path to the front of the URL (http://site.name1.local/site10), and it works.
First I test if a layer has this particular field ('sketch').
I added this after the line testing linkFieldNull.:
if (lfields == "SKETCH") {
this._substitute2(qLinks.content, featureAttributes, results);
else
If true I route it to a modified subroutine "_substitute2":
_substitute2: function (string, Attribs, currentLayer) {
var lfields = this._getFieldsfromLink(string);
for (var lf = 0; lf < lfields.length; lf++) {
if (Attribs[lfields[lf]]) {
var fld = this._getField(currentLayer, lfields[lf]);
if (fld.type === "esriFieldTypeString") {
string = string.replace(new RegExp('{' + lang.trim(lfields[lf]) + '}', 'g'), lang.trim(Attribs[lfields[lf]]));} else{string = string.replace(new RegExp('{' + lang.trim(lfields[lf]) + '}',
'g'), Attribs[lfields[lf]]);}}}
stringOriginal = string.substring(22); //22 chars to remove from string ( \\server-1.serv1.local in this example)... Yours may differ!stringAddTo = http://site.name1.local/site10 + stringOriginal;
string = stringAddTo;
return string;
},
I downloaded the app from here just last week: Enhanced Search Widget Version 1.3 - 12/14/15 many times, then deleted, and tried again. Here is a screen shot of the version:
Robert, regarding your question above about running WAB in https, how do I set it up any other way? I just downloaded WAB, registered the app, then started creating my app. It may be a dumb question, but I don't know any other way. I know enough to mess things up, but not enough to fix it. So as can be expected, I can only load secured rest services into the app.
Slightly related, I got eSearch to work on most of my rest services; however, when I set up the Expression Value to query my county zoning rest service, it just says processing and never finds the uniques for the field (0 of 2712). Does this have to do with me using secured protocol? Or why would it give me the "ESRI (processing) Wheel of Death"? The weird thing is, I ran the exact same set up in 1.2 and it worked great.
