Recommended Handlers

The core functionality of GDBM XI, namely to reconcile and to post, offers a quick way to get started with GDBM by pointing it at your operational map without requiring additional configuration. GDBM offers flexibility for organizations to customize their programs according their specific needs. However, configuring additional handlers isn’t needed to successfully run GDBM.

If you are interested in using GDBM beyond the out-of-the-box functionality of reconcile and post, the following are a few recommendations of handlers to consider:

PurgeVersionLock

The PurgeVersionLock handler is recommended only if you are seeing constant locking of versions when posting and you have already tried changing your workflow to solve the issue.

IMPORTANT: The PurgeVersionLock handler can cause data loss if it is run on a version that is actively being edited.

SendEmail

The SendEmail handler is beneficial to set up on any error handling steps. This handler notifies you via email if something in the program has gone wrong.

UpdateSubnetworks or ValidateNetworkTopology

You can assign the UpdateSubnetworks or ValidateNetworkTopology handlers to the Program Completion or Post Events. This performs actions on the Default version before the reconcile loop process pushes changes down to all child versions. This prevents the circumstance of pushing dirty areas down to every version.

FindEditedSubnetworks and CollectEditedSubnetworksAndUpdateTimestamps

If you are using the Feeder Services and Circuits-based integration, you should now use the more advanced FindEditedSubnetworks and CollectEditedSubnetworksAndUpdateTimestamps action handlers in pair, given that the UpdateLastUpdateSubnetworkTimeStamps handler has been deprecated. Using the suggested pair of handlers ensures the additional detection of non-network field changes made within the specific GIS Version. If you are not using Feeder Services at all, you should not include either of these action handlers.