SR-C97399 · Issue 439743
Button type added to allow grid expand in Edge
Resolved in Pega Version 8.1.6
When using an expand pane grid in a modal with the Edge browser, clicking on the expand icon using the enter key was throwing an error in new window. This was traced to an issue with a hidden non-auto-generated button in the pzModalHelp control not having a default type, and has been resolved by adding type="button" in the control so Edge will treat it as a submit button.
SR-D12530 · Issue 482722
Spinner wheel dom correctly cleared after incomplete case closure
Resolved in Pega Version 8.1.6
Incorrect behavior of the spinner wheel during a case search following the browser being closed while a case was open has been resolved by updating pzpega_ui_doc_actionRouter to ensure the wheel dom is correctly cleared.
SR-D18960 · Issue 499911
Logic updated to resolve busy indicator delay
Resolved in Pega Version 8.1.6
On click of submit in the main interaction flow, the busy indicator was not getting displayed or was displayed after a delay whenever there were a series of Ajax requests being made. The logic has been updated to resolve this issue.
SR-D23700 · Issue 497920
Repaired setValue(Boolean) clipboard mapping
Resolved in Pega Version 8.1.6
A Set Value for an Hidden Control associated property was not mapped to clipboard as expected. This was an unintended side-effect of work done to resolve an alert generated while attempting to post a feed even though there was no Pulse gadget used in the work object, and was due to the read-only option being considered for hidden input in spite of no design time configuration. A hidden field check has been added so that by default it will be readonly false irrespective of editable and non-editable.
SR-D9119 · Issue 481679
Handlng improved for rollback of Hfix with dependent HFixes
Resolved in Pega Version 8.1.6
Attempting to rollback an HFix with dependent HFixes resulted in a Hazelcast jar exception. Investigation showed the DL included the same jar multiple times in the dependent hotfixes, which was a result of how the DL was created via the hotfix process. In order to better handle this scenario, when there are multiples of the same entries to delete the message will be logged and the process will continue if the entry is not found in the database.
SR-D17660 · Issue 486702
Resolved OOM error for system scan
Resolved in Pega Version 8.1.6
In some installations, performing a system scan would cause an Out Of Memory Error. This was traced to the process used to de-serialize the catalog metadata, which caused the unzipped version of the catalog (containing data going back to v6 releases) to grow to 125 MB. To resolve this issue the system will make use of streams, but as that still requires the entire catalog object to be available, the system will also cull redundant objects from the hotfix catalog. Going forward, platform-specific catalog files will be created to minimize their size and improve efficiency.
SR-D10171 · Issue 482471
Updated UtilsEmailListener to handle additional special characters in the email ID
Resolved in Pega Version 8.1.6
When the Email Listener tried to map the properties from the email body and message header to the Pega Default out-of-the-box properties or user provided text properties, the mapping worked for simple alphanumeric email IDs, but mapped only the trailing part of the address if the Email ID contained an apostrophe or single quotes. For example, "toast.'[email protected]" was mapped as "[email protected]". This was due to a missed special character in the regex pattern, and UtilsEmailListener.java has been updated to correctly handle special characters in the email address as specified in RFC 5322.
SR-D16221 · Issue 485533
Email replies fixed for cases addressed to CC or BCC address
Resolved in Pega Version 8.1.6
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-D17577 · Issue 486863
Enhancement added to allow skipping Text Analysis on incoming email
Resolved in Pega Version 8.1.6
When an inbound email channel was configured for automatic routing only, PEGA0039 alerts were generated even if the Text Analysis feature was not being used. To resolve this, an enhancement has been added by way of the 'when' rule pySkipTextAnalysis which can be overriden and set to true. When this condition evaluates to true, text analysis will be skipped for Email IVA. By default the when rule evaluates to false. This rule must be saved in application ruleset and should return true if analysis is to be skipped. In addition, the timing of the Obj-Save has been moved so if the text analysis is skipped, the system will not prepare the unneeded interaction input.
SR-C95857 · Issue 483548
JSON parsing added for identifier data type
Resolved in Pega Version 8.1.6
After upgrade, Service-REST was no longer mapping data as expected when the property was of type "identifier". Handling has now been added for mapping where property type is identifier and the incoming type is any valid value for identifier.