Part 11 Compliance

Enable Part 11 Compliance at the project level for a specific project.

When enabled, the system enforces authentication before changing the execution status.

Note

The Part 11 Compliance option is available only when the eSignature feature is enabled in the project.

When Part 11 Compliance is enabled, changing a test case’s execution status prompts an authentication pop-up for Username and Password or Part 11 Authentication Token. The system updates the status only after successful authentication, ensuring that only authorized users can make changes.

Note

The Part 11 Compliance is only applicable to Test Case Approval and Test Suite Approval. The Part 11 Compliance is not applicable to Requirement Review.

Business Rules

  • When updating execution status for multiple test cases via Bulk Operations, the system prompts for authentication only once. After successful authentication, all selected test cases are updated.

  • The system sets the Timezone for “Execution Status Changed By” values based on the user’s location.

  • For Part 11 Compliance enabled projects, uploading the automation result file through Automation API is restricted.

  • Existing projects and users do not have Part 11 Compliance enabled automatically. For any newly created project, even if eSignature is enabled, the Part 11 Compliance feature is disabled by default.

  • If the Part 11 Compliance feature is enabled, and LDAP users can authenticate with Username and Password or Part 11 Authentication Token. SAML users can authenticate with Username and Part 11 Authentication Token. Refer to know how to generate the Part 11 Authentication Token.

  • Inactive or deleted users can not enable authentication.

Impact in Application

Enable Part 11 Compliance to prompt authentication for execution.

Affected Areas in

Description

Test Suite module

  • Select test suites and click Bulk Execute. To update execution status authentication is needed.

  • Import test suite run through excel and if the Execution Status in the file differs, authentication is needed. The execution status can be changed only after authentication.

  • For eSignature-enabled project, changing approval status of test execution requires authentication.

Test Execution Screen

  • Execute individual test suites and update the status for test cases individually or in bulk.

  • Click Set Your Build on test execution screen and reset the execution status to "Not Run." Authentication is requested for this change.

  • When syncing test cases with their latest version, authentication is required.

  • For eSignature-enabled projects, changing the test suite approval status to "Close" requires authentication.

Test Case list view

  • For eSignature-enabled projects, changing the approval status of test cases requires authentication. The test case is approved after successful user authentication subject to the user is added as a Test Case Approver.

How to Enable Part 11 Compliance?

Important

Enable the eSignature feature for the project to use Part 11 Compliance.

To enable Part 11 compliance, perform the following steps:

  1. Go to eSignature and select Approval Access.

  2. Turn the flag on for Part 11 Compliance.

    QPro_Enabling_Part_11_Compliance.png

  3. Click Yes.

Enabling Part 11 Compliance enforces users to authenticate before changing the status of test cases or test steps. Users can opt to disable compliance for test steps.

Diabling Part 11 for Test Step Level

By default, this option is unchecked, so the authentication prompt appears for every test step when you attempt to change its status. To limit authentication to the test case level only, enable this option by checking the box. Once disabled, user credentials are required only when updating the test case status, not for individual steps.

Business Rules

When the Part 11 Compliance feature is enabled, the system prompts you to enter your credentials to authenticate before performing specific actions.

Test Case Operations

Testers can perform the following test case operations depending on the status of the eSignature feature, Part 11 Compliance feature, or their Approver permissions for test cases.

Operation

eSignature Disabled

eSignature Enabled but Not Authorized to Approve Test Case

eSignature Enabled and Authorized to Approve Test Case

eSignature and Part Compliance Enabled and Authorized to Approve Test Case

Create new test cases

Y

Y

Y

Y

Edit unapproved test case/test case version

Y

Y

Y

Y

Approve test cases

NA

N

Y (does not require credentials)

Y (requires credentials)

Edit approved test cases/test case versions

NA

N

N

N

Create a new version of approved test cases

NA

Y

Y

Y

Bulk Approve test cases

NA

N

Y (does not require credentials)

Y (requires credentials)

Test Execution Operations

Testers can perform the following test execution operations depending on the status of the eSignature feature, Part 11 Compliance feature, or their Approver permissions for test execution.

Operation

eSignature Disabled

eSignature Enabled but Not Authorized to Approve Test Suite

eSignature Enabled and Authorized to Approve/Close Test Suite

eSignature and Part Compliance Enabled and Authorized to Approve/Close Test Suite

Create test suite and link platform, release and cycle to it

Y

Y

Y

Y

Approve a test execution

NA

N

Y (does not require credential)

Y (requires credentials)

Close a test execution

NA

N

Y (does not require credential)

Y (requires credentials)

Execute a test case

Y

Y (can execute only Approved executions)

Y (can execute only Approved executions)

Y (requires credentials and can execute only Approved executions)

Import Test Executions

Y

Y (can execute only Approved executions)

Y (can execute only Approved executions)

Y (*requires credentials and can execute only Approved executions)

*pop-up appears only when the status in file differs from

Bulk Execute test cases against multiple releases, cycles and platforms

Y

Y (can execute only Approved executions)

Y (can execute only Approved executions)

Y (requires credentials and can execute only Approved executions)

Bulk Execute test cases for a single platform, release and cycle

Y

Y (can execute only Approved executions)

Y (can execute only Approved executions)

Y (requires credentials and can execute only Approved executions)

Sync latest version of test case on Execution Screen

Y

Y (can sync only Approved executions)

Y (can sync only Approved executions)

Y (requires credentials and can sync only Approved executions)

Assigning/resetting a Build

Y

Y (can assign Build to only Approved executions)

Y (can assign Build to only Approved executions)

Y (requires credentials and can assign Build to only Approved executions)

Note

  • Enabling Part 11 Compliance blocks uploading automation result files through the Automation API for that project.

  • Enable Part 11 Compliance to allow or LDAP and SAML users can authenticate.

  • Authentication via inactive or deleted account is restricted.

  • Time is recorded as per the user profile.

API

Method Type

Request

Response

/rest/admin/compliance/authenticate

POST

{"username":"admin","password":"Ispl123#"}

{"success":true,"userId":1}

/rest/admin/project/getinfo

GET

NO

Added “isPartLevelComplianceEnabled“ flag

/rest/admin/project

PUT

Added “isPartLevelComplianceEnabled“ flag

Added “isPartLevelComplianceEnabled“ flag

/rest/execution/matrix/updatestatus

POST

Added “changedBy“ parameter

NO

/rest/execution/runstatus/bulkupdate

PUT

Added “changedBy“ parameter

NO

In this section:
© 2025
Publication date: