We need to enable COGO on a line feature class with branch version. Is it OK? How this may affect the database?
As you may know, Enable COGO (Data Management Tools) | ArcGIS Pro documentation adds 5 new attribute fields to your line feature class. As a result, the new fields will be part of the branch's attribute table and visible and editable by all users. You may want to test in a non-production branch before enabling COGO on production data to see if there are any negative items. From what I've read, enabling COGO on a line feature class in a branch version is fine and is a common practice for survey data/land information data.