Configure workflow management services
You can configure workflow management services to enable a scalable workflow management system that automates and simplifies many aspects of performing and managing GIS and non-GIS work in an organization. For more information about these services and how to use them, see Introduction to ArcGIS Workflow Manager.
License:
To configure workflow management services, you must have an ArcGIS Workflow Manager Services on Kubernetes license.
Enable workflow management services
To enable workflow management services, complete the following steps:
Sign in to ArcGIS Enterprise Manager and click the Capabilities button in the sidebar.
Turn on the Workflow management services toggle button.
Customize the Workflow Manager configuration
As an administrator, you can add and manage properties using the REST API to configure custom settings for ArcGIS workflow management services and the web app.
Administrative parameters
The following parameters can be added to define custom attributes.
|
Parameter |
Description |
Example format |
|---|---|---|
|
|
Controls how long Arcade expressions will attempt to evaluate. |
|
|
|
Controls how many edits are done at a time for specific operations. For example, creating jobs from an array. |
|
|
|
Controls how long a web request will attempt to be sent before failing in the Send Web Request step and template. |
|
|
|
Controls how long the token used in the Send Web Request step or template will be valid. |
|
|
|
Controls the maximum size allowed for attached responses on a job. |
|
|
|
Controls the frequency of when log messages in the web app are deleted by the cleanup task. This property is set to seven days by default. This property does not alter the frequency of when Workflow Manager Server logs are deleted. |
|
|
|
Controls the number of jobs that will automatically execute upon creation at one time. |
|
|
|
Controls whether incoming webhooks require header security. This property is set to Caution:Setting this property to |
|
|
|
Controls whether the Send Web Request step permits requests to localhost. |
|
|
|
Controls which protocol is permitted during the Send Web Request step. |
|
|
|
Controls which hosts are blocked from receiving web requests during the Send Web Request step. All addresses to the blocked host must be listed including IPv4, IPv6 and hostname. |
Note:0.0.0.0 and 169.254.169.254/32 are blocked by default. |
|
|
Controls which ports are blocked during the Send Web Request step. |
|
|
|
Controls which request headers will be blocked during the |
|
|
|
Controls which request headers are blocked during the Send Web Request step. |
|
|
|
Controls the allowed cipher suites. |
|
|
|
Controls the allowed TLS protocols. |
|
|
|
Enables CORS. |
N/A |
|
|
Controls CORS settings. |
|
|
|
Controls the maximum file size for attachments. |
|
|
|
Controls the max allowable POST body size. |
|
|
|
Controls whether the Send Web Request step permits requests to ports that are not defined in webRequestAllowPorts. |
|
|
|
Controls which ports are allowed to receive web requests during the Send Web Request step. |
|
|
|
Controls whether the Send Web Request step permits requests to hosts that are not defined in webRequestAllowHosts. |
|
|
|
Controls which hosts are allowed to receive web requests during the Send Web Request step. |
|
Geoprocessing tool names that match Arcade expressions
If the name of a geoprocessing tool matches the name of an ArcGIS Arcade expression, such as Buffer or Clip, add allowedList and add tool names that should not be evaluated as Arcade expressions. Alternatively, you can enclose the tool name in single or double quotation marks in the Run Pro GP Tool step's configuration.