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.
SR-A87830 · Issue 261150
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-A91779 · Issue 266553
Removed repeating keyword from validation error
Resolved in Pega Version 7.3
Each validation error was causing the word "error:" to be prepended every time the autocomplete results were opened. This has been corrected with the addition of a check in the displayErrors API for harness_accessibility js.
SR-A93749 · Issue 269857
BusyIndicator will show in mobile i-device browser during attachment upload
Resolved in Pega Version 7.3
While uploading using 'attach content' in the Safari browser on an iPad or iPhone, no busy indicator (throbber) was shown. This made it possible to interact with other controls including selecting "finish assignment" before the upload was completed, causing an abnormal completion of the case. To prevent unexpected behavior, the busyIndicator will be displayed in mobile browsers while the attach content process is in progress.
SR-A94098 · Issue 263125
Smart Info Tooltip and Modal window work in combination
Resolved in Pega Version 7.3
The combination of using Smart Info Tooltip for different field elements in combination with the Modal Window for some action on the same screen was resulting in the Smart Tip floating over the modal dialog, and the cancel button did not work. This was due to a conflict in the element handling, and the code has been modified to resolve this and support this use.
SR-A98230 · Issue 271051
Revision management GET logic revised
Resolved in Pega Version 7.3
When the revision manager creates a new revision, the second step is to add rules (strategies/data transforms etc.) into that revision so that a strategy designer can work on that. However, it was found that if one of the HTTP requests was of GET method, selecting the rules and hitting 'submit' constructed an oversized URL which listed all the rules listed on the Revision page and the browser would hang due to the GET exceeding the character limit. To avoid this, the logic used to create the post body has been modified to creating avoid long parameter values.
SR-A99678 · Issue 272068
Chart clipboard page unloaded properly in tab refresh
Resolved in Pega Version 7.3
When a portal tab containing a chart was refreshed due to use of the "refresh when active" tabbed layout checkmark, the old chart clipboard pages remained. This was due to a missed use case, and has been fixed.
SR-B10018 · Issue 280365
Null pointer resolved for change events
Resolved in Pega Version 7.3
On a section where a grid had at least one column cell with the visibility condition configured to be run on client, each data change event on other controls inside the same section raised a JavaScript error which disabled all of the following actions configured to be executed on the change event. These script errors were due to the improper usage of the findCell API call, resulting in the second parameter always being sent as null. To correct this, the getElementRowPageRef of pega_ui_doc_eventsConditionChaining.js has been updated to pass the grid parent table properly for findCell to avoid a null pointer.