There currently is no method to:
- Create a workflow specific branch version (eg: Valve Exercise)
- Publish a service from this specific branch version and have field staff make field edits and send them back for QA/QC before a push to default ,like we've always done in the past with Traditional versioning.
However, as @MikeMillerGIS spitballed last week it may be possible to 'Clone' a branch version. This differs from managed versions as there is no need for it to be tracked in order to be reconciled into its parent.
Theoretically this cloned version could be used to create a service in a webmap to allow field editing. This clone is then merged back into the default after appropriate QA/QC.
Delete the clone. Make a new one. Rinse. Repeat.
