Using custom dispositions and statuses for participants

Before passing a ParticipantTO variable to the Post Assign Task operation, the status attribute must be set. The status attribute in the ParticipantTO variable is set based on the button selected by reviewer or approver when they complete a task.

The reviewer can provide the following statuses:

DECLINED
COMPLETED
REJECTED
CHANGES_REQUIRED

Similarly, an approver provides the following statuses:

APPROVED
REJECTED

Note: The statuses are not used in the default flow for a stage and are kept only for custom use cases.

ParticipantTO also has an attribute named disposition , which is not set by default and is used for custom statuses. The status cannot be modified as they are important for the Review Commenting & Approval Core service.

The Review Commenting & Approval Core service evaluates necessary conditions for review stage execution based on the values of the status. Disposition values are not used in the evaluation and can be changed as required. So, you can use the disposition attribute to store custom statuses when required.

By using a custom task, you can change this task behavior to include custom button names. In some scenarios, you may require different statuses than the ones provided by default. those are available by default. When you use a custom task, you can create new statuses and dispositions.

When this participant instance populated with status and disposition is passed to Post Assign Task. The building block uses the status attribute to evaluate all necessary stage and review flow conditions and store disposition just as an additional attribute with approver. Any call to the Get Review Context XML operation or getReviweContext method) returns all the data related to a review along with the custom dispositions.