About processes that can be modified for custom task types

Human-centric processes assign tasks to participants of review and approval stages. The processes are available to you to use as a basis to create custom task types. They are located in the /processes/core/ folder in the ReviewCommentingAndApproval application. (See Processes under ReviewCommentingAndApproval/processes/core .)

The Review, Commenting, and Approval building block uses the following human-centric processes to assign review and approval tasks to participants.

ReviewCommentingAndApproval/processes/core/AssignTaskToInitiator
ReviewCommentingAndApproval/processes/core/AssignTaskToReviewer
ReviewCommentingAndApproval/processes/core/AssignTaskToApprover

To create a custom task, you can copy one of the processes and modify it in your own application. For information about the processes, see Processes under ReviewCommentingAndApproval/processes/core .)

In Workbench, It is recommended that you retrieve the ReviewApprovalAndCommenting application and use the processes as a basis for your custom task type.

Each process you create for a custom task type must have the following input variables:

Variable name	Data type	Description
useReplyToComplete	boolean	Specifies whether to use email to complete the review.
taskInstructions	string	The instructions or description of the review stage.
taskDocument	document	The document to review.
reviewTitle	string	The title of the review.
reviewId	string	The unique ID for the review. Commonly called the review Context ID.
participantTO	ParticipantTO	The identifier for the participant.
inArsProcessName	string	Required only when assigning tasks to approvers, it stores the name of the process to invoke to create the approval routing slip.

For human-centric processes, no records of Process IDs are associated with the processes until the process starts. It is a requirement that the first operation that you create for custom task types is a Pre Assign Task operation. (See Review Commenting & Approval (system) .) The Pre Assign Task operation is required for the following reasons:

To retrieve the process ID. The Pre Assign Task stores the process ID of the corresponding process instance. The process ID is required to invoke other operations for human-centric process.

The Post Assign Task operation requires a participant ID (ParticipantTO value), a Review ID (string value), and a task document (document value). To use the Post Assign Task operation, ensure that the participate ID is available. It is necessary that the Post Assign Task is the last operation in your process to start any post-processing process after the review stage completes.