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-123911 · Issue 189019
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-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-123945 · Issue 185036
Corrected symbol handling in ToolTips
Resolved in Pega Version 7.1.8
In the ToolTips, the '@' character was being replaced with '@'. This was an issue with the character being parsed instead of being treated as literal text, and has been fixed.
SR-123945 · Issue 186241
Corrected symbol handling in ToolTips
Resolved in Pega Version 7.1.8
In the ToolTips, the '@' character was being replaced with '@'. This was an issue with the character being parsed instead of being treated as literal text, and has been fixed.
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-123961 · Issue 184528
New Stylesheets save to harness correctly
Resolved in Pega Version 7.1.8
Stylesheets added to the StyleSheetName pageList were not getting saved in Harness rule. This was traced to the process not updating the primary page on clipboard, and has been corrected.
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.