Skip to main content

This content has been archived and is no longer being updated. Links may not function; however, this content may be relevant to outdated versions of the product.

Support Article

Date type XML is not parsing correctly

SA-29256

Summary



The issue has occurred after upgrading from Pega 7.1.7 to Pega 7.2. User has a web service which returns an array of data that also include a date field. The data is saved in a property which is of Date type. The format of the date is given below:

<paymentDate>2015-02-11-04:00</paymentDate>

The above XML parses correctly in Pega 7.1.7 but in Pega 7.2 it is not parsed. After debugging the service it was found that Pega is not mapping the values to date field whereas in Pega 7.1.7 it worked correctly. Creating a new property which is of type Date/Time didn't resolve the issue.


Error Messages


Not Applicable


Steps to Reproduce

  1. Create a service that returns an array of data including a date field. The date value is of the below format:
    <paymentDate>2015-02-11-04:00</paymentDate> 
  2. Use a Parse XML rule to parse the response. The date field property defined in PEGA should be of date type.
  3. Use the value parsed into the date type field to map it to another date type property. The XML is parsed correctly in Pega 7.1.7 where-as it is not parsed in Pega 7.2.


Root Cause



A defect in Pegasystems’ code or rules is identified as root cause of the issue.

Resolution



Follow the below steps:
  1. Apply HFix-29759.
  2. Set the below dynamic system settings entry:

    Purpose : SwitchToOldAssembler
    Owning Ruleset : Pega-IntegrationEngine
    Value : true
Suggest Edit

Published October 20, 2016 - Updated October 8, 2020

Did you find this content helpful? Yes No

100% found this useful

Have a question? Get answers now.

Visit the Collaboration Center to ask questions, engage in discussions, share ideas, and help others.

We'd prefer it if you saw us at our best.

Pega Community has detected you are using a browser which may prevent you from experiencing the site as intended. To improve your experience, please update your browser.

Close Deprecation Notice
Contact us