@ClaudzPora
Indeed, Branch Versioning only supports 2 tiers, the sde.default version and only a child version of sde.default, we cannot create child versions of child versions in Branch Versioning.
The example I provided above was for traditional versioning, where we could create child versions ad deep as we need, in that scenario we could set sde.default as protect, create a QA/QC version from the sde.default and then create all the editing versions as child of the QA/QC version. But this only works with traditional versioning.
You can use ArcGIS Workflow Manager to automate your editing workflows and versioning management for both versioning types, Branch Versioning and Traditional Versioning.
I hope this clarifies.
| Marcelo Marques | Principal Product Engineer | Esri |
| Cloud & Database Administrator | OCP - Oracle Certified Professional |
I work with Enterprise Geodatabases since 1997.
“ I do not fear computers. I fear the lack of them." Isaac Isimov