SR-123815 · Issue 188298
AddTime calendar function corrected for calculating expiry times
Resolved in Pega Version 7.1.8
Using the out-of-the-box @addTime function to calculate expiry time was not calculating the correct time or was reporting a missing calendar when passed a calendar instance. The root cause of this problem was due to the calendar instance not using the time zone field while acquiring Gregorian Calendar in the class CalendarUtility. java. This datetime problem has been fixed.
SR-123847 · Issue 187828
Ensured Property-Set of embedded page list to data page
Resolved in Pega Version 7.1.8
When performing a Property-Set to copy a source Pagelist property into a destination Pagelist property that references an editable data page, the data was not being propagated from the destination Pagelist property into the editable data page. The system has bene updated to ensure the Property-Set step moves the data to the target clipboard page and also updates the editable data page.
SR-123851 · Issue 184413
Stale thread issue resolved and logging updated
Resolved in Pega Version 7.1.8
The error "com.pega.pegarules.pub.context.StaleThreadError: Thread has been recycled" was appearing sporadically in the log files. The root cause was traced to the usage daemon, and has been resolved by changing the logic such that while capturing usage data, the system will avoid setting the last thread as processing thread while taking requestor lock. This avoids usage of a stale thread. Additionally, a change was made to avoid repeated logging of a stale thread error while creating a PRException object when exception occurs do occur due to a stale thread.
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-123968 · Issue 194580
Added special character handling to Process Modeler
Resolved in Pega Version 7.1.8
After migration, some sites attempting to open flows through Process Modeler saw only the 'loading' message for a long time and then an error was displayed. This was traced to the use of user-input strings containing special characters in the canvas-based rule data, and has been resolved by adding character escaping during the model generation.
SR-123968 · Issue 194306
Added special character handling to Process Modeler
Resolved in Pega Version 7.1.8
After migration, some sites attempting to open flows through Process Modeler saw only the 'loading' message for a long time and then an error was displayed. This was traced to the use of user-input strings containing special characters in the canvas-based rule data, and has been resolved by adding character escaping during the model generation.
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-124054 · Issue 189568
Simulation delete timing issue resolved
Resolved in Pega Version 7.1.8
When attempting to delete a simulation, if the deletion process exceeded the system time-out or the space on the database required for undo was too small (as can occur when many simulations have been run and the simulation output table contains many millions of records), the mass deletion failed and the system became hung or returned a time-out screen which required logging out and in again. At that point it was seen that the simulation results had been removed from the list but the actual results deletion did not complete. This was caused by the simulation work item being closed first, followed by the delete of the table. In the case of a failed deletion because of any DB issue, manual intervention was required to delete the records from the table as the simulation object was no longer available. To resolve this, the sequence of steps while deleting the Batch WO from LPhas been updated to show the relevant error message in case of failures for any reason, and the work object is closed after the output table is deleted.
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.