Adding digital signatures to complete approval stages

Signatures support three options. The <approvers> element has a signature_type attribute that can hold one of the following values:

• NO_SIGNATURE

• SERVER_SIDE

• CLIENT_SIDE

You can optionally add an approval routing slip when you use digital signatures. (See About review tracking sheets and approval routing slips .) If you do not, a signing sheet is attached to the review document that allows approvers to enter final comments and apply digital signatures.

When use you digital signatures, there is a particular series of steps you follow depending on the type of signature you choose. The types of signatures are NO_SIGNATURE , SERVER_SIDE , or CLIENT_SIDE .

If a value for rts_process_name is provided, the process is invoked for all review stages. The output document is stored in ReviewZoneProvider.

If a value for ars_process_name is provided and the signature type is set to NO_SIGNATURE , the system does not invoke the ars_process .

If a value for ars_process_name is provided and the signature type is set to SERVER_SIDE , the system invokes ars_process after the current approval stage is complete. The returned document is stored in ReviewZoneProvider. The system does not verify whether the signatures are applied.

If a value for ars_process_name is provided and the signature type is set to CLIENT_SIDE , the system verifies that the stage is a sequential approval stage. If so, the system invokes ars_process at the start of the stage and assembles the returned document with the review document. This assembled document is served to all approvers in the sequence. Each approver can place comments and signatures against their names or ID. The system expects that the document ars_process generated has a name or ID, a signature, and a comments field for all approvers.