Forum Discussion
trk
7 years agoNew Contributor
Thanks Lucian for the quick feedback. Really appreciate it.
I understand your suggestion and it should probably work, will give it a try. But still it is not what I was expecting from the tool.
Going in a bit more details this is how my test case is today:
- REST call #1 (where random number is created)
- Property transfer (where random number is retrieved and where a parameter from REST response from step 1 is also retrieved)
- REST call #2 (where random number is used together with parameter from REST response)
So it would all fit under these 3 steps.
With the addition of groovy script, then it would be 4 steps instead.
- Groovy script to create random number
- REST call #1 (where random number is used as a parameter)
- Property transfer (where a parameter from REST response from step 1 is retrieved)
- REST call #2 (where random number parameter is used together with parameter from REST response)
Would be good to know if there is a way around using just the 3 steps and if this can be considered as a bug in the tool (as this works fine using SOAP requests). Otherwise, would go with your suggestion with the 4 steps.
Thanks once again.
- Lucian7 years agoCommunity HeroCan you post a dummy request/ response/ screenshot etc? I am working quite a lot with properties and I am not aware of this bug (there was a bug involving dynamic Json paths recently but I don't think this is causing this)
Related Content
- 10 months ago
- 5 years ago
- 6 years ago
- 2 years ago
- 9 years ago
Recent Discussions
- 15 years ago