Enabling conflict prevention in the ALRS

Enabling conflict prevention in the ALRS

Conflict prevention can be enabled and configured on the Conflict Prevention tab on the ALRS Properties dialog box. In this dialog box, conflict prevention can be enabled or disabled. If enabled, users will be required to acquire locks on routes and events in order to edit route and events. If disabled, all locks will be removed and Roads and Highways will not coordinate editing via locks to prevent conflicts and measure discrepancies that may result from multiuser editing.

When configuring conflict prevention, you must configure which enterprise geodatabase version to use as the lock root version. The lock root version is the version users must reconcile with to acquire locks or post to in order to release locks. It can be the DEFAULT version or a surrogate of DEFAULT.

It is possible to restrict users from changing these configurations by not granting them write privileges to the LRS_Metadata table. Users that do not have write access to this table can not change ALRS configuration, including the settings for conflict prevention.

NoteNote:

If your ALRS was created in a version prior to Roads and Highways 10.2.2 patch 1, you will need to upgrade your ALRS to Roads and Highways 10.2.2 patch 1 to use conflict prevention. You will also need to upgrade your ALRS to 10.2.2 patch 1. For instructions on upgrading the ALRS, see Upgrading the ALRS.

Conflict prevention is only supported for enterprise geodatabases. It is not supported for file geodatabases.

Steps:
  1. Browse to the ALRS in the Catalog window.
  2. Right-click the ALRS and click Properties.
  3. Browse to the Conflict Prevention tab.
  4. Check the Enable Conflict Prevention check box.
  5. Browse to the lock root version. Use the drop-down arrow to select a version from which to reconcile and post edits. To learn more about managing geodatabase versions, see Creating versions and setting permissions.

    To enable the conflict prevention settings, you must be editing versioned data from an enterprise geodatabase.

Enabling Conflict Prevention in the ALRS Properties

When creating a new ALRS, you will have the option of enabling conflict prevention during the initial ALRS setup. In step 6 of the ALRS setup, you can enable the conflict prevention settings and define the lock root version.

Enabling Conflict Prevention in the initial ALRS Setup

Once conflict prevention has been enabled, all users of the enterprise geodatabase will be prompted to acquire locks on routes and events before performing any editing activities. The View Route Locks tool Unlock Route Tool will be enabled on the Esri Roads and Highways editing toolbar, and the Edit Locks widget Edit Locks will be enabled on the Review tab on the RCE ribbon.

Roads And Highways Editing toolbar with conflict prevention enabled

RCE ribbon with conflict prevention enabled

Disabling conflict prevention in the ALRS

Conflict prevention configurations in the ALRS can be edited by administrators with the appropriate privileges to edit the LRS_Metadata table. If conflict prevention is disabled, users will no longer need to acquire locks on routes and events before performing edits. As a result, the View Route Locks tool Unlock Route Tool will be disabled on the Roads And Highways Editing toolbar, and the Edit Locks Edit Locks widget will be disabled on the Review tab on the RCE ribbon.

Roads And Highways Editing toolbar with conflict prevention disabled

RCE ribbon with conflict prevention disabled

10/14/2014