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-B47060 · Issue 303231
Fixed BulkActions filter reset
Resolved in Pega Version 7.3
In the Bulk Actions page, adding a new filter property caused the other conditions to be reset incorrectly. To resolve this, checks have been added to see if there is already a filter condition configured in the Embed-FCondition.pzDefaultOperators.
SR-B47227 · Issue 304654
Requirements template sets Excel input cells as text for security
Resolved in Pega Version 7.3
For increased security in Pega Platform Excel files, the Requirements template has been changed to set all the input cell types as text instead of general.
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-B47384 · Issue 303522
Fixed focus reset for page number click in grid layout
Resolved in Pega Version 7.3
An anchor element generated for the active page in a repeat grid had "#" as href but did not have an onclick handler defined, causing a click of the Page number in a Grid layout to move focus to the top of the page. This has been corrected with the addition of an onclick handler in pzGridActivePage custom control for inactiveLink in 123 pagination.
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.