SR-B6425 · Issue 270890
Scrum Board chicklet error resolved
Resolved in Pega Version 7.2.2
After collapsing and expanding a user story chicklet in the Scrum Board, adding a new note to the user story would cause the user story chicklet to disappear. This was a rendering issue due to an error in the type property syncing with the level property, and has been fixed.
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.
SR-A101500 · Issue 278178
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.
SR-A101675 · Issue 270578
Size to Content refresh updated
Resolved in Pega Version 7.3
A expandable grid with a text area and button as columns in it was not correctly calculating the size after refreshing. An explicit call to the resizeHarnessActual has been added to ensure expected behavior.
SR-A103192 · Issue 271775
ReadOnly radiobutton display fixed for null value
Resolved in Pega Version 7.3
When a radiobutton control was set ReadOnly, "--" was not displaying as expected when the property did not contain any value. Instead, the radio button values were displayed as empty. This was caused by a missing span tag element for read only mode, and has been fixed.
SR-A87830 · Issue 258083
PD4ML JAR updated
Resolved in Pega Version 7.3
Metadata dates in a PDF generated with PD4ML are expected to follow ISO 8601 format "YYYY-MM-DDThh:mm:ss+##:##", with "+##:##" being the time zone adjustment based on UTC, but when the time zone was given as UTC (or a time zone with zero adjustment), PD4ML was setting the date as "YYYY-MM-DDThh:mm:ssZ00:00". This consequently generated errors with various PDF/A tools. To resolve this, the PD4ml jar has been updated.
SR-A87830 · Issue 258092
PD4ML JAR updated
Resolved in Pega Version 7.3
Metadata dates in a PDF generated with PD4ML are expected to follow ISO 8601 format "YYYY-MM-DDThh:mm:ss+##:##", with "+##:##" being the time zone adjustment based on UTC, but when the time zone was given as UTC (or a time zone with zero adjustment), PD4ML was setting the date as "YYYY-MM-DDThh:mm:ssZ00:00". This consequently generated errors with various PDF/A tools. To resolve this, the PD4ml jar has been updated.
SR-A87830 · Issue 259106
PD4ML JAR updated
Resolved in Pega Version 7.3
Metadata dates in a PDF generated with PD4ML are expected to follow ISO 8601 format "YYYY-MM-DDThh:mm:ss+##:##", with "+##:##" being the time zone adjustment based on UTC, but when the time zone was given as UTC (or a time zone with zero adjustment), PD4ML was setting the date as "YYYY-MM-DDThh:mm:ssZ00:00". This consequently generated errors with various PDF/A tools. To resolve this, the PD4ml jar has been updated.