- Getting started
- Project management
- Documents
- 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
- Manual test cases
- Importing manual test cases
- Document test cases with Task Capture
- Parameters
- Enabling governance at project level
- Disabling governance at project level
- Enabling governance at test-case level
- Disabling governance at test-case level
- Managing approvers for governed test cases
- Managing governed test cases in the In Work state
- Managing governeed test cases in the In Review state
- Managing governed objects in the Signed state
- Managing comments for governed test cases
- Applying filters and views
- Importing Orchestrator test sets
- Creating test sets
- Adding test cases to a test set
- Assigning default users in test set execution
- Enabling activity coverage
- Enabling Healing Agent
- Configuring test sets for specific execution folders and robots
- Overriding parameters
- Cloning test sets
- Exporting test sets
- Applying filters and views
- Accessibility testing for Test Cloud
- Searching with Autopilot
- Project operations and utilities
- Test Manager settings
- ALM tool integration
- API integration
- Coding Agents for Testing
- Troubleshooting
OAuth-based web service connection between a Test Manager project and your SAP system for periodic data collection.
To create an integration between your Test Manager project and your SAP system to collect data periodically, using a web service OAuth connection to your SAP system, follow the steps below. You can create one or several connections and then select the one of interest when working with your Heatmap.
1. Prerequisites
- Use one of the following Studio versions, so that you do not run into any compatibility issues: Studio Connected (where you have access to the latest version), Studio 2025.10.5 or Studio 2024.10.19.
- If you plan to use Change Impact Analysis, install the UiPath SAP Add-on on the target SAP system. Installing the Add-on's Heatmap package creates the SAP Internet Communication Framework (SICF) node (
/sap/opu/odata/UIPATH/) that Change Impact Analysis depends on.
If the SICF node isn't visible after import, confirm the Heatmap package installed correctly using report ICFTREE_CONSISTENCY (see SAP Note 3235642 for dangling ICFAPPLCUST entries).
If you run into connectivity issues while setting up OAuth, it can help to first validate the connection using SAP Web Service (Basic Auth) and then switch the connection to OAuth once basic connectivity is confirmed.
2. Create the SAP connection
Configure an OAuth-based web service SAP connection in your Test Manager project to enable periodic data collection from your SAP system for Heatmap analysis.
- Open your project in Test Manager, and go to Project Settings > Integration.
- From the New Connection dropdown list, select SAP.
- In the Edit connection dialog, fill in the fields according to the data from your SAP system:
- Name: Name the integration between Test Manager and SAP.
- Description: Describe the integration between Test Manager and SAP.
- From Heatmap Data Source select SAP Web Service (OAuth 2.0):
- Application Server: URL that your SAP system is working on.
For example, a URL can have the following format: https://mysapserver.com:443.
- Identity URL: URL from which the OAuth token is fetched.
- Client ID: OAuth client identifier registered for this integration.
- Client Secret: OAuth client secret associated with the Client ID.
- Polling interval: Time interval when data is brought from the SAP system. The default value is 24 hours. The minimum value is one hour.
If your organization requires SAP traffic to pass through an API gateway (for example, Apigee) rather than connecting to SAP directly, point Application Server and Identity URL at the gateway endpoints, and coordinate with your Basis/network team to ensure the gateway proxies requests to the correct backend SAP service.
3. Configure Change Impact Analysis
After you set up the web service OAuth connection, choose how to enable Change Impact Analysis, and define which SAP system it connects to.
-
Open your existent SAP connection, or select SAP from the New Connection dropdown list.
-
Select Change Impact Analysis connection.
-
Under Impact Analysis Access select the view tabs corresponding to SAP change types that you want to display in your Change Impact Analysis:
- UI: Selected by default, displays transactions impacted by the selected transports.
- API: Displays the technical interfaces impacted by the selected transports, such as SAP BAPI, SAP RFC, SAP QUERY, and SAP IDOC.
- Security: Displays security transactions and corresponding users impacted by the selected transports.
-
Under Connection Source select one of the following:
-
Same as Heatmap: Keep the same SAP connection details that you are using for the Heatmap. This means both functionalities will collect data from the same SAP system.
-
New connection: Create a separate SAP connection for Change Impact Analysis. This option allows you to use different authentication details while maintaining the same connection type as the Heatmap.
Note:We recommend you to connect the Heatmap to your production system and Change Impact Analysis to your quality system for optimal risk evaluation.
Follow the same steps as above, for creating an SAP web service connection.
-
Result
The OAuth web service connection to your SAP system is created and the Heatmap page becomes available in your Test Manager project. SAP data is collected at the configured polling interval.
If your Heatmap connection uses a CSV file, you must create a new connection for Change Impact Analysis. Follow the same steps for creating either an RFC or web service connection.