Mit der Workflow Manager-Lizenz verfügbar.
To configure Workflow Manager (Classic) system settings, start ArcGIS Workflow Manager (Classic) Administrator, connect to your Workflow Manager (Classic) database, and click Settings > Workflow Manager System Settings. The system settings tabs and the behavior they control are discussed below.
General
General application settings enforce how the application behaves in specific situations related to job assignment and status, area of interest, version management, and transaction management.
Learn more about creating status types
Job settings
The Job Settings section on the General tab contains the following settings:
| Option | Description |
|---|---|
Use automatic status assignment | The job's status is managed by Workflow Manager (Classic) based on the stage of the job.
|
Use step status assignment | With this option, if a status type is associated with a step in a job's workflow, the job's status updates to match the status when the step is reached. |
Show Pending Days | This option enables the display of pending days in the property tab of the job under dates. The number of days the job has been pending is calculated from the date the job is started. If the job is closed, the end date and the start date are taken into account to calculate the number of days the job was pending before it was closed. When the option to take holds into account for the pending days is selected, the number of days for each hold is taken out of the pending days calculation. For example, if the job was started on November 1 and two holds of 10 days each were present for the duration of the job, and the job was closed on November 26, the number of days the job was pending before being closed would be 6. |
Start JOB IDs at Value | Workflow Manager (Classic) adds this value to the automatically assigned Job ID of created jobs. |
Administration
When Prompt for User/Password when deleting job version is enabled, users are prompted to enter a password for the owner of the versions they are deleting.
As part of the custom steps in Workflow Manager (Classic), a clean up step is available that can be used to delete versions as part of the workflow. When the step runs, it prompts the user to provide a valid user name and password before deleting the version. If you have versions owned by individual database users, you can specify a Super-User here (such as an enterprise geodatabase user) to delete versions.
Application Tabs
The tabs available in the job view in ArcGIS Pro can be controlled as a system setting.
You can control the tab visibility by allowing certain users in a group to access certain tabs and restrict other groups from accessing the tabs in the application. This association is done based on group membership. For example, if you only want managers to see the History tab, you can disable this tab for other members of your organization and only grant the managers access to the tab.
Notifications
If you are choosing to use the built-in notification engine for Workflow Manager (Classic), configure the name of your SMTP server on this tab. This is used by all the Workflow Manager (Classic) client machines to send outgoing notification email messages. To use the built-in notification engine, you specify the SMTP server name and optionally provide a default sender email and name.
To use a secure SMTP server, you are required to specify the SMTP server, port, and valid user name and password that can be used to send the messages through the server. For example, if you are using an SMTP server, provide credentials for a valid email account that opens communications between Workflow Manager (Classic) and the SMTP server.
Hinweis:
The secure SMTP server relies on some .NET libraries that are not included with an ArcGIS Workflow Manager (Classic) Server-only installation. Use the built-in option if deploying a Server-only installation of ArcGIS Workflow Manager (Classic) to send notifications.
| Option | Description |
|---|---|
SMTP Server | The name of your SMTP server for sending outgoing messages. |
Port | The port of the SMTP server used; by default, the port number used is 25. This setting is optional, but if your SMTP server is using a different port number, enter it here. This is also required when using secured SMTP authentication. |
Plain Text Notifications | The text in the notification type message will not contain special formatting. |
HTML Notifications | HTML tags contained within the message of the notification type are resolved when sending the message. |
Default Sender Email | If the notification type does not have a designated sender, the email entered here is used. |
Default Sender Display Name | If the notification type does not have a designated sender display name, the email entered here is used. |
SMTP Authentication—Username | Must specify a valid email account when using a secured SMTP server. For example, jbloggs@gmail.com, if using Google's SMTP server. |
SMTP Authentication—Password | Must specify a valid password for the user name specified above when using a secured SMTP server. |
SMTP Authentication—Protocol | Must specify the protocol used by the SMTP server. For example, SSL or TLS. |
Map views
You can select an existing map from the Workflow Manager (Classic) repository that you want to show on the Map View tab.
You can choose the map you want to display from the ArcGIS Pro project by typing the name of the map in the Job Result Map View text box.
You can also configure the map to zoom to the job LOI and change the color of the LOI selection in the map view.
Workflow
Workflow settings allow you to control the behavior and presentation of your workflows.
Options
The Options section of the Workflow tab contains the following options:
| Option | Description |
|---|---|
Show step IDs on workflow | When enabled, the unique ID for the steps in the workflow display to the user. |
Confirm procedural step completion | When enabled, the user is prompted to confirm that they want to mark the current procedural step as complete. |
Auto close jobs when workflow is complete | When enabled, the job is closed after the last step in the workflow is marked as complete. |
Auto commit job workflows | When enabled, workflows are automatically ready for execution when the job is created. When disabled, workflows are in an editable state when the job is created. |
Require procedural steps to be marked as started | When enabled, users need to mark procedural steps as started before marking them as complete. |
Selected Step Symbology
The Selected Step Symbology section of the Workflow tab contains the following options:
| Option | Description |
|---|---|
Fill Color | Represents the fill color for the active step in the workflow |
Outline Color | Represents the outline color for the active step in the workflow |
Outline Width | Represents the outline width for the active step in the workflow |
Text Color | Represents the text color for the active step in the workflow |
Restore Defaults | Restores the default active step representation: yellow fill with black outline and text |
Hinweis:
Disabling any of the options will not change that parameter on the active step.
Location of interest
You can choose location of interest settings on the Area of Interest tab.
LOI overlapping
Use these settings to control if and how the areas of interest (LOI) for your jobs are allowed to overlap.
| Option | Description |
|---|---|
Allow | Any job LOI can overlap another job's LOI. |
Disallow | No LOI can overlap any other LOI in the system. |
Disallow by Job Type | LOIs for jobs of the same job type cannot overlap each other. |
Hinweis:
Jobs that are closed are not considered when evaluating for overlap.
AOI edit extension
Use these settings to further restrict user access to data in the job's area of interest while editing a feature.
There following LOI Overlapping options available:
- Warn users when selecting features completely outside the job AOI.
- Prevent users from selecting features completely outside the job AOI.
- Allow edits to features completely outside the job AOI.
Operator controls which behavior the above rules will be applied to:
- Completely Outside—This applies the rules above to edit operations happening to features entirely outside the job's area of interest. This operator ignores features that touch the AOI boundary; this is considered to be within the AOI.
- Outside—This applies the rules above to edit operations happening to features within the job's area of interest and also features that touch the AOI.
Buffer Distance allows you to expand the extent of the jobs AOI for which the AOI edit extension rules apply. For example, warn the user when selecting features outside the job AOI plus the distance specified as the buffer.
Security
You can configure security settings on the Security tab.
User store
Use these settings to change how users can connect to the Workflow Manager (Classic) database.
| Option | Description |
|---|---|
Traditional | Users are added to the Workflow Manager (Classic) database individually by an administrator or using an active directory import. They are authenticated to use the application based on their Windows login information, stored in the database. |
Portal | Users are added to the Workflow Manager (Classic) system from an organizational portal or ArcGIS Online by an administrator. They are authenticated to use the application based on their portal login. Hinweis:When using Workflow Manager (Classic) for Server, the Portal user store will work with a federated server only. |
Only a user with administrative privileges can change the type of user store for a Workflow Manager (Classic) database. Switching between traditional and portal user store modes refreshes the active users to those configured for that mode. Users set up in a mode are preserved, even if the user store is switched at a later date. Before you can switch the Workflow Manager (Classic) repository from traditional to portal in ArcGIS Workflow Manager (Classic) Administrator you must add and sign into the portal in ArcGIS Pro.
User authentication
When enabled, this feature allows Workflow Manager (Classic) to authenticate users against a domain.