Is there a way to toggle between match style as operation and signature in Devtest portal as in case of Workstation?

[Legacy User]

Usually we can change the match style as "Operation" and "signature" in Devtest Workstation.Can that be done in portal as well?

[kadne01]

Hi,

 

The change of match style from "Operation" to "Signature" and vice versa can be done from VSI of a VS. As we can open the VSI in the workstation, there is an option to do from there. Since thats not the case in Portal, you can make this change by opening the VSI in any test editor like Notepad/Notepad++ etc and change the match style of any transaction. 

 

Here is a sample of a transaction whose match style I changed from Signature to Operation

 

Changed line 

 

<rq id="16" op="deleteUser" tl="SIGNATURE">

 

To 

 

<rq id="16" op="deleteUser" tl="OPERATION">

 

Where I have changed the Match Style of deleteUser operation from Signature to Operation. 

 

Regards

Neelima K

[Legacy User]

Hi Neelima,

 

I have followed the procedure suggested by you to edit /modify the match tolerance level in Dev test portal. I have downloaded the .mar file from VSE and converted it to .zip file by changing the extension of .mar file and after that i have extracted the contents and modified the match tolerance level from SIGNATURE to OPERATION in .vsi file , saved it and again converted the .zip to .mar file by changing the extension but when i am trying to reupload the mar file to portal i am getting the below error :

 

Error : Error 500 - Our audit file is either missing or we are not a model archive or are corrupt. 

 

Could you please correct me if i am following the wrong procedure to change the match tolerance and suggest me the viable method.

[Premalatha Gadde]

The way you are creating the mar file after making changes is not the right way. You need to create mar file from the Workstation again using the correct VSM or deploy the VSM again.

 

If you need more help, please open a support case.

[Durga Prasanna Kumar Bellana]

You need to create Mar Info File by right click on the VSM file. After creating the .mari file then you need to create .mar file then you will not get any this kind of errors