SR-C73608 · Issue 415510
Updates to controls and labels
Resolved in Pega Version 8.2
Issue 413604:When configuring a button with a disable condition, the condition was not returned in the readonly field. The PegaAPI has now been updated to support "disable". Issue 413597 / 413598: While calling the API to get the view of the screen as a JSON format, button type controls were not returning the label of the field using the OOB pxButton control. This has been fixed. Issue 413625: The PegaAPI section was missing when using clipboard page or data page with the rest method. To correct this, support for Embedded page has been added in the pyWorkPage for PegaAPI.
SR-C53759 · Issue 404973
Corrected revalidate and save of Service REST rule after upgrade
Resolved in Pega Version 8.2
After upgrade, opening an existing Service REST rule and trying to save it in a higher ruleset using the revalidate and save tool resulted in the error "pyResourcePathParams.pyParameterName : This field should not be blank". This was caused by the Service REST xml not getting updated and has been corrected by adding UpgradeOnOpen to the process.
SR-C64243 · Issue 403381
Data flow region switching method added to prevent truncating event strategy data
Resolved in Pega Version 8.2
An enhancement has been added to allow customers to switch data flow execution from one region to another without clearing event strategy data. This process looks like (1) Dataflow is started on one region. (2) Dataflow is paused in same region. (3) Dataflow is started in second region. Previously, step 3 would delete the existing event strategy data. To prevent that, a new run option has been added named 'pyDataFlowStorageTruncateOnStart'. By default, this is set to true and truncation will occur. If set to false, the event strategy data will not be deleted.
SR-C65633 · Issue 408042
Improved handling for parsing multiple formats of DateTime
Resolved in Pega Version 8.2
In order to further correct an issue with DateTime formats, the system will now use the parseAsDateTime and parseAsDate functions to properly handle the parsing of the date and date time values. The Pega format will be tried first, and if that doesn't work then the UTF formats will be used. If there is still an issue, the system will call back on the original parseAsXSDDateTime/Date which should catch all cases. An exception will no longer be thrown until after all parsing methods are tried.
SR-C65239 · Issue 411325
Check added to resolve nested grid component mismatch
Resolved in Pega Version 8.2
When using a nested repeating grid with expand pane option and expand multiple row options, running a screen flow resulted in a component mismatch error when moving from one assignment to another. This was traced to a limitation in the implementation that sometimes caused the parameter of the outer and inner grid to become corrupted or affect the wrong grid. In this case, the paramters startIndex and recordsInCurrentPage were resulting in a numberformatexception which in turn caused the component stack mismatch error. To fix the issue, an empty check has been added for startIndex and recordsInCurrentPage in the grid generation code.
SR-C51848 · Issue 404318
Additional validation added for administrator role name in current application
Resolved in Pega Version 8.2
When running an extract rule from designer studio, the when rule "hasadminrole" was getting called to check if the user has the "pegarules:sysadmin4" role. After upgrade, this when rule was returning false if "pegarules:sysadmin4" was defined in 'manage dependent roles', requiring the role to then be entered manually. This was traced to a condition where the BIX extract was being run from a CS application that did not have any access role with the current application name :Administrator, but instead used the access role name :SysAdm4, . To resolve this, an additional condition has been added to validate whether the current application has an access role with name "current application name:SysAdm4" in their access group to run BIX extract.
SR-C48318 · Issue 388212
Template circumstancing works for report definition
Resolved in Pega Version 8.2
If a report definition was circumstanced using the template option, the base report definition was always shown shown instead of the circumstanced one. This was caused by a missed use case , and has been corrected.
SR-C55082 · Issue 392684
Cassandra upgrade
Resolved in Pega Version 8.2
Cassandra has been upgraded from 2.1.14 to 2.1.20.
SR-C53866 · Issue 392827
Added handling for custom skin using the $ symbol for value
Resolved in Pega Version 8.2
After upgrade, using a custom style sheet to display the $ symbol prior to values being shown or entered caused the application skin to not log and throw an error. This was caused by a missed use case for adding $ in css :before or :after content due to a dependency on this "$" notation for fetching right mixin color from skin color. The array index out of bounds exception was generated by the statemachine parser while handling special characters because it considered the quotes of csscontent to be corrupted. To resolve this, an extra check has been added for handling """ and "'" cases in cssCustomParser.java and junits have been updated.
SR-C50324 · Issue 393499
Synchronized block method added to load keystore set with RUF
Resolved in Pega Version 8.2
A recent enhancement allows for the SAML auth service to use a reference to an external file for the signing certificate keystore. When the keystore had the password set using a Rule-Utility-Function, rather than being static, there were intermittent login fails with the error "unable to process SAML WebSSO request1" on the screen, and the RULES logs contained thousands of entries of an error indicating "Password is wrong". It was sometimes possible to log in by starting a new browser sessions and trying again. This was an issue with the PasswordHash property being changed from a static to a non-static field: it was not thread safe, though each object got its own copy of the instance, because if two or more threads call the setPasswordHash() method on the same object, all of these threads tried to simultaneously update the passwordHash instance variable and incorrect results were seen. To correct this, the system will use a synchronized block when loading the entries into cache in the getKey() method - Caller function of KeystoreCacheImpl.java.