INC-220532 · Issue 739700
Property reference retrieves correct values
Resolved in Pega Version 8.8
When a pageGroup was mapped to a pageList through a page and the checkbox "Allow use as reference property in activities" was enabled, the property reference retrieved old clipboard page values and displayed data from prior work objects opened in the browser section. This has been resolved with an update which will then replace that pageList in clientDataProvider with whatever is received from the server.
INC-141595 · Issue 602713
CSRF and Browser fingerprint tokens added for testing custom scripts
Resolved in Pega Version 8.5.2
After upgrade, the test window appeared blank when attempting to test Decision Table rules. This was traced to there not being CSRF token and Browser fingerprint handling in the custom script used to show a prompt screen to the user. Because the CSRF token validation was missing, the request failed. To resolve this, CSRF and Browser fingerprint tokens have been added as hidden fields.
INC-211589 · Issue 710335
App-alias URL shown correctly on app definition rule after switch
Resolved in Pega Version 8.8
When using Cosmos React as the default app, switching from the react-based application to a non-react application resulted in a blank app-name in the application definition URL. Investigation showed the UI was not refreshing correctly on updating values in the app alias pop-up window, and this has been resolved by calling close work before harness unloads if no pending calls are present.
INC-217680 · Issue 717605
Tab name displayed correctly in embedded mashup portal
Resolved in Pega Version 8.8
"Work Item" was given as as the tab header instead of the Case ID## when:a case link was clicked/opened in an application embedded in an external site (IAC). This was traced to the pega.desktop.support.doGadgetAction function not calling the regular handleGadgetLoad function in this scenario, and has been resolved by explicitly directing work items opened in a multi-doc mashup portal to use handleGadgetLoad.
SR-D94002 · Issue 553766
Export to Excel cell style control added
Resolved in Pega Version 8.2.7
If a column was formatted with an auto generated numeric control, a new cell style was generated for every row during the export to Excel process. Since there is a limit on the amount of cell styles, once the number of rows in the file was greater than 64000 an error was generated. To resolve this, the system will disable the creation of a new cell style for every instance when an auto-generated numeric control is used.
INC-206109 · Issue 706236
Delayed Learning works correctly with Volume Constraints
Resolved in Pega Version 8.8
When running an outbound campaign using NBA Designers predictions and delayed learning in conjunction with volume constraints, the adaptive models ended up with incorrect feedback if the prediction had an Alternative label configured with a defined waiting window. This has been resolved with the addition of a new flag 'isVolumeConstraintEnabled' during dataflow creation which will check for volume constraint, and a filter in HandleResponses for that flag.
INC-139810 · Issue 592834
New Rule-Utility-Function added to allow customizing filename formatting in repository
Resolved in Pega Version 8.5.2
When using S3 as file storage, uploading a file with a name such as "sample.tar.gz" resulted in the file name in the repository being formatted as "sample.tar_.gz" instead of the expected "sample_.tar.gz". This was caused by the handling in pzSaveToRepository, which was meant to include the CaseID for the customer use case of same-name attachments on every instance of a case. In order to handle attachments with multiple file extensions such as "<FILE_NAME>.tar.gz", the logic for the fileName formatting has been moved from pzSaveToRepository to the new Rule-Utility-Function pyFormatAttachmentName so that is is possible to override and customize the behavior.
INC-143320 · Issue 602279
Support added for email addresses with hyphen in domain name
Resolved in Pega Version 8.5.2
When attempting to enter a email with a hyphen '-' in the domain part of an email ID ([email protected]), the reply button was getting disabled. This was caused by the regex validation implemented in the "pzValidateEmailAddress" (Work-Channel-Triage-Email) standard activity not covering all the possible cases. To resolve this, regex has been changed to instead use a platform-provided rule to ValidateEmailAddress.
INC-211977 · Issue 713460
Handling added for large BIX Postgres data sets
Resolved in Pega Version 8.8
BIX extracts were causing timeouts or JVM out of memory errors. This was traced to the Postgres JDBC driver ignoring fetch size in auto-commit transaction mode, which led to everything being loaded into memory at once. To resolve this, changes have been added to support fetch size for large results when using PostgreSQL database for BIX Extraction.
INC-220166 · Issue 724348
Declaratives processing temporarily disabled for DX API request
Resolved in Pega Version 8.8
After update, trying to navigate from one assignment to another assignment by using the DX API post assignment request displayed a date format error due to rule changes that caused the declare trigger to be called at the time of getting the response. This caused validation to fail. To resolve this, an update has been made to temporarily disable declaratives processing when processing DX API request content.