AnsweredAssumed Answered

VSI transaction Basepath and URLParam problems

Question asked by sdetweil2 on Feb 16, 2017
Latest reply on Feb 17, 2017 by sdetweil2

version  9.1, we recorded a set of REST/JSON transactions, which contain an account number in the URL,

we added the rest and json DPH's at the end of record, and the correct VSI transactions were created.

 

then we use postman to test the service (running in ITR), and the original account number URL works,

any other account number and we get a 404 error on return..

 

in the Error case, the ITR never moves off the listen step. 

 

we noticed the VSI transaction Basepath field contains the full URL with the ORIGINAL account number in it.

anything else will be wrong. 

 

if we shorten the basepath to just before the account number, then the service works. 

what is wrong here? the vsi transaction parameters are correct, including URLPARM0,

and its url string is /foo/bar/{URLPARM0}/test as expected. 

 

changing the VSI transaction parm to magic string or comparison operator to 'anything' don't help. 

Outcomes