SR-B385 · Issue 270797
ASCII characters properly displayed in dynamic layout headers
Resolved in Pega Version 7.3
When using a field value that contains special characters like + and = to display the header value of a dynamic layout the characters were being converted to their encoded ASCII characters on screen (ex [&] instead of [&]). This was traced to the Field Value text being encoded twice, and the GridHeaderElements function has been updated to correct this.
SR-A100118 · Issue 287256
Auto-populate updated for better page copy references
Resolved in Pega Version 7.3
After upgrade, an error was generated at a page-remove step on the Group information screen while running the quoting process. This happened in cases where a copy was made of a page containing an auto populate property and the data page referred by the AP had Common Parent references, and was traced to the parent page of the reference property having been removed from the common parent page. To resolve this, the auto-populate function has been updated to better maintain references in copies.
SR-A100292 · Issue 270065
Select Values from join properly displayed on chart
Resolved in Pega Version 7.3
In charts of report definitions using a join, properties with prompt select values were displaying the actual data rather than the prompt values. This was due to a handling difference for properties from joins: before rendering the chart, report data was copied to a page that did not have the correct pxObjClass, creating the assumption that the property applied to @baseclass. To resolve this, the class will be set on the page that contains the target property.
SR-A100558 · Issue 271513
Oversized file null-pointer exception resolved
Resolved in Pega Version 7.3
A 413 exception was being generated by uploading files with a size greater than the Initialization/MaxFileUploadSize DSS value. The controls have been modified with a check to restrict properly restrict file size during this process.
SR-A100558 · Issue 274795
Oversized file null-pointer exception resolved
Resolved in Pega Version 7.3
A 413 exception was being generated by uploading files with a size greater than the Initialization/MaxFileUploadSize DSS value. The controls have been modified with a check to restrict properly restrict file size during this process.
SR-A100717 · Issue 275645
Certificate validation handling updated to work with single-entry CN or DN
Resolved in Pega Version 7.3
Previously, the Gateway connectivity test assumed valid certificates would contain more than one CN entry. This caused an invalid certificate error on the host landing page of prgateway gateway test if the certificate in use had only CN entry. To address this, code has been added to handle cases where a certificate has only a single entry of either CN or DN.
SR-A100717 · Issue 277670
Certificate validation handling updated to work with single-entry CN or DN
Resolved in Pega Version 7.3
Previously, the Gateway connectivity test assumed valid certificates would contain more than one CN entry. This caused an invalid certificate error on the host landing page of prgateway gateway test if the certificate in use had only CN entry. To address this, code has been added to handle cases where a certificate has only a single entry of either CN or DN.
SR-A100782 · Issue 272266
Siteminder block resolved for DPParams containing double quotes
Resolved in Pega Version 7.3
Due to the DPParams being transmitted in JSON format, using the Siteminder CSSChecking parameter set to yes with BadCSSChars containing "%22" caused the " (double quotes) that surround the name value pairs to trigger a Siteminder block. To resolve this, the system will pass the DPParams in the post body instead of sending it in the query string.
SR-A101144 · Issue 272239
Error message clear after bad row deleted
Resolved in Pega Version 7.3
Error messages were not clearing even after deleting the row which caused the error. This has been corrected.
SR-A101500 · Issue 279633
Menubar Object memory leak repaired
Resolved in Pega Version 7.3
A memory leak has been resolved by eliminating unnecessary DesktopMouseClick events when creating a new old-Menubar object.