Description

When a feature or row is submitted to the Reviewer workspace it becomes a Reviewer result. Data Reviewer exposes a data quality control workflow that helps you review a result, correct any problems with the result, and then verify the fix to the result.

Lifecycle status represents the state of a Reviewer result in the workflow. A result moves through the following three life cycle phases:

1. Review: Initial status written by the tool that submitted the result.
2. Correction: The anomoly identifed by the Reviewer result is fixed or corrected.
3. Verification: The fix to the Reviewer result is verified.

Each life cycle phase contains status values that describe how the result was handled. For example, a result in the Correction phase could have a correction status of Resolved.

This REST operation allows you to change a result's lifecycle status. Changing lifecycle status moves a result between lifecycle phases and indicates how a result was handled within a phase.

For example, a result in the Correction phase could have a life cycle status of Resolved or Mark as Exception. If you have verified the correction to this result, you can change its lifecycle phase to Verification and its life cycle status to Acceptable. Lifecycle status is progressive. A result moves from Review to Correction to Verification.

This operation requires four parameters:

1. sessionId: An existing session Id number in the Reviewer workspace. Represents the session that contains results to update.
2. lifecycleStatus: Lifecycle description code. Valid values are 1-9.
3. technicianName: User that performs the update.
4. filtersArray: Array of filters that identify the rows to update in the Reviewer table.

The response is an object that contains an array of updated object IDs and a success status. If no matching records are found, the response contains an empty array:{"updateResults":[]}.

This operation does not support file geodatabases as Reviewer workspaces.

Parameters

<filters> 

Example Usage

Example 1:

Updates life cycle status values from 1 (Reviewed) to 2 (Resolved) for all results with a severity of 5 in session id 1.

http://localhost:6080/arcgis/rest/services/reviewer/MapServer/exts/DataReviewerServer/ReviewerResults/updateLifecycleStatus?sessionId=1&lifecycleStatus=2&technicianName=Norbert&filtersArray={filtersArray:[{singleAttributeFilter:[{fieldName:"severity",fieldValue:5}]}]}&f=pjson

JSON Response Example

{
 "updateResults": [
  {
   "objectId": 3,
   "success": true
  },
  {
   "objectId": 4,
   "success": true
  },
  {
   "objectId": 1882,
   "success": true
  }
 ]
}

Example 2:

Updates lifecycle status for results in session id 2 that have subtypes 'NewRoad' and 'RoadLine' to 9 (Exception). Request uses a listAttributeFilter.

http://localhost:6080/arcgis/rest/services/reviewer/MapServer/exts/DataReviewerServer/ReviewerResults/updateLifecycleStatus?sessionId=2&lifecycleStatus=5&technicianName=Norbert&filtersArray={filtersArray:[{listAttributeFilter:[{fieldName:"Subtype",fieldValue:['NewRoad','RoadLine']}]}]}&f=pjson

JSON Response Example

{
 "updateResults": [
  {
   "objectId": 10,
   "success": true
  },
  {
   "objectId": 11,
   "success": true
  },
  {
   "objectId": 15,
   "success": true
  }
 ]
}