Geocortex Essentials vs AGOL functionality matrix?
Does anyone out there have an out of the box functionality matrix for AGOL/Web App Builder vs Geocortex Essentials using the HTML5 viewer? I know this is ever changing, but am curious... I have been tasked with getting full picture.
Thanks in advance!
0
-
Business Needs Addressed Instantly By Using Geocortex. I just did this business case myself.
Caching Issues – When you add a new layer in ESRI Web App Builder it breaks the map layers if you don’t clear your cache. Geocortex uses XML for instant refreshing.
In AGOL/Portal You cannot select data on the map and have that interact with an attribute table and then export to shapefile or Excel.
In AGOL/Portal you cannot pick a layer and FILTER (not query). Geocortex you can.
In AGOL/Portal you cannot Hyperlink to files and folders on a network drive. ESRI’s workaround creates security issues after discussions with our IT. Geocortex has a built in workaround already for us that maintains security protocol in Edge and IE via the "Feature Hyperlinking Function".
In AGOL/Portal Layer Grouping in Table of Contents is not possible. As of now you cannot put a Feature Service lower then a Map Service in the TOC. Geocortex really manages this well via the Map Service Tab for dra order and the Layer Tab for User views of the TOC. That's really powerful upgrade. One day this will matter to you…trust me.0 -
I agree with all of those, and here's the flip side in my opinion. I use the acronym AGO because 1) I'm stubborn, 2) Online is one word, and 3) AGO looks so much better next to AGS.
Business Needs Address by using AGO:
You can create story maps.
New app features and enhancements are automatically upgraged for you.
You can stand up a simple viewer app much faster than in Geocortex.
You can use the built in map viewer to let people explore all of your available layers.
Your app views are tracked automatically.
The learning curve for new users is much less steep.0 -
Thanks for both of your replies. I am semi-new to 'AGO' :), so am trying to figure out pros and cons. Our staff is so used to requesting Geocortex viewers, because they deliver so much for their customers, but also require a select few of us to build them. We are trying to empower said staff to take the ArcGIS Online approach, if the application is simple essentially, where all requirements can be met by using the out of the box Web App Builder widgets.
I wrote a workflow that reads a .dbf, pubished to REST, that displays questions about the requirements of an application, and delivers a suggested application to use (AGO vs GC), based on a weighted system.0
Bitte melden Sie sich an, um einen Kommentar zu hinterlassen.
Kommentare
3 Kommentare