About Resolving Job Conflicts

An enterprise industry model supports two types of feature locking. The main difference is the handling of job conflicts. A job conflict occurs if the same feature is modified in different jobs.

Optimistic Feature Locking

If you work with several jobs, use these techniques to ensure that feature modifications do not conflict with each other.

• Before you change the job status, check the job manually for conflicts.
• If you change the job status, the system automatically checks whether the job contains features that were modified in other jobs.
• Use the Job Manager to check for job conflicts.

Example

1. Create a job X, and modify feature 1000.
2. Create a job Y, and delete feature 1000.
3. Set job X to pending. A warning is displayed.
4. Set job Y to pending. This is not allowed because there is a job conflict.

Pessimistic Feature Locking

Pessimistic Feature Locking detects any job conflicts as early as possible. For example, in Job A, you add a transformer on a pole. In Job B, User B selects the same pole to delete it from the database. User B is alerted immediately that the feature is locked. User B cannot modify the feature.

To solve the job conflict, user B contacts you. You can jointly decide how to proceed. For example, use the Partial Posting command to extract a the feature from the current job and change its state to Live. Then, that feature can be modified again in the other job.