Please enable JavaScript to view this site.

Version:

Navigation: » No topics above this level «

Job Management

Prev Top Next More

Job Management is a workflow system that lets your organization create, assign, track, and close spatial jobs using versioned editing. It provides a structured environment where edits are isolated in branch versions and merged back to the default version only when a job is closed.

Job Management features are accessible from the Job Management tab in the toolbar. Users can access these features only if they belong to a portal group registered with the Job Management system.

Administrators also have access to the Groups option to register portal goups with the Job Management system and manage any group already registered.

job-management-toolbar

Key Features

Job operations: Create, assign, reassign, track, and close jobs from a single interface

Automated workflows: Validation and conflict detection

Team collaboration: Role-based permissions for administrators, supervisors, and workers

Getting Started

Job Management requires explicit installation and configuration before it is available to users.

To get started with Job Management:

1.Set up the Job Management service by running the provisioning script.

2.Plan the structure for groups by deciding which hierarchy model fits each team's workflow.

3.Register a portal group with the Job Management system to grant its members access.

4.Add users to the registered portal group in ArcGIS Portal so that they can view and access the Job Management tab in the toolbar.

What Happens During a Job

Understanding the job lifecycle helps you follow the correct steps at each stage:

When a job is created, the system automatically creates a branch version across all feature services linked to the map.

Workers make edits in this isolated branch version without affecting other users or the default data.

During active work, workers reconcile their version with the default version to pull in the latest changes.

When work is complete, the job is marked as completed and a supervisor (or the worker, in a single-level hierarchy) closes the job.

On closure, the system reconciles, releases locks, posts all edits to the default version, and deletes the branch versions.

© 2026 VertiGIS Ltd. All Rights Reserved. | Privacy Center | Imprint
Documentation Version 1.17 (ca68ceb8)