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-A91979 · Issue 261380
referencePropertyLink will be directly copied if autopopulate disabled
Resolved in Pega Version 7.3
A run-time failure occurred due to a reference to an AP property failing to copy properly during objOpenByHandle. This was because autopopulation is disabled in objOpenByHandle, causing the source property to be returned as null when page-copy lost the reference information. To resolve this, when autopopulation is disabled the referencePropertyLink will be directly copied from the source page to the target page without trying to resolve the reference property's source.
SR-A92512 · Issue 270130
WebLogic tool generation updated for complexType schema
Resolved in Pega Version 7.3
A red X error was seen for PRAsync MDB modules on the Resource Dependencies screen in the WebLogic console in deployments with WebLogic 11i or 12c. This was due to the EJB component (prbeans.jar) not being implemented to support complexType schema, and has been resolved by updating the Pega Platform WebLogic components to support complexType schema in the WebLogic tool generation.
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-A95151 · Issue 268672
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-A95291 · Issue 272970
Role Ruleform documentation updated to reflect new privilege behavior
Resolved in Pega Version 7.3
The documentation for the role ruleform has been updated to reflect that decision tables are not given the OpenDeveloperForm privilege necessary to edit the ruleform when "add to favorites" is used instead of "delegate". If an attempt is made to open a "Favorite" decision table delegated rule from the portal's My Rules screen, a blank-looking screen will be displayed instead of the rule form.