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

UTC format fields not converting to GMT format for REST



A REST service returns a datetime value in a JSON message using UTC format (for example, 2017-06-12T18:16:00.324Z).

While HFix-29779 prevents an exception from getting thrown, the datetime format still remains in UTC format and does nott get converted to Pega supported GMT format.

It is expected that Pega would parse the datetime value to it's internal format so that it can be used to display datetime values or used in data transforms.

Error Messages

InvalidDateTimeValue 2017-06-12T18:16:00.324Z

Steps to Reproduce

1. Use SOAPUI to simulate the Rest JSON response - {"createdate":"2017-06-12T18:16:00.324Z"}.
2. Use Rest integration wizard to generate Data page and connect-rest Rule.
3. Change the Int- createdate property type from Text to DateTime.
4. Run Data page and Trace the execution.

Root Cause

A defect in Pegasystems’ code or rules


Perform the following local-change steps:
  1. Apply Hfix-35264.
  2. Restart JVM for the code change to take effect.
Suggest Edit

Published August 20, 2017 - Updated October 8, 2020

Did you find this content helpful? Yes No

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