SR-D15089 · Issue 485330
Handling added for single quotes in custom DateTime controls when using Export to Excel
Resolved in Pega Version 8.3
A previously resolved issue with the timezone not being appended to datetime when exporting to Excel if a custom control was used has been further updated to better handle single-quote strings in custom DateTime controls.
SR-D13160 · Issue 485449
Hotfix installer updated to adhere to installorder file included in the package
Resolved in Pega Version 8.3
In order to ensure hotfixes are always installed in the proper order, the installer has been updated to iterate over a set that is ordered according to the INSTALLORDER.PEGA file included in the DL file at packaging time.
SR-D11911 · Issue 485465
Mobile JS performance improved
Resolved in Pega Version 8.3
Some out-of-the-box javascript bundles contained un-compacted scripts, creating a performance issue issue on mobile. This has been corrected.
SR-D16221 · Issue 485527
Email replies fixed for cases addressed to CC or BCC address
Resolved in Pega Version 8.3
Using Customer Service, if a Customer included 3 email accounts in single email (one email in To, one in CC, and one in BCC) and all three accounts had the listener configured and running, the system created 3 cases accordingly (I-1, I-2 and I-3). However, when the CSR picked up the case and replied back on each Interaction case, the customer could receive emails only from the first case (the I-1 case which was created based on To address) and replies from the other cases created from the CC and BCC email addresses were not received. Investigation showed that the function populating the “From” email address for replies was only considering email addresses in the “To” recipient list of the original email and not the email addresses which were in the “CC” or “BCC” list. This has been corrected.
SR-D11605 · Issue 485662
:JAWS correctly reads heading for Report browser/viewer
Resolved in Pega Version 8.3
JAWS 18 was not reading the titles in the report browser and report viewer as "heading level 1" as it should. For the Report Browser, JAWS was reading the title as "<title> - heading level 2", and for the Report Viewer, JAWS read the report title as "<title> - frame". This has been corrected by adding the appropriate aria tags to pzGetStyledLocalizedText.
SR-C97046 · Issue 485716
Added restriction to limit environment sending multiple OTP emails
Resolved in Pega Version 8.3
Multiple One Time Password (OTP) Emails were being sent for a single requestor on a change password screen when the password was expired. This was caused by the environmental settings refreshing the changepassword harness, and has been resolved by adding a restriction against sending multiple OTPs for a requestor to whom an OTP has been successfully sent once.
SR-D16970 · Issue 485762
New API introduced to handle DSM service startup fail or delay
Resolved in Pega Version 8.3
A Stream node was shown with JOINING_FAILED status in the landing page, but executing a JMX call to get the status on the landing page resulted in a message that it was not a registered bean. This was caused by JMX being registered before service initialization and allowing for decommissioning a node other than itself. Investigation showed that this feature was developed prior to its use for cloud monitoring, and subsequent development led to the same feature being used via LP. In order to prevent conflicts, a new REST API has been introduced to allow cloud monitoring to manage nodes in which DSM services failed to startup or are still in the process of getting to "NORMAL" state.
SR-D16074 · Issue 485881
Additional language options added to Language Wizard dropdown
Resolved in Pega Version 8.3
An enhancement has been added to the “select a language” dropdown in the Language Wizard that extends the available options to include Latin American Spanish (es_XL), Brazilian Portuguese (pt_BR), and Korean (ko_KR).
SR-D14591 · Issue 485930
Check added to resolve intermittent console errors
Resolved in Pega Version 8.3
An intermittent issue where an autocomplete control was hanging after repeated use has been addressed by adding an additional check (dispElem && dispElem.parentNode) to avoid console errors.
SR-D14573 · Issue 485986
Wait corrected for sub case after reopening
Resolved in Pega Version 8.3
A re-opened parent case was not waiting for the sub case when a sub case was reopened, but it did wait if there was no sub case on the reopened parent case. This has been resolved by enhancing the system to better handle the reopen of activator and dependent work objects by checking the reopen time: - pzGetAllStatusforDepClass activity: added step 2 to consider activator reopen time - pzGetMessageKeysForFlowDependencies list view: added criteria to filter on reopen time