Location Referencing ライセンスで利用可能です。
The LRS Locks table allows you to view and release line, route, and event locks. You can view existing Location Referencing locks, acquire new locks, and release existing locks.
The Locks Table button 
on the Location Referencing tab is available if an LRS Network from a conflict prevention-enabled LRS is added to the Contents pane. Click the Locks Table button to open the table.
The easiest way to differentiate between the lock types is to look at the contents of the Event column. If a cell in the Event column contains a value, the lock is an event lock. If a cell in the Event column is blank, the lock is a route lock.
The following is an example of event and route locks in the LRS Locks table:
The LRS Locks table contains route, line, and event locks. The easiest way to differentiate between the lock types is to look at the contents of the Event column. If a cell in this column is populated, it is an event lock (point 2 above). If a cell in the event column is blank, it is a route or line lock (point 1 above).
Tools available in the locks table
| Tool | Tool name | Tool description |
|---|---|---|
Selection | ||
| Select All | Selects all the records in the locks table and shows the selection on the map. |
| Zoom To | Zooms to the routes associated with the highlighted locks on the map. |
| Switch Selection | Switches the selected rows |
| Clear Selection | Clears any selected rows in the table. |
| Copy Selection | Copies the selected rows. |
Release locks | ||
| Release selected locks | Releases the locks from the selected rows. This tool is enabled only when all the selected rows have their releasable status values set to Yes. |
| Release all releasable locks | Releases all the locks whose releasable status value is Yes. There is no need to select rows. |
| Release highlighted locks | Releases the locks from the highlighted rows. This tool is enabled only when all the highlighted rows have their releasable status values set to Yes. |
Highlighted | ||
| Unselect Highlighted | Removes the highlighted rows from the current selection set. |
| Reselect Highlighted | Updates the current selection set to highlighted rows (only). |
| Switch Highlighted | Switches the highlighted rows. |
| Clear Highlighted | Deselects the currently highlighted rows. |
Right-click the row | ||
| Flash | Flashes the route on the map. |
| Zoom To Selection | Zooms to the route on the map. |
| Pan To Selection | Pans (center) to the route on the map. |
| Select/Unselect | Selects or unselects the row in the table and on the map. |
| Highlight/Unhighlight | Highlights or unhighlights the row in the table and on the map. |
| Pop-up | Shows the attributes for the route on the map. |
Filters in the locks table
Expedite sorting of locks in the table using the available filters for network, user, version, event, line name, or route name. The filters can be used individually or in combination to show only those locks that meet these conditions.
After a value is changed in a filter, the filter is highlighted in blue. The filter is applied to the table only when you click Apply. Once the filter is applied, the cell is no longer highlighted.
Releasing locks
Locks can only be released if the releasable status value is Yes.
Description of the Releasable column in the locks table
| Releasable status | Reason |
|---|---|
Yes | The lock is owned by the logged-in user (in any version), and the route or event has not been edited. |
On Post | The lock is owned by the logged-in user (in any version), and the route or event has been edited. |
No | The lock is owned by another user. |
To release a lock, select a row with the releasable status value of Yes and click the Release Selected Locks button 
. Alternatively, click the Release All Releasable Locks button 
to release all locks with the releasable status value of Yes without selecting any rows.
Impact of the user and version on releasable status
The releasable status reported in the locks table is dependent on the logged-in user and database version being edited. For example: The logged-in user is user22 and the version is Version2.
The first three locks were acquired by user22 using Version2. Since the user saved the edits, the releasable status value is On Post (point 1 above).
The next three locks were acquired by user22 using Version2. Since the user did not save any edits, the releasable status value is Yes (point 2 above).
The final lock was acquired by user11 using Version1. Since the logged-in user is different than the user who acquired the locks, the releasable status value is No (point 3 above).
In another example, the logged-in user is user11 and the version is Version2.
The first six locks were acquired by user22 using Version2. Since the logged-in user is different than the user who acquired the locks, the releasable status value is No (point 2 above).
The final lock was acquired by user11 using Version1. Since the logged-in user is the same as the user who acquired the locks, and they did not save any edits, the releasable status value is Yes (point 1 above). It would have been the same case if the logged-in user and version were user11 and Version2, respectively.