Service SOAP Inbound data mapping not working correctly with both CDATA and Attachments in Request
We are facing an unique issue in Service SOAP Inbound Data mapping. We have exposed this Service from PEGA and testing it using SOAP UI.
When we have CDATA as part of Request XML and we map this as an LiteralXML to a Property, we are observing that CDATA tag is not being removed and it is part of the LiteralXML.
Example:
SOAP Request: <Message><![CDATA[ <InsideCDATA><RequestElements></RequestElements></InsideCDATA> ]]></Message>
PropertyValue: <Message><![CDATA[ <InsideCDATA><RequestElements></RequestElements></InsideCDATA> ]]></Message>
However when we have attachments and CDATA present in SOAP Request, we are observing the Property value is without CDATA tag.
Example:
SOAP Request: <Message><![CDATA[ <InsideCDATA><RequestElements></RequestElements></InsideCDATA> ]]></Message>
PropertyValue: <Message><InsideCDATA><RequestElements></RequestElements></InsideCDATA></Message>
This difference in xml value is throwing errors in ParseXML rule.
Getting the following error :
We are facing an unique issue in Service SOAP Inbound Data mapping. We have exposed this Service from PEGA and testing it using SOAP UI.
When we have CDATA as part of Request XML and we map this as an LiteralXML to a Property, we are observing that CDATA tag is not being removed and it is part of the LiteralXML.
Example:
SOAP Request: <Message><![CDATA[ <InsideCDATA><RequestElements></RequestElements></InsideCDATA> ]]></Message>
PropertyValue: <Message><![CDATA[ <InsideCDATA><RequestElements></RequestElements></InsideCDATA> ]]></Message>
However when we have attachments and CDATA present in SOAP Request, we are observing the Property value is without CDATA tag.
Example:
SOAP Request: <Message><![CDATA[ <InsideCDATA><RequestElements></RequestElements></InsideCDATA> ]]></Message>
PropertyValue: <Message><InsideCDATA><RequestElements></RequestElements></InsideCDATA></Message>
This difference in xml value is throwing errors in ParseXML rule.
Getting the following error :
Has anyone encountered this problem? This is happening only when we have attachments and CDATA and with CDATA alone it is working fine.
What is the correct way to handle CDATA with Attachments in SOAP Request?
Any help in this regard will be highly appreciated.
Note : We are using PRPC v7.1.8
Accepted Solution
Pegasystems Inc.
US
Upon reviewing the corresponding SR, we see that it has been resolved. SA-19915 was created as a result of the investigation. Please reference that if you have the same question.
Cognizant
US
Hi Prasad
We have seen similar kind of issue. We passed the request like this.
Param.Request: Contains the elements which are inside the CDATA.
In service activity we can do a property set before calling the request data transform and set it to a param like
Param.FullRequest = "<Message><![CDATA["+Param.Request+" ]]></Message>"
Now pass Param.FullRequest this to the requst data transform.
Can you give a try.
Thank you
Sam
Updated: 6 Jan 2016 5:51 EST
UnitedHealth Group
IN
Hi Samanth,
I tried this and it did not help. Still getting the same error.
We have raised an SR at the moment and awaiting further update from PEGA.
Regards,
Prasad
Virtusa IT Consulting
AE
Hi Prasad,
I have created SR-A16632.
Alekhya Gumudavelli can you please help with the below query?
What is the correct way to handle CDATA with Attachments in SOAP Request?
Thanks,
Habeeb Baig
Accepted Solution
Pegasystems Inc.
US
Upon reviewing the corresponding SR, we see that it has been resolved. SA-19915 was created as a result of the investigation. Please reference that if you have the same question.