There are three checks performed to determine editing status:
The workspace matches the Lucity geodatabase.
The version of the geodatabase is configured with Lucity.
The feature classes are linked to Lucity.
Processes before saving edits:
If the feature's commonID field is updated, the extension will check to see if the feature already exists in Lucity. If it does exist, the extension will populate the feature's attribute data with the information in Lucity.
Note: This is not the case if the GIS field is not null or if the Lucity field is null.
If a shape or area is changed and the always update length are option is checked in the Feature Class setup, then the Lucity length and area fields will be updated.
Special Situations after edits are saved:
If editing intersections lock is turned ON, the street names and the intersection diagram will be automatically updated.
Updates the Segments tab in the structures module in Lucity
Updates the to and from street name fields
If the record is not locked, the total pavement area in Lucity will be updated
Update to and from Node IDs
If a the Lucity field XX_SN_ID exists and is populated, the street fields are updated.