SR-C80372 · Issue 425075
Oniine help files updated to more completely reflect SAML Authentication Rule Form fields
Resolved in Pega Version 8.2.1
The online help files have been updated to reflect that the SAML Authentication Rule form has various fields including Entity Identification, Login Location, Logout protocol binding, and Artifact Resolution Service Location that support GRS syntax (=D_myDataPage). When configuring SAML it is also required to update WebSSO Service Package to point to the Access Group as the Application Access Group. https://community.pega.com/sites/default/files/help_v74/procomhelpmain.htm#concepts/concepts2/globalresourcesettingfields.htm
SR-C68134 · Issue 423617
Support added for configuring key stores using prconfig or system properties
Resolved in Pega Version 8.2.1
Previously, stream service only supported key store and trust store configuration using Data-Admin-Keystore instances. Unlike cluster encryption, it did not allow the configuration of key stores using prconfig or system properties. In order to align Stream service SSL configuration with the rest of the platform, support has now been added for the following system and prconfig properties:-Dpega.cluster.keyStore -Dpega.cluster.keyStorePassword -Dpega.cluster.trustStore -Dpega.cluster.trustStorePassword
SR-C80129 · Issue 421416
Data type search adjusted to handle text query
Resolved in Pega Version 8.2.1
After creating a data type and adding a class join and then delegating the data type to a user, the data type search bar in the configuration tab was not working. This was traced to the decision search filter using "=", which did not handle a text query. This has now been changed to use "Contains" to resolve this issue.
SR-C74784 · Issue 428818
Added file truncation to HCClient.txt to ensure data integrity
Resolved in Pega Version 8.2.1
When a work object model contained more than two embedded lists, simple save corrupted the JSON in the local storage work object browser. Investigation traced the issue to using the same file without truncating its content. Because the HCClient.txt file in Rule: webwb - pzpega_mobile_settings - js was reused while displaying items in DocumentViewer, writing a smaller amount of data into it than the previous write left orphaned content in the file that corrupted the new data. To resolve this, the file content will be truncated before writing new data into it.
SR-C76417 · Issue 430546
Check added for reference function in DB2 join
Resolved in Pega Version 8.2.1
In DB2, when a sub-report column contained a function that was used for a join condition in the main report, an invalid filter property error was generated while saving. This was traced to the edit validate rule checking for the data type of both of the properties used in the join, and has been resolved by adding a check to see if the join operand is of function 'reference'; if so, the system will resolve the function, check for data type property, and set it.
SR-C64192 · Issue 421338
Activity Run allows autocomplete control for data transform
Resolved in Pega Version 8.2.1
An enhancement has been added to allow changing the control from Dropdown to Autocomplete when an activity is Run and the "apply data transform" checkbox is checked.
SR-C71221 · Issue 427921
Radio buttons maintain arttributes after dynamic layout table reordering
Resolved in Pega Version 8.2.1
When using a table configured in a popup where each row of the table was rendered using a dynamic layout that included radio buttons within it, the radio button fields were being cleared when the rows of the table were reordered. This was caused by the radio buttons not having unique name values, and has been resolved by using the updatehandles function in the pega_ui_repeatlayout js file to set the checked attribute based on the selected value after the reorder.
INC-203994 · Issue 698853
DSS added to handle merges with lower versions of Postgres
Resolved in Pega Version 8.7.1
After update, executing the batch campaign with volume constraint resulted in the second data flow DF_Wait failing with error message "ERROR: number of columns (1844) exceeds limit (1664)". This was due to the database set’s change (in 8.5) to use the database layer’s merge statement. Prior to that, the logic used "deletes and inserts". Depending on the version of Postsgres, the generated SQL statement for a merge statement is different. The “INSERT … ON CONFLICT … UPDATE” syntax is generated for Postgres 9.5+ AND when there is a PK constraint defined for the DB table. Otherwise, the complex UPSERT statement (old syntax) is generated, as was the case in this issue. This is a known issue in the Postgres server software where it mis-interprets the number of columns involved. i.e., it mistakenly counts the number of columns twice. As a result, the actual maximum columns allowed is only half of the official limit (1664). The same UPSERT statement does not cause the “exceeds limit” exception if there are 832 or fewer columns in the statement. To resolve this, an option has been provided to select between the “original logic” (deletes and inserts) and the “merge statements” logic by way of the DSS “decision/datasets/db/useMergeStatementForUpdates”. Setting “true” will use the merge statement logic, and setting “false” will use deletes and inserts. When the DSS is not defined, the default is "true" and the system will use merge statements in the form preferred by Postgres 9.5+.
INC-
196961 · Issue 693473
Iteration method updated for SetRequiredSkillsCountColumn
Resolved in Pega Version 8.7.1
After update, database utilization spiked and did not drop. Investigation traced this to the use of Local.totalCount in pzSetRequiredSkillsCountColumn, which caused the iteration loop to run more times than necessary. This has been resolved by replacing Local.totalCount with Local.iterationsCount in the iteration.
INC-184040 · Issue 688256
Improved accessibility for Disclosable Documents/attach files/auto selection dropdowns
Resolved in Pega Version 8.7.1
When using Dragon for accessibility, issues were seen when trying to select different options in the dropdowns related to attaching multiple files. This was caused by the legacy grids being used not supporting this type of accessibility functionality, and has been resolved by updating pzAttachFileDDFileList to use an optimized table instead.