we are implementing the Webservice, we are not trying to call an existing one, so I assume you mean Rule-Service-HTTP instead? That's the workaraound we are probably going for, although I'm not very happy with it.
We have tried yor Code-Snippet, but there is no 'pxHTTPServletRequest' property or object on the pxRequestor page when the service activity is executed.
Yes John. I meant service-http. Apologies for the typo.
Let me check if I can find any more workaround. As per my knowledge, user id and password can be tracked in the header, so it might be possible to get any other parameter, although I am not sure about this. You can raise a Pega SR to check if there is any other way.
This feature is not available in PRPC currently (at least till Pega 7.1.7), you need to customize 'invokeaxis2' activity. You might refer to the link below for more information on how this may be achieved.
we are implementing the webservice. The parameters in the http header are sent to us and we need to find a way to read them in the Pega Service Activity. From what I understand in the link you provided, it shows how to add custom http header paramaters when calling another webservice.
help on the rule form says that the "Request Headers" section on the Request tab of the rule form is for reading the content of the Soap-Envelopereads the content.
Complete the Request Headers section to map data from the SOAP envelope header.
That won't give us Access to the parameters passed in the http header.
<!-- and so on -->
<!-- Here our request data -->
We'd be able to read the HeaderParam 1 and 2 (from the Soap-Envelope Header), but not from the protocol-Level http header.
The SR I have submitted has changed it's type from "How-To Question" to "Enhancement Request".
I'll post updates to this as answers to my original question.