Using Event Editor during your everyday workflows, you may need to view and release locks. The locks table in Event Editor allows you to view and release route and event locks for advanced linear referencing systems (ALRS) with conflict prevention enabled. For more information about conflict prevention, see Conflict prevention. For example, you may want to add events to a group of routes in a new subdivision. Before you acquire locks, you could use the locks table to see if any locks exist on the routes where you want to add events. Once your editing is complete in the area, the locks table can be used to release any locks on routes without changes. The locks on the routes with edits would be released when changes from the version are posted to the lock root version.
The locks table can be opened from the Versioning group of the Review tab. Clicking the Locks button opens the locks table in Event Editor.
Locks table tools
The locks table can be used to view locks or release existing route and event locks with the buttons at the top of the toolbar. A lock or group of locks can be highlighted by selecting the lock records in the table.
Note:The Do not prompt to acquire event locks check box is unchecked by default. If you want locks to be automatically acquired when editing in Event Editor and no prompt message to appear, check the check box. This option will only be applied to the local machine.
The table is populated with 25 locks per page. To browse through the pages of locks, use the Next Page button , Last Page button , Previous Page button , First Page button , and the page number drop-down list.
|Function or tool||Description|
Clears all highlighted records in the locks table.
Highlights all records in the locks table.
Zooms to the routes associated with the highlighted locks in the table.
Zooms to the routes associated with the selected locks in the table.
Centers on the routes associated with the highlighted locks on the map.
Releases locks on highlighted records in the locks viewer table. If any locks were acquired by another user, acquired in another version, or have pending changes, a message appears and those locks remain.
Refreshes the list of locks. This also refreshes the list of values for each filter based on which users, versions, events, and routes are associated with the updated list of locks.
Transfers locks on highlighted records in the locks viewer table. You need to select the geodatabase version using the Version drop-down arrow on the locks table to activate the tool. If any user is in an edit session using the same geodatabase version, a message appears and those locks remain with the existing user.
Transfers locks on selected records in the locks viewer table. Select the geodatabase version using the Version drop-down arrow on the locks table to activate the tool. If any user is in an edit session using the same geodatabase version, a message appears and those locks remain with the existing user.
This tool is only available when Allow Lock Transfer is selected on the ALRS properties dialog box and Event Editor is configured to show the transfer locks tools. For more information, see Enabling conflict prevention in the ALRS and Configuring the Event Editor Editor web application.
Filters in the locks table
As Roads and Highways users complete everyday editing workflows, the locks table could have route and event locks from a variety of users, in different versions, on a variety of events, and on a variety of routes. To expedite the sorting of the locks in the table, filters are available based on the user, version, event, and route in which the locks were acquired. The filters can be used individually or in combination to only show the list of locks meeting those conditions. Filtering by user or version provides a drop-down list of all the different values present in the locks table. The event filter contains all the event layers in the map. To filter by route, paste a route ID into the text box and press Enter, or type the beginning of the route ID. After three characters are typed, a list of matching route IDs that can be selected appears.
In the previous example, the user locked a group of routes to perform edits on a new subdivision of routes. Once editing is complete, the user wants to release the locks for the routes that were not edited. Table filters could be used to narrow the list of locks to those acquired by that user in the version used for editing.