ArcGIS Workflow Manager (Classic) helps simplify your data management strategy. It ensures that your users are accessing the right data at the right time.
Data access controls
Workflow Manager (Classic) has tools to help manage your data access. Each user is assigned a database login, so in many cases, users do not ever need to manually connect to the database themselves. The geodatabase version they are using can also be tracked as a property of the job, which helps in reducing errors (editing the wrong version) and can also help in saving users time while setting up their data.
To learn how to configure database logins for your users, refer to the Adding data workspace connections using the Workflow Manager Administrator topic.
Version management
Workflow Manager (Classic) can manage data versioning and allows multiple users to edit data in their own version. There are two types of versioning: traditional versioning and branch versioning.
Traditional versioning
The data stored in a geodatabase can be edited by multiple users via traditional versioning. Each user who requests a map edit is given their own child version of the map document so they may make edits separate from other users. Once the user has completed their edits, the child version may be reconciled and posted back to the parent version.
In a workflow management environment, administering manual version management is difficult and inefficient. Versions must be tracked, including which version each job is working on, the connections to a version, and cleanup. Workflow Manager (Classic) automatically manages versions and frees the user from this responsibility. Instead of using ArcCatalog to delegate job versions, you can associate a version with a job and Workflow Manager (Classic) will handle the rest.
With Workflow Manager (Classic), you can leverage and take advantage of versioning without requiring a deep understanding of it. For more information, see Maps and versioning in Workflow Manager (Classic).
Branch versioning
Branch versioning manages multiuser editing by publishing the data as a feature service. It creates a version management service to manage versions. For more information, refer to Enterprise data management strategies.
Workflow Manager (Classic) supports branch versioning with the same level of management as traditional versioning. When a job is connecting to a feature service data workspace, Workflow Manager (Classic) can check the job version, create a new version, edit data, and delete job versions.