To create and share Geocortex Inline views, you require an ArcGIS identity—either in ArcGIS Online (AGOL) or your enterprise Portal for ArcGIS. If Portal for ArcGIS is used, administrator privileges are required.
Geocortex Inline Designer runs in the user's browser using an ArcGIS Online or Portal for ArcGIS identity and supports the following browsers:
Geocortex Inline views run in host web map viewer applications.
For optimal performance, we recommend that users access Geocortex Inline on devices with a minimum resolution of 1440 x 900 pixels.
To run views, the browser should meet the host application's browser requirements:
Geocortex Web 5+: To run views using Geocortex Web, the browser should meet the requirements for Geocortex Web 5.0 and later.
Geocortex Viewer for HTML5 2.9+: To run views using the Geocortex Viewer for HTML5, the browser should meet the requirements for Geocortex Viewer for HTML5 2.9 and later.
Web AppBuilder for ArcGIS (Developer Edition) 2.4+: To run views using Web AppBuilder (Developer Edition), the browser should meet the requirements for Web AppBuilder for ArcGIS (Developer Edition) 2.4 and later.
You can download Web AppBuilder (Developer Edition) here for free. Follow the instructions to install it.
Web AppBuilder for ArcGIS embedded within the Portal for ArcGIS component of ArcGIS Experience Builder Enterprise Edition 10.5.1+: To run views using Web AppBuilder for ArcGIS in Portal for ArcGIS, the browser should meet the requirements for Web AppBuilder in Portal for ArcGIS.
To run views using Web AppBuilder in Portal for ArcGIS 10.5.1, users must sign in to the app. The app will not load the Inline Workflow widget for anonymous users.
Starting in Web AppBuilder in Portal for ArcGIS 10.6, anonymous users can use publicly shared Workflow widgets in public apps. For more information, see Add Custom Widgets.
Geocortex Inline works with Portal for ArcGIS 10.5+.
You can use Portal for ArcGIS 10.5 to access Geocortex Inline Designer and store workflows. However, you cannot host views in Web AppBuilder for ArcGIS (Developer Edition) in Portal for ArcGIS 10.5 apps, because version 10.5 does not support custom widgets. Custom widgets are only supported in version 10.5.1 and later.
If Portal for ArcGIS is secured using Windows Integrated Security and anonymous access to the Portal is disabled in IIS, you must install the Geocortex Web Adaptor Extensions to allow Geocortex Inline to communicate with Portal for ArcGIS.
Geocortex Inline does not expose any ports, so you do not need to adjust your firewall settings. Geocortex Inline (including the Designer) relies on the ports that IIS uses (ports 80 and 443 by default).
Geocortex Inline is licensed software. If you do not have a valid license, your views will show a licensing message when they run.
Licensing is based on the number of ArcGIS identities (named users for ArcGIS Online and Portal for ArcGIS) that your organization has.
To obtain a license, contact Customer Service at customerservice-ca@vertigis.com.
Geocortex Inline is designed to consume and display content from a variety of Esri software; the Esri licenses required to author and publish content are available from your Esri distributor.
Inline uses the modern ArcGIS pattern and ArcGIS Identities to author and access applications. You must have at least a Creator user type (formerly, a Level 2 user) or a GIS Professional user type to create content in Inline. An Esri portal (ArcGIS Online or Portal for ArcGIS Enterprise) and the ArcGIS Identities themselves are also available from your Esri distributor.
Geocortex Inline does not use cookies.
By default, ArcGIS portals (including ArcGIS Online) allow cross-domain requests using Cross-Origin Resource Sharing (CORS).
If your portal has the default Organization | Settings | Security | Allow Origins settings, you do not need to do anything.
However, if you have modified the Organization | Settings | Security | Allow Origins settings from the defaults, you must configure those settings and add the Geocortex Inline Designer as an allowed origin.
For details, see Restrict cross-domain requests to your portal.
