Can we rename the VSI operations to help to identify the scenarios for each transaction?

Products

• CA Application Test
• CA Continuous Application Insight (PathFinder)
• Service Virtualization

Issue/Introduction

Is there a way we can rename the VSI operations to help identify the scenarios for each transaction?

Environment

All supported DevTest releases.

Cause

N/A

Resolution

It is possible to rename the operations for each transaction, but we will have matching issues during playback.

The name of the transactions is created based on the operation it is captured.
An example, for the operation POST /humanresources/v2/collaborator/get/SEN0001ERRO, if SEN0001ERRO is part of the request, the operation in the request file needs to be something like the: POST /humanresources/v2/collaborator/get/SEN0001ERRO HTTP/1.1

We can also use pieces of the request as arguments or the operation name by using the request data manager data protocol. 

Refer to section "Request Data Manager Data Protocol" in the documentation of the DevTest release you are running.

The Action Copy can be used to copy a piece of data in the request to another part of the request.

This DPH is available only with the Workstation, not in the Portal.

Additional Information

Refer to section "Match Tolerance" in the documentation of the DevTest release you are running.