> But TN seems insistent on returning extra metadata, such as
> flags, rule, etc.
Tons of junk may exist in a service at runtime. Undropped variables may be present from earlier processing rule executions. WM TN isn’t very disciplined itself either - it passes extra variables to the service called by the processing rule (even though the service signature only contains the 3 records described in “wm.tn.rec:ProcessingService”.)
The solution: call pub.flow:clearPipeline at the beginning and maybe at the end of your service. You have to set the ‘preserve’ array to the names of the variables you want to ‘preserve’ from being wiped from the pipeline.
#Integration-Server-and-ESB#B2B-Integration#webMethods