Prereview and postreview process development considerations

It is recommended that custom prereview and postreview processes are short-lived processes that complete in minimal timeframes. Do not use long-lived processes containing operations that wait for a response. For example, do not use operations from the User service, Wait service or use Event Receives.

If your process requires a time-intensive short-lived process that does not impact the review and requires intensive processing to complete, create a separate subprocess. Then, in your custom prereview or postreview process, invoke the subprocess and set the Invocation Policy to Do Not Wait For A Response. For example, you have a requirement to extract the comments from the PDF document in a postreview process for storage. Extracting the comments from a PDF document does not impact the review itself and can be completed in the prescribed manner.

You can use the building block operations in custom prereview and postreview processes that retrieve information, such as getReviewStage, getReviewDocument operations and event throws. Do not use operations that modify the review, such as the reviseReview operation that changes the state of the review.

For prereview processes, do not modify the PDF document that can cause subsequent Assembler operations to fail. For example, do not policy-protect a PDF document. In addition, ensure that you apply usage rights to the PDF file to allow Adobe Reader users to add comments and apply signatures to the PDF document.

For postreview processes, do not modify the document value provided in the inReviewDocument when you are using client side signatures for approval stages. Modifying the document value breaks the digital signature.