INC-218265 · Issue 720613
DoClose updated to resolve lock and context issues
Resolved in Pega Version 8.6.5
An interaction case was closing when intent tasks were closed from CSRecents. Investigation showed this was due to the doClose activity not being triggered in the right context, and has been resolved. An additional issue with locks not being correctly released after opening the new case Create stage and clicking Cancel in the modal was traced to a missing pyWorkPage in the safeURL params that was needed by the doClose activity, and this has been resolved by adding the primary page name.
SR-121115 · Issue 183812
Added optional setting for handling blank localization settings
Resolved in Pega Version 7.1.8
Previously, a blank localization value was carried forward as a blank value. This behavior was changed in Pega7 to have the localization API Executable#getLocalizedText return the Label itself. In order to maximize usability going forward, an API has been added that allows either behavior based on local settings. This is accessible as PublicAPI.java getLocalizedTextForString (String aRef, String aString,boolean aReturnEmptyForLocalisedString) To use the API to carry the empty value, pass "true" to aReturnEmptyForLocalisedString parameter. The API will then return the localized string in the field value as-is i.e it will return an empty string if the localized string is empty.
SR-121115 · Issue 182793
Added optional setting for handling blank localization settings
Resolved in Pega Version 7.1.8
Previously, a blank localization value was carried forward as a blank value. This behavior was changed in Pega7 to have the localization API Executable#getLocalizedText return the Label itself. In order to maximize usability going forward, an API has been added that allows either behavior based on local settings. This is accessible as PublicAPI.java getLocalizedTextForString (String aRef, String aString,boolean aReturnEmptyForLocalisedString) To use the API to carry the empty value, pass "true" to aReturnEmptyForLocalisedString parameter. The API will then return the localized string in the field value as-is i.e it will return an empty string if the localized string is empty.
SR-123750 · Issue 189489
Smoothed multiple portal tabs handling
Resolved in Pega Version 7.1.8
After opening the Case Manager developer portal, if a user portal was opened in a second tab using the 'Switch Portal' option shown in operator menu, returning to the developer portal tab caused that tab to be refreshed and the user portal tab to close. Previously, attempting to open a second portal session in a tab of the same window resulted in a 'Multiple sessions running' error. This limitation was removed in Pega 7.x. However, in this case the 'ShowDesktop' activity could not determine the 'ThreadName' parameter and defaulted to the 'Standard' thread and this change caused the refresh. The logic for determining the thread name has been updated to remove this issue.
SR-123127 · Issue 185219
Improve error handling for File Listener
Resolved in Pega Version 7.1.8
The File Listener not processing all files successfully when there was more than one file to be processed. This was caused by missing logic for the clearing of 'hasOnce' at the file level for the record type. Since 'hasonce' was not cleared at file level, once a file with an incorrect configuration is processed, others files were also getting processed as errors. This has been resolved by adding code to reset the 'hasonce' on a per file basis so File Listener is able to process multiple files.
INC-146572 · Issue 603294
iniGadgets updated to support jQuery with Mashup
Resolved in Pega Version 8.5.2
Mashup gadgets were not loaded during browser refresh when the host page had a jQuery in it. This issue occurred while trying to find the gadget divs. There is an 'if' condition to check if $ is available in initGadgets method. In this scenario, this 'if' block was getting executed and mashup gadget divs were returned as empty. As a result. mashup was not getting loaded. This has been resolved by updating the iniGadgets method to check for jQuery instead of $.
INC-213918 · Issue 714454
Discard button works consistently
Resolved in Pega Version 8.6.5
After check out, the discard button was not working consistently for decision tables or MapValue. Investigation showed this occurred when an exported file was being downloaded in the same window, as the thread would be busy with the file and not able to perform the discard action on the window. To resolve this, the configuration for the download on the same window has been removed, exportToDecisionTable has been modified to handle an iframe, and a runScript action has been added to register the exportToExcel activity and download in iframe.
INC-145425 · Issue 600773
New email template added to include full message history
Resolved in Pega Version 8.5.2
Whenever a reply was sent from the email triage case, the outbound email sent only the actual reply along with the original email and latest reply only, skipping all remaining replies from email. For example, if there were 5 replies from case, replying 5th time generated an outbound email that contained only 5th reply (actual / current), original reply (which created the service case) and the latest reply (reply 4 in this case) and skipped reply 1 and reply 2. To resolve this, a new Outlook-style template has been added for use in replies that will include all of the previous exchanges.
SR-119103 · Issue 178373
Missing hyphen auto-added to base class by import wizard
Resolved in Pega Version 7.1.8
When running the Connector & Metadata wizard to import the XSD file, entering the base class name without a dash created classes and properties all concatenated with the class name. However entering a dash at the end of the base class name created properties separated with the dash from the class names. This was an error in the wizard - it is no longer mandatory to end the abstract class with a dash, and the code has been updated to correctly append the hyphen at the end of baseclass if one doesn't exist.
SR-120195 · Issue 180041
Smoothed adding rows to a repeat grid after canceling previous action
Resolved in Pega Version 7.1.8
When adding an item to the Repeat Grid, a small modal is opened to allow value entry to associate with that row. However, canceling the modal and then clicking on the button to add a row failed to open the modal a second time and it was not possible to add another row to the Repeat Grid. This was caused by the previous canceled modal call remaining active resulting in the new event being skipped. To correct this, the modal dialog incall property will be reset so it may be properly opened as expected following a previous cancelation.