SR-B46599 · Issue 304003
ListenerPage made available to the service API
Resolved in Pega Version 7.3
In order to enable using the service mail activity to fetch information from the Email Listener, "pyListenerPage" has been made available in the API so the service activity can find it.
SR-B46802 · Issue 304072
Null check added for missing propInfo in WSDL
Resolved in Pega Version 7.3
A null-pointer exception was occurring in cases where the propInfo generated from SOAP WSDL was null. This has been fixed with the addition of a null check.
SR-B46832 · Issue 302938
Logic added to convert UTC Date for REST clipboard mapping
Resolved in Pega Version 7.3
An error was generated while mapping UTC format Date fields to the clipboard in REST. This was traced to the DateTime properties in the JSON response not being converted to Pega-supported datetime format, and the necessary parsing logic has been added.
SR-B4703 · Issue 276811
Browse Messages accepts custom properties for authentication
Resolved in Pega Version 7.3
Browse Messages was throwing a username null error due to custom properties provided in the JNDI server rule form not being read. Support has now been added to read custom properties for browse messages.
SR-B47342 · Issue 303997
Fixed page reference error when copying
Resolved in Pega Version 7.3
An error stating reference pyWorkPage.ProductLines were not valid was generated during deferredSave while copying embedded reference type auto populate properties. This was caused by operations that added references from the data page before the current auto populate's reference information was added to duplicator. To resolve this, if the copy target is auto populate the system will skip adding references, and if the target is any other page the references will be copied.
SR-B4749 · Issue 285795
Fixed Guardrail warnings not clearing on Justification
Resolved in Pega Version 7.3
Guardrail warnings that appeared on the Map Structured rule Justification Dropdown were not clearing until the mapping was deleted and readded with proper justification. This was an error related to the value default for property pyJustification not being defined in the prompt list, and has been fixed by adding blank as a valid value for pyJustification property with prompt label "Default", and setting the pyJustification in pyDefault model for the row to be empty string instead of "Default".
SR-B47650 · Issue 301985
Dynamically populated values localized
Resolved in Pega Version 7.3
Dynamically populated values were not getting translated in Data Migration Wizard. In order to improve localization, Property Value has bene modified to use a Localized property value for pyLabel in general settings.
SR-B47650 · Issue 303884
Dynamically populated values localized
Resolved in Pega Version 7.3
Dynamically populated values were not getting translated in Data Migration Wizard. In order to improve localization, Property Value has bene modified to use a Localized property value for pyLabel in general settings.
SR-B4768 · Issue 276160
Global DB Trace timestamp uses UTC
Resolved in Pega Version 7.3
When running Global DB trace, recorded timestamps were not following the 'set timestamp' setting. Timestamps instead corresponded to the requestor context. DB Tracer logging has been updated to ensure appended timestamps are passed as "UTC".
SR-B4772 · Issue 285014
GetXML read-only conflict resolved
Resolved in Pega Version 7.3
When executing the "run" button on the rule form to test a read-only data page sourced by a Rule-Parse-XML, a read-only violation in getXML() resulted when attempting to expand the XML of the page for presentation to the user. This was traced to an unnecessary override IF block in prGetObject() related to overriding context class, and it has been removed.