Methods to implement automated review

Available with Data Reviewer license.

ArcGIS Data Reviewer provides multiple options for implementing automated review. These capabilities are flexible and scalable to accommodate both small and large deployments.

Depending on the needs of your organization and your deployment, you can automate data review of features from multiple sources such as those stored in shapefiles, geodatabase feature classes and stand-alone tables, and web feature layers from ArcGIS Enterprise.

The options for automated review are as follows:

• Reviewer batch jobs
• Reviewer rules in a geodatabase
• Reviewer rules in a map

Reviewer batch jobs

Reviewer batch jobs contain configured Data Reviewer checks that validate features stored in feature classes (for example geodatabase feature classes, or shapefiles) and stand-alone tables. Batch jobs are created using tools in ArcMap and stored in a file (.rbj) that can be shared using project templates and packages in ArcGIS Pro.

Consider the following when implementing automated review using Reviewer batch jobs:

• Rules are created using tools in ArcMap.
• A read-only permission on source data is required for creating rules.
• Validation of features is supported using ArcMap (Batch Validate tool), geoprocessing (Execute Reviewer Batch Job tool), ArcGIS Workflow Manager (Classic) (Run Reviewer Batch Job step), and ArcGIS Server (executeJob REST operation).
• Features from multiple data sources (geodatabase and shapefiles) are supported.
• Nonversioned and traditional versioned geodatabase sources are supported.
• Errors are stored in a specified geodatabase within a Reviewer dataset.
• Errors are managed manually using ArcMap (Reviewer table), ArcGIS Pro (Reviewer Results view), and ArcGIS Server (getResults REST operation).

Learn more about migrating from ArcMap to ArcGIS Pro for data validation

Reviewer rules in a geodatabase (attribute rule-based workflows)

Reviewer geodatabase rules are configured Data Reviewer checks that validate geodatabase feature classes and stand-alone tables using attribute rule-based workflows. Rules are created using tools in ArcGIS Pro and are stored in a geodatabase that can be shared by exporting to comma-separated values files (.csv) or XML workspace document files (.xml).

Consider the following when implementing automated review using Reviewer geodatabase rules:

• Rules are created using tools in ArcGIS Pro.
• Enables assessment of a feature’s quality before/during (attribute constraint rule) and after editing (attribute validation rule).
• An ArcGIS Desktop Standard license and data owner's permission on the source data is required for creating rules.
• Attribute validation rules are supported using ArcGIS Pro (Error Inspector), geoprocessing (Evaluate Rules tool), and ArcGIS Server (evaluate REST operation).
• Attribute rules are supported in file geodatabase (using ArcGIS Pro) and branch versioned enterprise geodatabase (using ArcGIS Enterprise) deployments.
• Features stored in geodatabase features classes and stand-alone tables are supported.
• Errors are stored in system-maintained tables along with production data.
• Errors are managed automatically.

Learn more about managing Reviewer rules in a geodatabase

Reviewer rules in a map

Note:

Reviewer rules will not be supported in map-based workflows in subsequent versions of ArcGIS Pro, you are strongly encouraged to use attribute rule-based workflows.

Reviewer map rules are configured Data Reviewer checks that validate feature layers referenced in a map. Rules are created using tools in ArcGIS Pro and are stored in a map that can be shared using project templates and packages, map files and packages, and layer files and packages in ArcGIS Pro.

Consider the following when implementing automated review using Reviewer map rules:

• Rules are created using tools in ArcGIS Pro.
• A read-only permission on source data is required for creating rules.
• Validation of features is supported using ArcGIS Pro (Run Reviewer Rules command).
• Features from multiple data sources (geodatabase, shapefiles, and web feature layers) are supported.
• Nonversioned, traditional, and branch versioned geodatabase sources are supported.
• Errors are stored in a specified geodatabase within a Reviewer dataset.
• Errors are managed manually using ArcMap (Reviewer table), ArcGIS Pro (Reviewer Results view), and ArcGIS Server (getResults REST operation).

Learn more about creating Reviewer rules in a map

The following diagram illustrates which automated validation to use according to your GIS deployment scenario: