Available with Workflow Manager license.
Configure application settings
The JavaScript Viewer can be customized to use authentication and custom maps by configuring the application and map settings. To configure an application, and map and proxy settings, modify the deployed js/app/WorkflowManager/config/AppConfig.js file.
The following table lists the various application settings that can be configured:
Application setting | Description |
---|---|
app.ServiceRoot | Specifies the REST URL of the Workflow Manager (Classic) service. |
app.AuthenticationMode | Specifies whether to use ArcGIS Server token authentication, Portal for ArcGIS authentication, Windows authentication, or no authentication. Note:Portal for ArcGIS authentication is available in ArcGIS Workflow Manager (Classic) Server 10.3.1 and later. |
app.TokenService | Specifies the URL of the ArcGIS token service. Applicable only if AuthenticationMode is set to Token authentication. |
app.PortalURL | Specifies the URL of Portal for ArcGIS. Applicable only if AuthenticationMode is set to Portal authentication. |
app.Appld | Specifies the application ID of the viewer after it is registered with Portal for ArcGIS. Applicable only if AuthenticationMode is set to Portal authentication. |
app.DefaultUser | Specifies the default user name for the web application. Note:The user must be a valid Workflow Manager (Classic) application user. |
app.AutoLogin | Specifies to automatically log in the default user when the application is opened. Note:This applies only when no authentication is used and a valid Workflow Manager (Classic) user is set as the default user. |
app.DefaultQuery | Specifies the default query upon launch of the application using the query path. The query path includes all the container names indicating the hierarchy, separated by backslashes. |
app.jobLOILayer | Configuration for the dynamic Location of Interest (LOI) map service. The LOI map service is comprised of the Point of Interest (POI) feature class (optional) and Area of Interest (AOI) feature class with the feature classes being the topmost layers.
Note:Support for a new POI feature class was added to ArcGIS Workflow Manager (Classic) Server at 10.4. |
proxy.url | Specifies the location of the proxy. |
geometryServiceURL | Specifies the location of the ArcGIS geometry service. |
Configure map settings
If you wish to use different basemaps than the default basemaps you can configure the map settings. You can configure the basemap toggle with tiled map services. Refer to the BasemapToggle widget for supported basemap types.
For dynamic map service support, configure the custom basemap section of the configuration file.
Note:
The JavaScript Viewer can be customized to use authentication and custom maps by configuring the application and map settings. To configure an application, and map and proxy settings, modify the deployed js/app/WorkflowManager/config/AppConfig.js file.
The following table lists the various map settings that can be configured:
Map setting | Description |
---|---|
map.basemapToggle | Specifies the properties for the basemap toggle widget. The widget only supports tiled map services.
|
map.customBasemaps | Specifies the properties for a non-tiled map service to be used as the application’s basemap. This configuration is used when the basemapToggle option is unavailable.
|
map.initialExtent | Specifies the application's AOI map extent on log in. |
map.search | Specifies the application's search controls for the map.
|
Configure proxy settings
If you are using proxy, configure the proxy setting.
Configure the proxy settings for the application. Modify the deployed proxy/proxy.config file.
The following table lists the proxy setting that can be configured.
Proxy setting | Description |
---|---|
serverUrl | Specifies the Workflow Manager (Classic) Server REST endpoint. Change myserver to the hostname of your ArcGIS Server. |
Set up a localized viewer for supported languages
Workflow Manager (Classic) JavaScript Viewer supports the following additional languages:
- Chinese (Simplified): zh-CN
- Italian: it
- Russian: ru
- Spanish: es
- Turkish: tr
To configure a supported language, complete the following steps:
- Open the deployed index.html (or index.aspx) file.
- Remove ‘//’ (uncomment) from the locale you want to use with the application.For example:
locale: es
Note:
Only one language can be configured at a time.
- Save index.html (or index.aspx).
The JavaScript viewer will open in the locale selected in the deployed index.html (or index.aspx) file.