Robert Scheitlin, GISP I have might have come across a serious conflict between eSearch and Identify:
1. First, select something with eSearch (in my case, by selecting graphically).
2. Attempt to Identify. it will fail. It hangs indefinitely with the progress bar spinning. In console it says "Uncaught TypeError: Cannot read property 'indexOf' of null" -- in line 753 Widget.js. I even noticed this when I told Identify to only identify on a single layer. It also happens with All Layers.
I believe this is because of the new temporary "Search Results" layer that the eSearch creates. As evidence, I noticed that as soon as I removed the Search Results layer, Identify started working again perfectly, immediately. I had to use the "Remove from Current Results" feature of eSearch to remove the one parcel I'd selected. (Closing the layer in the Attrib table did not do the trick, only removing via Remove from Selection). Once I'd removed the eSearch's "Search Results" layer in this manner, just as I said, Identify again worked perfectly.
So, is there some way to de-conflict Identify and eSearch, or will this involve you coding this issue into a future update? Anyone else see this? I have the latest version of each widget in WAB 1.2 and was using Chrome for this test. I will be glad to be of service for testing any updates or workflows Robert!
I love eSearch's graphical selection feature. It is extremely powerful and robust. Outstanding.