Pub.client:http send String to post in the body instead of URL

[mm4wm (mm mm)]

Thanks a lot. That helps. I am new to webMethods and still learning. But really appreciate all your suggestions and guidance!

[Holger_von_Thomsen]

Or you can invoke the pub.flow:clearPipeline service where you specify the variables to be preserved in the output.

See IS Built-In-Services Reference fro details.

Regards,
Holger

[reamon]

Not a bad suggestion. Here’s a different point of view for consideration: avoid using pub.flow:clearPipeline. Instead, always explicitly drop vars as soon as they are no longer needed.

Here are some thoughts on this from posts many moons ago that may be informative:

Use of ClearPipeline in the flow services

Hello There, Is it a best practice to use Clear Pipeline in main flow service and also some of util services where we have a bulk of code? Did anyone saw any issues using clearPipeline service. Many Thanks, Veera.

CustomWare Local Variable Holder coding style

Are there any standards or best practices to be following while developing Flow services? We have already completed our dev. But we have lots of variables that are in the pipe line. We also have some of the variables not dropped after they are used up. Will that affect the performance? We still didn’t go live into production. What are the problems that we face when we go live into production? Is there any document that we can read to get the above details?

The pipeline is passed between services?!?

Hi, I’m new to webMethods so please forgive if I ask questions with obvious answers… I have been developing before using C, C++ and more recently Java and C#. The flow language presents something new: the pipeline. 1st thing I discovered is that the pipeline will just accumulate all the existing variables unless there are “dropped”. Fine, this shows what variables exist and actually it forces you to clean them as soon as you don’t need them, otherwise it’s a mess - let’s say this is …

(The last one refers to a notion of the pipeline being “copied over from services to services” but it is not – the pipeline is a global variable pool for the thread and all services run in that thread have access to the pipeline – with exceptions for services invoked as transformers or within a scope.)

Edit: A couple of the threads referenced above mention “best practices” – there is no such thing. Just practices that some find useful for their environment. You may find they work for you as well.

[John_Carter4 (John Carter)]

Personally I don’t like clearPipeline, smacks of lazy programming
John.