In this blog, we will dive into applying the branch versioning functionality discussed in previous blogs to a standard editing and version administration workflow you might encounter in your organization.<\/p>\n
The first steps of configuring and publishing to an ArcGIS Enterprise portal were covered in the previous blog: Branch Versioning: Setting the Stage<\/a>. With that out of the way, we are ready to consume and edit our data within a client application.<\/p>\n"},{"acf_fc_layout":"sidebar","content":" While similar workflows can be scripted or performed in other field or web apps, this blog will focus on usage within ArcGIS Pro.\u00a0 In the below workflows, it is assumed that Version Management capabilities are active within the published service and the Default version is protected.<\/p>\n","image_reference":false,"layout":"standard","image_reference_figure":"","snippet":"","spotlight_name":"","section_title":"","position":"Center","spotlight_image":false},{"acf_fc_layout":"content","content":" The first step is to consume our branch versioned data from ArcGIS Enterprise portal. This is accessed through the Catalog pane in ArcGIS Pro as with any other feature service<\/a>; however, the ability to create and interact with versions through this service is enabled by the version management capability.<\/p>\n Once you have the data in your map view, the editing workflow is initiated by creating a named version where the edits can be performed in isolation from the Default version. We have a couple of options to create new versions: using the Create Version<\/strong> geoprocessing tool, or from within the UI leveraging the New Version<\/strong> tool found within the Versioning<\/strong> group.<\/p>\n Here is a quick overview of creating a version using the Versions tab:<\/strong><\/p>\n <\/p>\n An important step to note when creating versions is the access permission<\/a> chosen for the version. The access permission plays an important role in controlling which portal users have access to edit data within the version and perform reconcile\/post operations. Here’s a more detailed breakdown of each:<\/p>\n One common versioning workflow is to have editors access public or private named versions for editing with administrators performing reconcile, post, and conflict management tasks against a protected Default version. The choice on whether to set access to private, protected, or public is largely dependent upon your organizations editing and management workflows.<\/p>\n Locks are also important to consider when working with public branch versions. Named branch versions only support one editor at any given time. When a branch version is accessed, a lock is placed on the web service which prevents others from editing.<\/p>\n Once we have created and changed to this new version, we can begin making edits. If editing within ArcGIS Pro is a relatively new concept to you, reference the web help here<\/a> to get started.\u00a0 Also, check out this blog<\/a> which helps dispel some common myths around editing in Pro.<\/p>\n <\/p>\n"},{"acf_fc_layout":"youtube","start_time":"0","end_time":"","youtube_video_url":"Editing our Branch<\/h1>\n
Creating a Version<\/h2>\n
\n
Understanding Access Permissions and Locks<\/h3>\n
\n
Editing Within a Version<\/h3>\n