Question

6
Replies
1203
Views
Prasad_BY Member since 2014 12 posts
UnitedHealth Group
Posted: 4 years ago
Last activity: 4 years 7 months ago
Closed
Solved

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 :

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

Pega Customer Service Data Integration
Moderation Team has archived post
Share this page LinkedIn