Quality management teams typically use preconditions and follow-up actions for review and approval, e-signature, and test execution. You can assign preconditions and follow-up actions in the Administration web UI or in the Eclipse client. For more information about configuring preconditions and follow-up actions, see these resources:
The following table lists the preconditions for quality management.
| Precondition | Description | Affected operation | Configurable? |
| Allow Test Data Record Selection Before Execution | Use this precondition to allow test data records to be selected before execution. | Execute Test Case | No |
| Disallow Execution of Test Case Execution Record if Owner is Not Executing it | Use this precondition to prevent test case execution records from running if anyone other than the owner attempts to run the execution record. | Execute Test Case | No |
| Disallow Execution until Build Specified | Use this precondition to prevent test execution until a specified build completes. This precondition affects only test executions that are tied to a build. The precondition does not affect time-based execution. | Execute Test Case and Execute Test Suite | No |
| Disallow Execution until Test Suite, Test Case, or Test Script is Approved | Use this precondition to prevent test execution until certain artifacts are approved. | Execute Test Case, Execute Test Suite, and Execute Test Script | No |
| Disallow Execution of Test Case if no Test Script is associated with it | Use this precondition to prevent test case execution if no test script is associated with a test case. | Execute Test Case | No |
| Disallow Modifications to Completed Approval Groups | Use this precondition to prevent completed approval groups from being modified. | Save Formal Review | No. For more information, see Disallow modifications to completed approval groups precondition. |
| Disallow Modifications to Formal Review of Approved Artifacts | Use this precondition to prevent modifications to the Formal Review section of approved artifacts. | Save Formal Review | No |
| Disallow Saving of Test Plans, Test Cases, Test Scripts, Test Suites, and Results with State Approved or Retired | Use this precondition to prevent users from editing and saving certain test artifacts after the artifacts are approved. | Save Test Plan, Save Test Case, Save Test Script, Save Test Suite, Save Test Case Results, and Save Test Suite Results | Yes. For more information, see Allowing users to edit approved artifacts. |
| Disallow Transition to Approved Until All Test Cases Approved | Use this precondition to prevent test plans from moving to the Approved state until all of the associated test cases are approved. | Save Test Plan | No |
| Disallow Transition to Approved Until All Test Scripts Approved | Use this precondition to prevent test cases from moving to the Approved state until all of the associated test scripts are approved during a Save Test Case operation. | None | No |
| Disallow Transition to Under Review until Associated Work Items Resolved | Use this precondition to prevent certain artifacts from moving to the Under Review state until all of the associated work items are resolved. | Save Test Plan, Save Test Case, and Save Test Suite | No |
| Do not allow Execution of Test Case Execution Record until the Test Case and the associated Test Plan are approved | Execute Test Case | No | |
| E-Signature Required for Lock, Unlock | Use this precondition to require an E-Signature when users lock or unlock certain test artifacts. | Save Test Plan, Save Test Case, Save Test Suite, Save Test Script, Save Test Case Results, and Save Test Suite Results | Yes. You can require free-form comments or predefined comments to apply the E-Signature. |
| E-Signature Required for Formal Review | Use this precondition to require that an e-signature is supplied when the status of an approval or review record is changed for a test plan, test case, test suite, test script, execution result, or test suite log. | Save Formal Review | Yes. You can require free-form comments or predefined comments to apply the E-Signature. For more information, see Requiring e-signature for the review process. |
| Require an Actual Result for Script Steps | Use this precondition to make the Actual Results column of a manual test script mandatory under certain conditions. | Save Test Case Result | Yes. For more information, see Defining a precondition to mandate actual results in a manual test script. |
| Require Defects before Failed Results Reviewed | Use this precondition to require that defects be associated before failed results can be reviewed. | Save Test Case Result | No |
| Require Prior Test Artifact State Transition | Use this precondition to prevent an artifact from moving to a state in another state group until its child artifacts move to a state in the groups that you specify. For example, you can configure a precondition to prevent someone from saving a test plan in a state in the Approved group until all of the child test cases are approved. | Save Test Plan, Save Test Case, Save Test Suite | Yes. You can select the state groups that the rule applies to, such as Reviewed or Published. For test case results and test suite results, you can apply the rule to current results or all results. |
| Required Approvals | Use this precondition to restrict artifact state changes based on the artifact's approval status. | Save Test Plan, Save Test Case, Save Test Script, Save Test Case Results, and Save Suite Results | Yes. For more information, see Defining preconditions for reviews and approvals. |
Each individual quality management operation, such as Save Test Case, can have several preconditions that are defined for it. Preconditions are defined as part of a configuration, which includes the operation, the role that can do the operation (who), and the time frame of the operation (when). All of the operations in the following image apply to the Everyone role, which is the default, and have no limits on when each operation can be done.

If you want to assign a different role (who) or time frame (when) to a precondition than the default values, you must copy a configuration or create a configuration by clicking the Configure command.
By default, the configurations that are you set in the project area apply for all time periods. However, you can customize configurations so that they apply only for a specific timeline, iteration, or iteration type. Additionally, the Show archived time periods icon toggles the display of configurations for timelines or iterations that have been archived.
Administrators can use the Data Migration Administrator role to create data that is exempt from the normal constraints that are enforced by preconditions and follow-up actions. For example, you might need to migrate data into the Quality Management application by using the REST API. In that case, you can use the Data Migration Administrator role to bypass the process behavior rules and migrate data that violates the version 4 process constraints. With the REST API, you can read and write data without using the web interface.
You can combine this role with other roles, but you must place this role in the first position in the list of selected roles, as the next image shows.

For example, if you need to be exempt from preconditions and follow-up actions so that you can upgrade the software, you might take these steps:
After the upgrade, if you want the user to have the same operational constraints as everyone else, remove the Data Migration Administrator role from the user's role list. If you only move the role in the priority list, the change might not be effective. In addition, if the role will no longer be used after the upgrade, remove the preconditions and follow-up actions that are configured for the role.