- Getting started
- Project management
- Working with Change Impact Analysis
- Create test cases
- Assigning test cases to requirements
- Cloning test cases
- Exporting test cases
- Linking test cases in Studio to Test Manager
- Delete test cases
- Enabling governance at project level
- Disabling governance at project level
- Enabling governance at test-case level
- Disabling governance at test-case level
- Enabling or disabling governance in bulk for test cases
- Enforcing signing order for governed test cases
- Managing approvers for governed test cases
- Managing governed test cases in the In Work state
- Managing governed test cases in the In Review state
- Managing governed objects in the Signed state
- Managing comments for governed test cases
- Viewing governance information for test case logs
- Managing approvers for governed test case logs
- Managing governed test case logs in the In Work state
- Managing governed test case logs in the In Review state
- Managing governed test case logs in the Signed state
- Managing comments for governed test case logs
- Enabling governance at test case log level
- Disabling governance at test case log level
- Viewing and searching test cases
- Project operations and utilities
- Test Manager settings
- Tenant level settings
- General project settings
- Events
- Subscribing to events
- Subscribing to all events
- Unsubscribing from events
- Unsubscribing from all events
- Unsubscribing from the Notifications settings page
- Viewing notifications
- Filtering notifications
- Viewing email notifications
- Enabling email notifications for SMTP servers
- Viewing only unread notifications
- Marking all notifications as read
- Clearing all notifications
- Deleting notifications
- Customer managed keys encryption
- Audit logs
- ALM tool integration
- ALM tool integration
- Test Manager Connect
- Test Manager - Integration Service connector
- Outbound IP ranges for connectors
- Working with SAP Cloud ALM and Test Manager
- Step 1: Integrating SAP Cloud ALM with Test Manager
- Step 2: Creating automated test cases in SAP Cloud ALM
- Step 3: Creating automated test cases in Test Manager
- Step 4: Synchronizing test cases from Test Manager to SAP Cloud ALM
- Step 5: Assigning test automations to test cases
- Step 6: Executing test cases
- SAP test automation best practices
- Troubleshooting the Jira integration
- API integration
- Coding Agents for Testing
- Troubleshooting
About PII masking
PII masking in Test Manager Autopilot, protecting personally identifiable information before it reaches any LLM during Autopilot activities.
The PII (personally identifiable information) used in Autopilot activities can be automatically masked before reaching any LLM, ensuring compliance with data protection regulations and data privacy.
What is PII?
PII covers data such as names, emails, phone numbers, or social security numbers, originating from production data or customer reports.
How is PII masking used in Autopilot?
PII masking is a privacy shield within the AI Trust Layer which pseudonymizes sensitive entities in transit and which prevents accidental data exposure when using LLMs. PII masking is supported in Test Manager, ensuring that no PII leaves the test environment.
PII masking can be used to mask all Autopilot capabilities which involve user input.
Restriction: PII masking applies only to content included in the requirement description and does not extend to attachments provided within Autopilot activities.
How do I enable PII masking?
To mask sensitive information when using Autopilot in Test Manager, you must enable PII masking in AI Trust Layer.
The masked PII is displayed as in the example below:
Figure 18. PII masking example