Job Management defines how responsibility is distributed across users in your organization.
Job Management isolates each job's edits in a branch version (a private workspace) and merges them into the shared default version only when the job is closed. Roles decide who is allowed to perform each step of that flow.
Administrators can manage all of:
•Jobs
•Groups
•Users
Only portal administrators control who can access Job Management by registering portal groups and managing their membership. They can also configure permissions for the Worker role across the Job Management system.
They have full access to all jobs in Job Management - enabling them to support users by managing any job at any stage of its life cycle.
Portal administrators have the following capabilities across all jobs in the system:
•View all jobs
•Open any job for editing
•View job history
•Complete or close any job
•Put any job on hold
•Re-assign any job
Oversees the full job life cycle. A supervisor creates and assigns jobs, monitors progress, reviews and validates completed work, resolves conflicts, and closes jobs. Supervisor permissions are fixed and cannot be customized.
Supervisors have full administrative control over jobs within their group, including the ability to open, close, and modify jobs.
Supervisors need the Manage all portal privilege to post jobs. This privilege also allows them to edit the default version, even when it is protected. To prevent this, block default version editing for the feature services where supervisors should not edit the default version.
Before you start, protect the default version (SDE.DEFAULT) of your branch versioned geodatabase. For instructions, see Manage branch versions in the ArcGIS Pro documentation.
•blockDefaultVersionEditing: Property of the version management service in the AppJSON. It is an array of feature service URLs. Edits to the default version are blocked for every feature service listed.
To block default version editing for supervisors:
1.Open the AppJSON of your Job Management app.
a.Open the application in VertiGIS Studio Web > Press Ctrl + Shift + E.
b.Open VertiGIS Items Manager.
2.Locate the version-management-service entry.
3.Add the blockDefaultVersionEditing property and list the URL of each feature service to protect.
4.Save the AppJSON.
Example:
{
"id": "version-management-service",
"$type": "version-management-service-type",
"useAsyncTasks": false,
"blockDefaultVersionEditing": [
"https://<server>/server/rest/services/<service>/<service>/FeatureServer"
]
}
Edits to the default version are only blocked for the feature services listed in the array.
The Worker role is optional. A group consisting only of Supervisors is sufficient for most organizations.
Workers are best suited for organizations that need a clear separation between those who coordinate and oversee jobs and those who carry out the fieldwork, such as when field crews and project managers operate independently, or when tighter control over who can create, assign, or close jobs is required.
Workers can always complete jobs. Administrators can also configure additional permissions for the worker role.