Requesting electronic signatures for a formal review
Overview
Note: Project administrators can set all new formal reviews to require electronic signatures by default in Project Settings (Project Administration Console).
Blueprint allows review creators to request electronic signatures from approvers in a formal review. Electronic signatures can only be enabled for all approvers in a formal review.
To request electronic signatures from approver(s):
Note: In order to configure a formal review package, you must first create a baseline to include in the review package.
-
Click the New button, point to Child Artifact and then click Review.
-
Select a baseline to include in the review.
Click OK.
Note: Only after you select your baseline can you enable Require electronic signatures for formal reviews.
-
Select Require electronic signatures for formal reviews.
The electronic signature feature can only be enabled for all approvers in a formal review.
-
If you require meaning-of-service definitions to be assigned to users, select Require Meaning of Signature (MoS).
Enabling this option will also require reviewers to provide their user name in addition to their password to electronically sign off. -
Select the users you want to include in your review and then click OK.
When approvers begin the review and either approve or disapprove an artifact, they must provide electronic signatures either via federated authentication or password authentication. If meaning-of-signature definitions are required, approvers included in the review in multiple roles will also have to select the one that applies to the current decision.
