Geodatabase Version Persistence
We've provided this overview to help you understand how geodatabase versions get persisted in workflows utilizing a combination of transactional data, Segment Analyzer mash up tables and views across multiple applications. A typical use case where this overview is helpful for visualization, is the process of running cross-check validations using Validation Assistant on mash up tables created using Segment Analyzer in conjunction with validations written to directly validate data in your transactional database. Below we'll break down the workflow and the set-up utilized to keep everything in sync.
<<< This topic is still under construction >>>