SR-126368 · Issue 196112
Application Wizard node validation improved
Resolved in Pega Version 7.1.8
When using the new application wizard on a FW which has multiple built ons, selecting cases from a built-on app caused the wizard to validate the classes incorrectly and expected the user to change class names. To correct this, the application express has been updated to track intermediate class nodes that are not class groups, and now tracks non-workgroup and case type leaf name components and aggregates them.
SR-126414 · Issue 189748
Static content retrieval corrected
Resolved in Pega Version 7.1.8
StaticContent was not being cached by the browser for all HTTP responses that came from the remote nodes via FCM/IAC. Instead, every request resulted in a full round trip to the server, causing performance problems for end-users. As part of a recent change, the trailing slash after the thread was removed from the initial request sent from the browser to Gateway to avoid the retrieval of static content for every thread. However, the gateway code slash was appended after the thread for the subsequent requests. This has been corrected.
SR-126432 · Issue 189500
Enhanced SQL error logging
Resolved in Pega Version 7.1.8
In order to better understand and address sporadic "Unexpected error during processing" SQL errors, logging has been added to capture the exception message when classloading from database fails. The changes are done in AbstractJdbcJarReader and the loggers are of level ERROR and will be logged to Appserver log files.
SR-126439 · Issue 189008
WebSphere security updated for class name
Resolved in Pega Version 7.1.8
IBM issued a bug alert for WebSphere that affected the prsysmgmt application. To meet the security criteria outlined, the serveServletsByClassnameEnabled attributes have been changed to false in prjmxui/WEB-INF/ibm-web-ext.xmi file.
SR-126448 · Issue 189959
Special character handling added to 'pzupgraderulemessages'
Resolved in Pega Version 7.1.8
The 'pzupgraderulemessages' activity was introduced to recalculate the pzinskeys of Rule-Message instances. These instances were migrated to a new table and the property, and pyclass name was made part of the key. Running this activity was made mandatory as part of upgrade/update process effective v 7.1.7. This activity selects each rule-message instance using its pzinskey and checks if it needs to be recalculated. To fetch the Rule-Message record, a plain SQL is used which did not escape any special characters in the pzinskey (\t, etc.).However, this lack of character escape was problematic for some customers who had existing rules utilizing special characters, so the activity has been updated to use a prepared statement which takes care of escaping characters in place of the generated plain SQL.
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.