SR-121183 · Issue 180073
Clarified complex visible 'when' usage with Expression Builder
Resolved in Pega Version 7.1.8
Execution was failing while using a complex visible 'when' expression with more than one Boolean operator. This is not incorrect behavior; Expression Builder only honors one Boolean operator, but the expression will work if typed directly and "Run on Client" is checked. This caused confusion due to the system not flagging the expression as unsupported in Expression Builder, and this has been fixed. In addition, the code has been updated to properly handle multiple logical operators so that runtime behavior is correct and no error is reported at save time. However, please note the following important information: For auto-generated sections, complex 'when' expressions will be allowed and honored when typed directly , but Expression Builders will still allow only one operator. Also, for non-auto generated sections and JSP directives, the old limitation of 1 operator will still apply.
SR-123977 · Issue 185468
Optimized regex decision tree for property and when values
Resolved in Pega Version 7.1.8
A regex expression run against long property names was resulting in system slowdown and stuck requestor threads. A similar issue was encountered with When rules. To resolve this, the decision tree has been optimized.
SR-A2 · Issue 203635
Updated use and edit of the 'Search for work' rule
Resolved in Pega Version 7.1.9
After upgrade, an out-of-the-box functionality to search for work items by selecting the case status and selecting a particular field to add as filter on that search was not working correctly and the search icon (which gives the list of status window dynamically) was missing. An attempt to perform a private check out of of the rule generated an error and did not allow 'save as' because it was unable to identify a property pyStringType. This issue was traced to a missing property 'pyStringType' in @baseclass, and this has been added.
SR-A3841 · Issue 208792
Cleaned up 'clear pages after non-use' function
Resolved in Pega Version 7.1.9
When the 'clear pages after non-use' option is selected, all the referencing threads should be closed and the page should be removed automatically. Instead, the document and threads were closed but the data page was not removed. This was traced to the Thread context not being present in the ThreadContainer during thread clean up, and has been corrected.
SR-A3841 · Issue 207560
Cleaned up 'clear pages after non-use' function
Resolved in Pega Version 7.1.9
When the 'clear pages after non-use' option is selected, all the referencing threads should be closed and the page should be removed automatically. Instead, the document and threads were closed but the data page was not removed. This was traced to the Thread context not being present in the ThreadContainer during thread clean up, and has been corrected.
SR-122191 · Issue 182679
Smoothed post-upgrade ApplicationSetup that uses previously generated LDAP configs
Resolved in Pega Version 7.1.8
An LDAP configuration created under a previous version of the software was generating an NPE after upgrading. This was traced to step2 of the ApplicationSetup activity where the system was expecting a page which was missing at that point due to the user not yet being fully identified. To avoid this, a step has been added to check if the page is available and avoid the NPE.
SR-123434 · Issue 183436
Smoothed post-upgrade ApplicationSetup that uses previously generated LDAP configs
Resolved in Pega Version 7.1.8
An LDAP configuration created under a previous version of the software was generating an NPE after upgrading. This was traced to step2 of the ApplicationSetup activity where the system was expecting a page which was missing at that point due to the user not yet being fully identified. To avoid this, a step has been added to check if the page is available and avoid the NPE.
SR-128397 · Issue 193116
reRunReport modified to use fully qualified RUF from Procomm ruleset
Resolved in Pega Version 7.1.8
In some cases, re-running a report would fail due to an inability to pick the correct instance of the Rule-Utility-Function getPropertyValue from two rulesets with the same parameters (in the KYC ruleset and the Procomm ruleset). This has been resolved by modifying the reRunreport activity to use the fully qualified RUF from the PegaProcom ruleset.
SR-131726 · Issue 202769
Fail-over updated to cover server crash scenarios
Resolved in Pega Version 7.1.9
In a testing event, the user session did not properly fail over to another server if the original server was shut down; an error was thrown instead. This was found to be an authentication issue where on node crash, a new requestor was created on the second node and then immediately authenticated as it is SSO. As part of authentication, the mRequiresSpecialProcessingForNodeCrash flag was cleared, meaning the node crash activity was not executed and entire portal was not refreshed. This has been corrected by updating the system to execute crash node activity for SSO cases.
SR-129159 · Issue 196998
Replaced missing OperatorID page for LDAP tab thread
Resolved in Pega Version 7.1.8
The OperatorID page in the clipboard was not visible in the tab thread when logged in through LDAP though it was visible in other threads or when not using LDAP. This was an error, and has been corrected.