Are you using a "Call Rule" action, or are you are graphically wrapping a "reusable rule" for the set of processing actions?
That is, when I think of a "reusable rule", I typically build the rule in the processing policy and then use the "Call Rule" action in the various places I need it. With all that said, you can actually "reuse" that rule in other policies for other service objects as well. Because of that, if it is truly a "reusable rule", I develop it on an unused proxy's processing policy, and then just use it as needed.
However, when graphically creating a "reusable rule", behind the scenes, it is somewhat doing the same thing. But, I'm not sure how the PIPE works under that case, I'd have to build an example to see.
------------------------------
Joseph Morgan
CEO - Independent
------------------------------
Original Message:
Sent: Tue August 19, 2025 06:59 PM
From: Sudarshan Bandaru
Subject: To capture last pipe data in a processing rule
Hi,
Our organization is introducing a new API Security tool called Traceable. As part of this requirement, we need to send both the request and response payloads to this tool from DataPower.
What we plan to do is, create a reusable rule which will take care of sending payload logs to Traceable and call this reusable rule from request and response rules after Results action.
In some of the proxies, transformations have been used to modify the response payload and it was saved to PIPE context and same was used in Results action.
When we try to call the reusable rule after results action with same PIPE context, it is erroring because the output context of Results action is not PIPE. So, we would like to know if there is a way to capture this PIPE context?
We can try changing the PIPE context of previous processing actions to some dp_var context, apply it to Results actions and use same when calling the reusable rule.
But I am wondering if there is way to achieve this without modifying the existing processing action's contexts?
------------------------------
Sudarshan Bandaru
------------------------------