Branch Versioning + Data Reviewer Checks Issue

[MarkGroom]

Hi all. We are preparing our database to be usable with Workflow Manager. We have prepped and published our database (Branch versioned, Arcade Attribute Rules, etc.), and is more/less ready to use in WFM.

We have hundreds of Data Reviewer batch checks set up for our outdated system - that we want to incorporate/run at the end of a Workflow Job. We are having trouble applying these Data Reviewer checks in a versioned database. We don't want to have to up-end and re-write/map these Data Reviewer Checks for each new environment if we don't have to.

Brainstorming, we are thinking of perhaps making a version of the Default database, that editors will then create a version of and edit (a QAQC version, that users will then branch off of).

We don't feel as if this is the first instance of this speedbump - we value any input or recommendation. Thanks for your time.

[DanMoore]

One thing to mention is that you can only create branch versions off of default(Default-QAQC-child won't work for branch versioned data). You can manage who posts edits by utilizing users that have the "manage all" privilege in their role - https://enterprise.arcgis.com/en/portal/latest/administer/windows/roles.htm

[JayCary]

It sounds as if you are trying to use a Reviewer Batch Job (.rbj) from Workflow Manager (Classic?) to validate features shared through a branch-versioned feature service. If so, then the problem you're encountering may be due to the fact that Batch Job-based validation only supports traditional and non-versioned workspaces.

For branch-versioned services, the recommended workflow is to use Data Reviewer's checks that have been integrated into Attribute rule workflows and the Validation service.  Workflow Manager 10.9.1 includes a new step (Evaluate Data Quality) that integrates this service into a job.

The Q2 2022 release of ArcGIS Pro will include an automated method for converting Reviewer Batch Jobs to Attribute rule CSV.