Global settings that are applied to all jobs and are split into three sections:
For each setting, click 
at the bottom of the section to apply any changes made.
To cancel changes and revert to the last saved state, click 
.
General
The General section contains the following settings which are applied globally:
| Setting | Description |
|---|---|
| Conflict Resolution | |
| Include Diff Views With Conflict Extraction | Conflict child jobs will include information about the conflicting features based on the Oracle Workspace Manager CONF views. In addition to this, the Workspace Manager DIFF views can also be requested which includes information about the other users' non-conflicting changes which can help to put the conflicts into context |
| Try to automatically resolve any conflicts | When selected, 1SMS will attempt to fix any conflicts detected, before creating a child for fix-up action. For more information, please see Automatic Conflict Resolution. |
| Maximum number of automatic conflict resolution retries | Sometimes, Oracle Workspace manager (particularly on Oracle 11g) doesn’t return all conflicts when requested. To resolve this, auto conflict resolution can be tried a number of times to ensure that all conflicts have been resolved. This setting can be used to specify how many times to retry if conflicts aren’t all resolved. A low number might result in unresolved conflicts. A high number might result in the job taking longer and using more resources before going to a conflicted state. |
| Automatically resolve conflicts using the latest changes for the following columns |
Enter the column names you want to apply this setting to, separated by line. Note: This applies to non-spatial conflicts only. |
|
Job ID |
|
| The column in the feature database tables that will be populated with the 1SMS Job ID on update | The name of the column populated by 1Exchange and used by 1Validate to indicate which features have been uploaded by the current job and therefore need validation. A database administrator must ensure that all tables that contain data to be extracted and submitted include this identically named column. The column must be an integer type and does not need to be indexed. |
| Quarantine | |
| Jobs enter the Quarantine state prior to merging | This requires a job to be checked before completion, and stops the changes being immediately applied to the central database once validated. |
| Worklist Customisation | |
| URL of a custom logo to display in Worklist | Enter the URL of an image to use it as a custom logo in the top right corner of the Worklist interface. |
| Enable the light theme for all users | Activating will apply the light theme to all users instead of the default dark theme on next load of the Worklist. |
| Error Handling | |
| Clean up uploaded files on submission error |
Toggle on or off to delete the uploaded files in the event of a submission error. Note: This is set to on by default |
Notifications
1Workflow has the ability to send email notifications on job state changes and in the event of errors. For details around these settings please refer to
Services
| Setting | Description |
|---|---|
| 1Workflow host and port |
The location of the 1Workflow host and port e.g:
|
| 1Plan host and port |
The location of the 1Plan host and port e.g:
|
