SR-126455 · Issue 189883
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-126460 · Issue 190738
Corrected persistent highlighting of work object
Resolved in Pega Version 7.1.8
If a work object was opened from the following button in the left panel, that particular WO opened but remained highlighted in blue even after other selections were made. This was caused by a configuration issue where the pyFavorites section was refreshed if the FollowUnFollow count changed, but if there was a Mixin as the Background for Row focus and Row Selection cases the text would remain highlighted until there was another change in the FollowUnFollow count. In order to resolve this, "Use default background for this format" will be enabled by default.
SR-126468 · Issue 192170
CheckInCandidates rule issue resolved
Resolved in Pega Version 7.1.8
When checking in a rule via the rule Check-in Approval process, it was not possible to add rows. The problem was traced to the approved request being returned from the workbasket with the "Allowed to update row layout" checkbox unchecked. When check-ins are done via the Rule Approval process, the checked-in rule's copy is read from the database: however, due to the property 'pyAllowedToChangeRowsStr' incorrectly being left marked as transient for the Check-in Approval process, the property was not retrieved from database if that process was used. To correct this, 'pyAllowedToChangeRowsStr' property has been unmarked as transient.
SR-126490 · Issue 190168
Disabled unneeded PEGA0050 alerts
Resolved in Pega Version 7.1.8
PEGA0050 alerts were triggered when a clipboard page list was copied to another list. In general these copies happened when lightweight page lists are involved. In Pega 7, lightweight lists have been enhanced and these copies are not required in most of the cases. Because it is no longer needed, the "alerts/virtuallists/copy" setting has been changed to false to disable the alerts
SR-126513 · Issue 192544
Edit in Excel now handles 'HTTPOnly'
Resolved in Pega Version 7.1.8
After implementing 'HTTPOnly', Decision Table Edit in Excel was not working. Attempting to use it caused the system to stall for a few seconds while the label color was orange, and then the text color on the button went back to black but no Excel file popped up. This was found to be caused by the lack of a null check in case of HTTPOnly cookies in the edit_in_excel js function, and this has now been added.
SR-126530 · Issue 188522
Enhanced error handling for exceptions generated by import
Resolved in Pega Version 7.1.8
After upgrading to a single schema on Oracle 11.2 database, the system started up showed the login page, but once logged in a blank Screen/UI would be displayed and errors were logged indicating "Failed to resolve rule file". The rule file varies depending on the content source. This issue was caused by exceptions not being handled properly by import, and has been resolved by modifying the runWithRequester method (importImpl.java) to check for Exception as a return object object from the method invocation, and propagating the exception if one is returned.
SR-126530 · Issue 193829
Enhanced error handling for exceptions generated by import
Resolved in Pega Version 7.1.8
After upgrading to a single schema on Oracle 11.2 database, the system started up showed the login page, but once logged in a blank Screen/UI would be displayed and errors were logged indicating "Failed to resolve rule file". The rule file varies depending on the content source. This issue was caused by exceptions not being handled properly by import, and has been resolved by modifying the runWithRequester method (importImpl.java) to check for Exception as a return object object from the method invocation, and propagating the exception if one is returned.
SR-126545 · Issue 189937
Added remote case handling for password protected implementation applications
Resolved in Pega Version 7.1.8
There was a problem creating an implementation application in Application Express if the built-on application was password protected and the current logged-in application was also password protected, and the cases from built-on have remote case types. This was caused by validation issues, and has been corrected by modifying 'CreateObjectByPage' to pass the parameter 'SkipAddRemote' while calling save activity as true. Save will use this activity to skip current validation through 'ManageRemoteWorkTypesInApplication'.
SR-126546 · Issue 194655
Additional out-of-the-box controls marked for accessibility
Resolved in Pega Version 7.1.8
The following out-of-the-box controls have now been marked as accessible: UI Controls: - pxButton - pxHidden - pxDisplaytext
SR-126546 · Issue 200724
Clipboard message method updated to improve performance
Resolved in Pega Version 7.1.8
Occurrences of ClipboardPage#getMessagesAll have been replaced with ClipboardPage#getMessageCountAll to improve performance.