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-187350 · Issue 703199
UUID added to iOS direct photo upload to differentiate filename
Resolved in Pega Version 8.7.2
When "Content Storage" with the option "Store in repository" was enabled on the "Integration" tab in the Application definition, it was not possible to add more that two attachments to a case with an iPhone when directly capturing a photo through the camera app instead of uploading the photo as an attachment using the gallery. When using the default "Store in Pega database", the additional photos could be uploaded directly from an iOS camera without any errors. Investigation showed that when "Store in repository" was enabled, a file name conflict check was done in the repository. Because the iOS camera app saves/uploads every image as "image.jpg", this caused the error when checking for a filename conflict in the repository. This has been resolved by adding code to append a UUID to the attachname when the device is mobile and browser is Apple Safari.
INC-192673 · Issue 706242
Tab highlighting updated
Resolved in Pega Version 8.7.2
Not all elements were indicated with yellow highlighting when tabbing through the screen. This has been resolved.
INC-194180 · Issue 704637
GetChildcases handling updated for large numbers of cases
Resolved in Pega Version 8.7.2
When a very high number of child cases being processed contained a wait shape that was dependent on the movement of a parent case, some of the cases were moved to the next step of the flow automatically while others required a manual command to ResumeFlow. In extreme cases where many child cases were waiting, a node crash could occur. This was traced to the pzGetChildcases report having a maximum value of 500 lines, and has been resolved by increasing the maximum number of rows to retrieve to 9999 in the Data Access Tab of the pzGetChildCases report definition. In addition, the pxCheckFlowDependencies activity has been modified to perform with a higher number of cases, and DSS(MaxRecords) logic has been added to split the child cases into multiple queue items for each access group to decrease load on each thread process.