SR-A98319 · Issue 266117
All key value data supported for field mapping
Resolved in Pega Version 7.2.2
If a data type was configured with local storage where all the columns are keys, the validation error "Must specify a target for at least one source field that isn't a record identifier" occurred when attempting to import data. Previously, pzValidateUpdateFieldMappings expected at least one non-key field in data type configuration and did not consider the condition of having all fields be keys of the data type defined. To support this configuration, the function has been updated to find the count of properties which are keys and which are not and use a 'when' rule pass for the above scenario.
SR-A92755 · Issue 261497
Fixed links display with privilege option in repeating grids
Resolved in Pega Version 7.2.2
When making use of the privilege option in the link control configuration as a condition to enable/disable the links in the repeat grid, the links were disabled/hidden even when the operator had the correct privilege. Analysis showed this happened in cases where the primary page was different from the page context on which the current part of the section was rendering (for example, when a grid or repeating dynamic layout is present), and it has been fixed by passing the current step page to the pega_rules_default.ValidatePrivileges function instead of passing the primary page.
SR-B69409 · Issue 317548
CLOB type handling enhanced in Marketing
Resolved in Pega Version 7.3.1
Pega Marketing uses the out-of-the-box DSM activity pxRunDDFWithProgressPage for triggering Data flow runtime. After upgrade in DB2 environments, the DF execution completed but the activity returned a failure. It was found that if a CLOB column is present in the filter of a NativeSQL object invoked from an activity, the status had an error message even though functionality was fine. To ensure consistent behavior, CLOB has been added to supported data types so the severity of the exception can be changed so as to not show error message in activity's status.
INC-152108 · Issue 622372
Logic updated for exporting customized multi-column report definition
Resolved in Pega Version 8.5.3
While attempting to perform an export to Excel for the results of a report definition which had two custom functions for two columns, the error "PRRuntimeException: Section 'pzRDExportWrapper' execution error on page '' of class 'Rule-Obj-Report-Definition'. : The Reference .pyTextValue(2) is not valid. " was logged. The export worked if either one of the columns was removed or if "Display values across columns" in the column settings was unchecked. This has been resolved by updating the logic in PivotTableDataGridGenerator for rowheaders to handle using DisplayValuesacrossColumns with FunctionAliases when not checked on in sequence.
SR-C39690 · Issue 381877
New RUF added for deleting data type from CSV during import
Resolved in Pega Version 8.1
After upgrade, attempting to use the import CSV functionality to delete caused the wizard to hang and log the error 'PRRuntimeException: Can't continue with file upload. Can't read File'. This was caused by the system using the pxHasSingleKey RUF in pzDeleteRecords to check whether or not the class has a single key, which does not work for this use case. In order to support this method, a new RUF(pxHasSingleKeyAndExposed) has been created which will check the class for single key and also will check whether it is exposed or not. This will result in executeSQLForBatchDelete API being skipped and pzCreatePagesAndImportInBatch will get called instead.
SR-C33657 · Issue 401228
Connector and Metadata wizard skip of renaming classes works for very large metadata in Chrome
Resolved in Pega Version 8.2
When using the Connector & Metadata wizard to generate Data mapping rules for Java Bean metadata with an imported jar containing a large number of metadata (over 5000 classes and properties), clicking on the option to skip renaming of classes and properties caused the browser to hang. This was traced to legacy code which was not efficient enough to handle this volume, and modifications have been made to avoid unnecessarily overloading the DOM and triggering onclick addEventListener events multiple times. This reworked skip function works smoothly with Chrome, but as yet does not work with the IE browser due to legacy coding and browser incompatibility issues.
SR-C58201 · Issue 399199
Hazelcast thread locking improved
Resolved in Pega Version 8.2
The system was hanging after attempting Hazelcast locking. Tracing showed threads that seemed to be waiting for the system lock to become available so that they could acquire a database lock. This was caused by an implementation issue in LockUtils that did not wait to ensure that the distributed map's lock was released if it wasn't yet available. To correct this, debug logging has been added to the "LockUtils" class which will print when the lock is acquired or released along with the associated stacktrace. In addition, a wait function has been added to the Distributed Map lock to improve the timing between release and grab.
SR-D23239 · Issue 499591
Support added for multi-operator SAML logins
Resolved in Pega Version 8.4
When a SAML user logged in by Single Sign-On (SAML), the system processed the login to portal as a different operator if there was a function on the Attribute field under Operator identification in the SAML authentication service. In this scenario, using an expression for operator provisioning did not work because all SAML login sessions resolved to same first operator due to parseAndEvaluateExpression() in ExpressionHelper.java ignoring new expression arguments if the expression page already existed. To support the use of multiple operator logins in this format, the system has been updated to clone a new expression page for every session and update it with the correct expression arguments.
SR-D24187 · Issue 506128
Catch block added to handle invalid FindAndUpdateElement clipboard data
Resolved in Pega Version 8.4
An exception was generated relating to "Unable to passivate page on thread '<savedwork>' . The following items were not serializable: [Property not serializable: "Declare_pyDisplay.pyDisplay(InteractionPortal).pyUIElements(3).pyParameters.activityParamPage" Class: "com.pega.pegarules.pub.runtime.ParameterPage." This was traced to invalid data in the clipboard, and has been resolved with the addition of a catch block in pzFindAndUpdateElement Rule-Utility-Function which will put an empty string in the clipboard whenever there is an invalid value in the 'Declare_pyDisplay.pyDisplay().pyUIElements().pyParameters' clipboard page.
SR-D7323 · Issue 493178
Pin Case to Board updated to use unique IDs for different workpools
Resolved in Pega Version 8.4
When using the Pin Case to Board functionality, it was only possible to find and pin cases in the default/current work pool of the working access group and not any other cases in any other work pools which allowed access to open/search/process. This was due to pyLabel being used to compare if a value entered was valid, which was not a unique key. To resolve this, the pyValidatePinDetails activity in Pega-Ext-Mentions-Documents, Pega-Ext-Mentions-Cases, and Pega-Ext-Mentions-Groups classes have been updated to compare pzInsKey instead of pyLabel to check for validate pin.