Contributions
Cleaning up properties after every VirtAction
I find myself writing context.setProperty() statements on my dispatch scripts, so I can dynamically customize my responses. However I noticed that the lifetime of dispatch script context.properties goes well beyond the lifetime of a VirtAction call. How would I go about cleaning up after every VirtAction call? Or is there a more appropriate context I can use to store and manipulate properties with the scope of a VirtAction?5 years agoPlace ReadyAPI QuestionsReadyAPI Questions787Views0likes1CommentHow to Handle dynamic QUERY Style key-value parameters in my request url?
Hello all, When setting up a VirtAction with a path variable, I can use that variable from within the response. For instance, a VirtAction api/v1/clients/{client_id} will create a variable named client_id which I can now use in the response. How can I do the same name with query (non path) parameters? Is there a way ServiceV Pro can store these query parameters into variables that I can use in the response message?Solved5 years agoPlace ReadyAPI QuestionsReadyAPI Questions1.4KViews0likes1Comment