SR-123911 · Issue 192195
Changed timing for retrieving autocomplete values after modifications
Resolved in Pega Version 7.1.8
When AutoComplete controls is used to populate Data, a wrong value was sometimes getting populated in the AutoComplete. The issue was due to the delay in change tracking request after the request is complete, causing it to take values from the server before the changes were committed. This has been corrected.
SR-123930 · Issue 185707
Corrected Oracle SQLs for checkout/locking
Resolved in Pega Version 7.1.8
Checked Out Specification Rules were not showing as Checked Out on the RuleSet Version. This caused issues when the RuleSet Version was locked based on the assumption that there are no checked out rules. If there was a checked out specification rule, the operator who was working on it could no longer save their changes because the RuleSet Version was locked. This was traced to Oracle not transferring the correct rules column for locking status, and has been resolved with updated triggers for Oracle for both standard and multitenant installs. Contact Pegasystems Global Customer Support for the updated SQL files.
SR-123960 · Issue 184251
Error message updated for report 'save as'
Resolved in Pega Version 7.1.8
The error message created when doing a 'Save As' report to a private category has been updated for clarity. Previously, the error generated was "The name you entered is not valid". This has been changed to "The name should start with letter followed by letter or digit or underscore".
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-124044 · Issue 188405
Save as fixed for French localization
Resolved in Pega Version 7.1.8
Setting localization to French in the Microsoft Internet Explorer browser and attempting a property save generated a JavaScript error. The root cause of this problem was traced to the localized French string value for the English equivalent of dupPropPrompt contained the ' character, which broke the first line of code in RULE-OBJ-PROPERTY PZDUPLICATEPROPERTYMSG. This has been fixed.
SR-124085 · Issue 184464
Adjusted error handling of "Prebuild Conclusions" during upgrade
Resolved in Pega Version 7.1.8
The "Prebuild Conclusions" task of an upgrade was failing with the error 'ClassNotFoundException'. This was caused by a misconfiguration in the operating environment that led to the jar file that contains the class not being on the classpath during the upgrade. There was a workaround of setting the build.conclusions=false, but a check has been inserted that will skip these error entries and continue building the remaining conclusion entries.
SR-124103 · Issue 185047
Error logging smoothed for service activities-multi threading on multiple nodes
Resolved in Pega Version 7.1.8
When an item was processed by one node and then in the process of being dequeued by the same node, other nodes attempting to access the same instance and queue received a warning message indicating the item had failed to dequeue. This message was verbose, and was filling up logs. For Advance mode Agents, when item is not found in the Queue Engine it was logging the message with "warnForced". To prevent the logging issue, the log level has been changed from 'warnForced' to 'warn'.
SR-124103 · Issue 185048
Error logging smoothed for service activities-multi threading on multiple nodes
Resolved in Pega Version 7.1.8
When an item was processed by one node and then in the process of being dequeued by the same node, other nodes attempting to access the same instance and queue received a warning message indicating the item had failed to dequeue. This message was verbose, and was filling up logs. For Advance mode Agents, when item is not found in the Queue Engine it was logging the message with "warnForced". To prevent the logging issue, the log level has been changed from 'warnForced' to 'warn'.
SR-124139 · Issue 186636
Corrected date format error on Data Agents Schedule
Resolved in Pega Version 7.1.8
Post-upgrade in a UAT environment, the Master Agent [Daemon] was not creating the Data Agents Schedule for Rule Agent Queue. This was caused by a month name vs month number mismatch in the YearlyMonth calendar property, and has been corrected.
SR-124153 · Issue 187971
Revised max datetime value for validation
Resolved in Pega Version 7.1.8
Previously, a date property could have a max set value of 31-Dec-9999. This max date was not working in some time zones due to the input date being converted to GMT for internal operations. This meant that 31-Dec-9999 in some locales was getting converted to 1-Jan-10000GMT, which then failed validation. To correct this, the datetime validity logic has been changed to use "1st Jan 00:00:00.000 10000 GMT" for validation.