SR-125539 · Issue 188739
Property Optimization Wizard working for Page level properties
Resolved in Pega Version 7.1.8
The Property Optimization Wizard was not working on Page level properties in a PageList due to due to the 'PropertyPath' Param in the displayResults activity having "()" characters that did not exist in previous versions. To resolve this, the "()" are stripped off in the Rule-Declare-Index name.
SR-125610 · Issue 189352
Added handling for property-defined declare value list indexing
Resolved in Pega Version 7.1.8
When adding or updating entries in a value list, the corresponding index entries were not getting created in the database. This was caused by handling that was missing from the minimum feature string clipboard properties that were recently introduced for better performance. These strings get created when it's not a reference property and has no declaratives defined etc. In this case, a declare index that is defined on the value list property should not have those elements be minimum feature properties. To correct this, the code has been changed to pass the featureID of the parent property.
SR-126011 · Issue 195418
RUF 'hasMessages' working with Declarative Pages
Resolved in Pega Version 7.1.8
Attempting to execute a Declarative Page with the RUF 'hasMessages' as a precondition caused a NPE. The error was caused by a null page call, and has been corrected by adding a null check for pageVarName and adding a find page call.
SR-126011 · Issue 195591
RUF 'hasMessages' working with Declarative Pages
Resolved in Pega Version 7.1.8
Attempting to execute a Declarative Page with the RUF 'hasMessages' as a precondition caused a NPE. The error was caused by a null page call, and has been corrected by adding a null check for pageVarName and adding a find page call.
SR-126092 · Issue 189635
Enhanced logging for SQL exceptions with BIX
Resolved in Pega Version 7.1.8
In order to enhance diagnostics while using BIX, logging has been added to print the stack trace for an SQL Exception while fetching the last updatedatetime.
SR-126177 · Issue 189199
Major ruleset skim logic updated
Resolved in Pega Version 7.1.8
When skimming a ruleset to a new major version, property rules (Rule-Obj-Property) which were available in lower rulesets but withdrawn in a higher ruleset version were skimmed to the new ruleset with their status as Available. This was contrary to expected behavior, as these rules should be ignored and not added to new ruleset. This has been addressed by correcting the logic in the special handling for Rule-Obj-Property types during skimming.
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-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.