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-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-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.
SR-B5172 · Issue 275097
SOAP handling for BOM bites fixed
Resolved in Pega Version 7.3
After upgrade, an exception was generated when hitting the PRSOAPServlet. This was due to an error in encoding BOM bytes, and has been fixed.
SR-B5417 · Issue 274794
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-B5820 · Issue 276037
Properties of type Integer text value properly formatted
Resolved in Pega Version 7.3
Properties of type Integer text value were not properly formatted when set to property. This has been fixed by modifying the assembler code to pass the property type and use it properly for runtime mapping.
SR-B6165 · Issue 278927
Trend Reporting list view error resolved
Resolved in Pega Version 7.3
After running a Summary View with Trend Reporting, the following error appeared in the logs: NumberFormatException For input string: " ". This was caused by the data transform for the trend reporting list view initializing a null value for pyCeilingField as " " instead of "", and has been fixed.
SR-B6244 · Issue 277565
Documentation and log messages updated for BIX/useHistoryClasses
Resolved in Pega Version 7.3
When using command-line BIX 7.1 to extract records and write them to a secondary database, messages from the system gave the impression that some of the records were skipped. This was due to a mismatch in the number of records reported at different points in the extraction: as the records got updated while the extract was running, those particular updated records got skipped as they did not fall into the time range that user was passing. To avoid this confusion, the text in the logs has been clarified to read: "Processing Class class name with XXXX instances (processing count may vary as records get modified before BIX extraction)." In addition, the documentation regarding the usage of the BIX/useHistoryClasses option has been updated to reflect this information.