SR-D898 · Issue 435996
Pega0069 alert accuracy resolved for UHC FinishAssignment
Resolved in Pega Version 8.3
Pega0069 alerts were not raised for the CS commit and confirm harnesses, and the reported total duration was not always accurate. This has been resolved by capturing document busy/idle for CS harnesses.
SR-C90418 · Issue 436016
Exception handling improved for pxAdjustSLA, pxAdjustSLATimes, and pzAdjustSLATimesInBulk functions
Resolved in Pega Version 8.3
If the SLA Deadline days were updated from 0 to 1, the SLA agent did not trigger the deadline escalation activity and the error "com.pega.pegarules.pub.context.PRQueueException: Instance of class Queue not found: SYSTEM-QUEUE-SERVICELEVEL.SYSTEM-QUEUE-SERVICELEVEL" was generated. This has been resolved with the addition of better failure handling to the pxAdjustSLA, pxAdjustSLATimes, and pzAdjustSLATimesInBulk functions for cases where an exception is generated.
SR-C97656 · Issue 436039
DSS added to allow custom timeout for BIX query
Resolved in Pega Version 8.3
The BIX query to retrieve the blob column was taking up to 60 seconds for large volume, causing timeouts. Previously, the extract defaulted to using repost pzSample which is internal/final and has a default timeout of 30 seconds. In order to avoid timeouts, the new DSS "BIX/selectQueryTimeout" has been added to allow setting a custom value.
SR-C93802 · Issue 436136
Rounding added to avoid exception for ADM number too small to save to Oracle
Resolved in Pega Version 8.3
An exception was thrown when trying to save ADMSnapshot agent predictor bin data that was too small (below 1 x 10-130) for the Oracle Number column it was written into. This blocked up-to-date reporting on adaptive models. To resolve this issue, the code has been modified to round the double type numbers to an acceptable scale before writing to the database.
SR-C96547 · Issue 436157
Check added to format simplified Chinese date generation to match system expectations
Resolved in Pega Version 8.3
"When the browser language was set to Chinese (simplified) and a template was used for an application, an invalid date exception was generated. This was caused by a difference in handling between the moment.js function used to format the datetime, and Pega. The moment javascript formats dates with the below 6 meridiem for Chinese locales (zh-cn, zh-hk, zh-tw):凌晨 - Early morning 早上 - morning 上午 - morning (AM) 中午 - noon 下午 - in the afternoon (PM) 晚上 - at night But the Pega server only accepts two standard meridiem i.e. 上午 - morning (AM) and 下午 - in the afternoon (PM). Due to this, using an unsupported setting resulted in an error. To resolve this, a check has been added for the Chinese locales (zh-cn, zh-hk, zh-tw) that will adjust the non-supported formats to be either 上午 - morning (AM) or 下午 - in the afternoon (PM). Additional support has also been added to handle this function for iPad.
SR-C86589 · Issue 436265
Added explicit thread cleanup to resolve case worker portal UI rendering problem
Resolved in Pega Version 8.3
Creating a case in the case worker portal was resulting in the respective screen being rendered with a distorted UI. This was traced to an issue in topnavigation where the thread was being changed to a base thread and skipping the FlowModalProcess thread removal when the new DC action was triggered. To resolve this, the system has been modified to append "$FlowModalProcess" in harnessOnBeforeUnload if it is missing to make sure the FlowModalProcess thread is removed.
SR-C90457 · Issue 436282
Handling added for deleting a temp file when pyTranslationFileName is blank
Resolved in Pega Version 8.3
The Localization wizard was generating a file delete error when attempting to delete a temporary folder. To resolve this, an "if" condition has been added to PegaAccel-Task-Localize.pzResetExportDetails to handle file deletion scenarios where the pyTranslationFileName is blank.
SR-C94914 · Issue 436300
Cursor position retained after password field refresh
Resolved in Pega Version 8.3
If a section was created which contained a Password control with an "Any Key" event that included "Post value" and "Refresh-Other section" actions, the cursor always stayed at the beginning of the line. This has been resolved by adding code to ensure the caret position is retained after a refresh for the password field.
SR-C96456 · Issue 436306
Autocomplete grid scroll bar fixed for large DataPage results
Resolved in Pega Version 8.3
When autocomplete (default setting) was present inside a grid and the result popup had < 20 results, the scrollbar was not coming up in Google Chrome. This has been resolved by modifying the fixGridWidthIfRequired API to set set vertical scroll to auto.
SR-C96001 · Issue 436367
Independent query logic inserted for non-resolved rules to avoid non-applicable columns
Resolved in Pega Version 8.3
Nothing was displayed under "Revalidate and save" for Rule-Ruleset-Name and Rule-Ruleset-Version. In Tracer there was an error message saying that "There was a problem getting a list: code: 207 SQLState: S0001 Message: Invalid column name 'pyRuleAvailable'. " Investigation showed that because the system was using the same logic for resolved and non-resolved rules, Rule-Ruleset-Name and Rule-Ruleset-Version were looking for the column pyRuleAvailable which was not applicable because non-resolved rules don't have this column. To resolve this issue, a separate query executor has been added for non-resolved rules as there are a few columns related to resolved rules that are not applicable for those that are not resolved.