You can set up your review process so that reviewers are
required to authenticate with the Jazz™ server
each time they complete a review. Reviewers authenticate by providing
their electronic signature (e-signature).
About this task
You can define artifact preconditions for each user role
by configuring an Operation Behavior on the Process Configuration
page of the project area. In the web client, you can select preconditions
for saving the artifacts that your organization requires to be signed
at the completion of a review. You can require e-signature at formal
review for these test artifacts:
- Test plans
- Test suites
- Test cases
- Test scripts
- Test case results
- Test suite results
Procedure
- In the web client, log in as a user who has permission
to save project areas. These users have permission to save project
areas:
- Users who have permission to save the project area in the
process configuration
- Users who are administrators of the project area
- Users who have permission either the JazzProjectAdmins or
JazzAdmins repository group permissions
- In the Quality Management application, click the Admin (
) menu and then
click Manage This Project Area. For
details about logging into the administrative pages, see Logging in for project administrators and team leads.
- In the navigation pane, click Preconditions &
Follow-up Actions.
The Preconditions and
Follow-up Actions editor opens and shows the operations that are available
for each test artifact type.

- In the list of operations, find the Save Formal Review
operational behavior for the user role that you want to apply a precondition.
If you want to assign a different role or time frame than
the default selections, you must copy or create a configuration. For
details, see "Copying precondition configurations" and "Creating
precondition configurations".
- In the Action column, click the Edit Configuration (
) icon. Tip: In the Save
Formal Review editor, you can verify and change the user role that
you apply preconditions to.
- Next to Preconditions, click the Add icon.

- In the Add Precondition window,
select a precondition for the appropriate artifact. For
example, select E-Signature Required for Execution Result
Formal Review.
- Optional: Edit the precondition title and type
a description. The title is displayed to users in the E-Signature
Required window. You might want to edit the title to emphasize process
or governance requirements in your organization. The description is
displayed as the Action in the E-Signature Required window. You can
use the ${action} and ${name} variables
in the description. For example, you might type Setting
my verdict to "${action}" for the "${name}" request.
- Select e-signature options:
- Optional: Add the e-signature requirement for
other test artifact types by repeating steps 6 through 9.
- Click Save on the project area page.
Results
After you require user authentication for reviews, reviewers
are required to supply a password when they save a review.
Example
This example shows the settings for a precondition for saving
a test plan formal review.

When a user who
matches the assigned roles tries to approve and save a formal review
in a test plan, this window is displayed:

What to do next
By configuring the E-Signature Required for Lock, Unlock
precondition, you can require users to apply an e-signature before
they lock and unlock artifacts for editing. When you configure that
precondition, you can also enable comments or predefined comments
that users must enter to apply the e-signature.