Combining VSI's is adding transaction to the Specific Transaction instead of creating a new Stateless Transaction

Products

• Service Virtualization

Issue/Introduction

When combining VSI's which has same Operation names but different signatures, seen the transactions are added to Specific Transactions instead of adding it to Stateless Transactions.

Steps to reproduce:

1. Create a Main.vsi with the below Stateless Transactions:

[88] PersonDetails -> META transaction has Match Style Signature

Name:

Phone:

 

[244] PersonDetails-->META transaction has Match Style Signature

Name:

Phone:

AlternatePhone:

 

[262] PersonDetails-->META transaction has Match Style Operation

Name:

Phone:

Address:

 

 

The Main.vsi should looks like below. Transaction Ids could be different.

 

2. Then create another New.vsi with the below Stateless Transaction.

PersonDetails-->META transaction has Match Style Operation

Name:

Phone:

Address:

State:

Country:

 

 

Then Combine the New.vsi into Main.vsi, the new Stateless Transaction is added to the Main.vsi as a Specific Transaction instead of a new Stateless Transaction. See the below screenshot of Main.vsi after the combine.

 

 

Environment

All supported DevTest releases

Cause

The [262] Stateless Transaction -->META Transaction has Operation as Match Style which caused the issue.

 

Resolution

Here are the steps to resolve:

. In Main.vsi, change the [262] Stateless Transaction -->META Transaction--> Match Style from Operation to Signature.

. Delete the added [156]Specific Transaction from the Main.vsi and save it..

. Close the Main.vsi and New.vsi files.

. Retry combining New.vsi into Main.vsi.

. Open the Main.vsi and should see the new transaction in the Stateless Transactions list as in below screenshot.

 

 

Additional Information

Refer to section "Combine Service Images" in DevTest documentation for the version you are running.