Question

Service SOAP - RULE PARSE XML stream request doesn't set all the properties that is coming from external system

Parse-XML does not map XML request data to ClipboardPage

1. We have a soap-service rule which is being called by external app

2. We are setting the properties in RULE PARSE XML stream request rule

3. External App is sending all the parameters as part of their request

4. But we see some properties are not being set on the page

5. Screen shots attached.

Performed the below steps:

  1. Perform 'revalidate and save' of these properties and it saves successfully.
  2. Performed 'revalidate and save' of the Parse-XML rule and it works this time
  3. Execute Service-SOAP and still could not find the property
  4. Since it couldn't find the property we see this error in tracer "Goal seek requires missing input property JurisChangeClaimStatus.dsClaimStatusRequest.ClaimStatusRequest.ClaimSubStatus"

Please share if any one faced similar issues faced. Version Pega 7.1.8

Incoming Request:

--------------------------

<?xml version="1.0" encoding="UTF-8"?>

<ns0:ChangeClaimStatus xmlns:ns0="urn:PegaRULES:SOAP:JurisChangeClaimStatus:JURIS">

  <dsClaimStatusRequest>

    <ClaimStatusRequest>

<ClaimUID>4872822.904</ClaimUID>

<ClientId>1970</ClientId>

<FileNum>151217000000002</FileNum>

<ProcUnit>670</ProcUnit>

<VendorId>PEG</VendorId>

<UserID>SYSTEM</UserID>

<ClaimStatus>O</ClaimStatus>

<ClaimSubstatus>A</ClaimSubstatus>

<ClaimTier>FeatherTouch</ClaimTier>

      <DenialType> </DenialType>

<Appealed>no</Appealed>

      <Overturned>no</Overturned>

<Reopened>no</Reopened>

<ReasonCode></ReasonCode>

    </ClaimStatusRequest>

  </dsClaimStatusRequest>

  </ns0:ChangeClaimStatus>

**Moderation Team has archived post**

This post has been archived for educational purposes. Contents and links will no longer be updated. If you have the same/similar question, please write a new post.

Comments

Keep up to date on this post and subscribe to comments

December 18, 2015 - 12:39pm

Hi Raja,

Can you please use DSS Pega-IntegrationEngine / SwitchToOldAssembler= true , restart server and then check if mapping is correct?

December 18, 2015 - 2:29pm
Response to ARVINDMALAV

Tried this option, but couldn't resolve the issue. We found the issue is the case sensitivity from incoming request vs pega parse xml which resolved the issue.

Pega
December 21, 2015 - 5:41am
Response to RajaSekharC

Please share the stacktrace when issue occurred.