INC-224487 · Issue 729466
Security test status message includes assignment
Resolved in Pega Version 8.8
After update, the error message generated during a security test returned Status OK 200 but without any content. This was traced to a skipped step in pzGetAssignmentActionDetails activity and has been corrected.
INC-225615 · Issue 725299
BAC updated for delegated circumstanced decision table rule
Resolved in Pega Version 8.8
An unregistered request error was encountered while launching the DelegatedRulesPage harness when pyBlockUnregisteredRequests >=1. This was traced to a delegated circumstanced decision table rule which caused a request error for the @baseclass.pzLookupCircumList activity, and has been resolved by updating the BAC handling for this activity.
INC-227714 · Issue 730395
Empty check added to OpenRuleAdvanced
Resolved in Pega Version 8.8
A blank screen was displayed when attempting to open a requirement set rule in Dev Studio. This was a missed use case while updating the OpenRuleAdvanced control to handle BAC compatibility, and has been resolved by adding an empty check in addition to the existing null check along with an 'if' condition to check for pyActivity input.
INC-227819 · Issue 735349
Improved browser compatibility for ContentDisposition header
Resolved in Pega Version 8.8
When files were downloaded from a Sharepoint repository by clicking on the link, the filename was appended by a unique case instance ID or a sequence number to avoid duplicates. This caused a workflow disruption due to the reupload considering the file to be new rather than updated. This was traced to an issue with the usage of the ContentDisposition header which should have set the default file name: as created, the method was not compatible with Google Chrome on Microsoft Windows and was ignored. This has been corrected by updating the ContentDisposition header to set the default file name correctly when using supported browsers.
INC-229440 · Issue 734024
isRulesetLocked updated for efficiency
Resolved in Pega Version 8.8
When trying to access some access roles, the error "The number of database bytes input for this interaction has exceeded the ERROR level for Requestor" was generated. Investigation showed there were many read-BLOB events being triggered by the when rule pzRuleInLockedRuleSet. To address this, isrulesetlocked has been modified to not open every version of a ruleset, but instead perform a simple count and check if the ruleset exists.
INC-233264 · Issue 743670
Rule updated to "Refactor Copy Move Merge"
Resolved in Pega Version 8.8
The Pega-RulesRefactoring:08-01-01 agent rule "Refactor Copy/Move/Merge" has been updated to remove the '/' character as it was interfering with the agent name validation.
SR-108009 · Issue 154664
Execution plan reuse on SQL Server 2008 R2
Resolved in Pega Version 7.1.7
Due to the way a SQL server treats execution plans, each decimal bind value with a different scale is treated as a different type. To optimize the execution, the scale value for the execution plans will now be set the same as the table definition for obj- methods.
SR-110773 · Issue 160105
WorkPage now properly deleted after rule checkin
Resolved in Pega Version 7.1.7
There was an issue with rule check-in where it created the WorkPage with the obj-class Work-ProjectManagement-CheckIn, but it did not delete WorkPage when the check-in was complete. To address this, protective code has been added that checks the class of WorkPage for the existence of expected properties in order to properly handle the related clipboard pages.
SR-111606 · Issue 163137
Improved consistency with multiple class inheritance rules
Resolved in Pega Version 7.1.7
A gap in the handing of multiple class inheritance was causing an issue with the consistency in picking the correct rule from a cache. If the entry was placed in a class where the applies-to class of the rule could not see it, that entry was missed from invalidation later on during the save. This could be temporarily remedied by clearing the cache, but the rule handling has been updated to consistently choose the correct rule from the cache under multiple inheritance.
SR-111945 · Issue 157966
Closing Lucene search popup in Firefox corrected
Resolved in Pega Version 7.1.7
When using Firefox, it was not possible to close the popup box generated by a Lucene search unless a work object was selected first. This was caused by an error the the method used to access the document id, and has been corrected.