Adding review and approval stages

You can add four types of stages to a review. (See Review and approval stage types in Managed Review & Approval Solution Accelerator 9.5 Solution Guide .)

The type of stage you choose depends on whether you require a review or approval stage. It also depends whether you want participants to participate one at a time or in parallel.

As part of adding a new review stage, you set parameters to determine whether the stage expires, the duration of the stage, how users complete their tasks, and whether the stage completes immediately after all required reviewers complete their tasks.

Some additional parameters that you can add under a stage include:

This topic does not describe how to configure the additional parameters, just that the XML elements to create a stage.

Complete the following steps to add a review stage:

  1. Nest the <stages> element under the <review_context> element.

  2. Nest a <stage> element under the <stages> element for each stage document to add to the review.

  3. For the <stage> element, set the following attributes:

    • type: A value of PARALLEL_REVIEW , PARALLEL_APPROVAL , SEQUENTIAL_REVIEW , SEQUENTIAL_APPROVAL to specify how the stage executes.

    • name: A name to describe the review stage.

    • taskType: Sets whether the review is completed using email, Workspace, or a custom . Use a value of WORKSPACE, EMAIL_CONNECTED, or CUSTOM to specify how to complete the stage.

  4. Set the timeframe for the stage by setting the following attributes in the <stage> element. (See Setting schedules for stages .)

    • duration_unit

    • duration

    • non_expiring_stage

    • wait_for_expiry

  5. Nest the following elements under the <stage> element:

    <start_date/> 
    <end_date/> 
    <status>PENDING 
    </status> 
    <pre_process_hook/> 
    <post_process_hook/> 
    <assign_task_to_initiator_process/> 
    <disposition/> 
    <moderators/>
  6. Depending on whether the stage is an approval stage or review stage, nest one of following elements under the <stage> element.

    • For a review stage, nest the following set of elements under the <stage> element.

      <reviewers> 
          <assign_task_to_reviewer_process/> 
          <status>PENDING</status> 
          <final_comments/> 
          <disposition/> 
      </reviewers>
    • For an approval stage, nest the following set of elements under the <stage> element.
      <approvers signature type="NONE"> 
          <assign_task_to_approver_process/> 
          <status>PENDING</status> 
          <final_comments/> 
          <disposition/> 
      </approvers>
  7. (Optional) Configure whether to add reminders to participants by nesting a <reminders> element under the <stage> element. (See Adding reminders to stages .)

The following example shows a review stage.

<?xml version="1.0" encoding="utf-8"?> 
<review_context xsi:schemaLocation="http://adobe.com/solutions/rca/reviewcontext" xmlns="http://adobe.com/solutions/rca/reviewcontext" 
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"> 
<initiator domain="" canonical_name="" name="" oid="" email="" isGroup="false"/> 
    <review_id/> 
    <revision>0</revision>      
    <title/> 
... 
...  
<stages> 
    <stage type="PARALLEL_REVIEW" wait_for_expiry="false" name="Basic-ParallelReview" 
    duration="5" duration_unit="DAYS" taskType="WORKSPACE" non_expiring_stage="false"> 
        start_date/> 
        <end_date/> 
        <status>PENDING</status> 
        <pre_process_hook/> 
        <post_process_hook/> 
        <assign_task_to_initiator_process/> 
        <disposition/> 
        <reviewers> 
            <assign_task_to_reviewer_process/> 
        </reviewers> 
        <moderators/> 
    </stage> 
</stages> 
... 
... 
</review_context>

// Ethnio survey code removed