INC-182534 · Issue 677142
Resolved Sub Report Filter Criteria error
Resolved in Pega Version 8.7
After upgrade from Pega 7 to Pega 8, Sub Report filter criteria were throwing a runtime error when pyPartyFullName from Index-WorkPartyUri was used as a filter condition. Under certain conditions, Sub Report and Main report use class joins with the Index-WorkPartyUri table to get the count of cases. In this case, the error was caused by the ValidateFilterValue edit rule passing the wrong class name for the sub report class join property. This has been resolved.
SR-B51367 · Issue 311023
Resolved stack overflow for three level nested WO
Resolved in Pega Version 7.3.1
A StackOverflow exception was generated when using three levels of nested work objects due to a recursive looping of the parent pzInskey looking for its children. To fix this, the pyLoadMyCasesNested activity has been updated to set the RD based on whether a parameter sent to it is blank.
SR-B70379 · Issue 326388
Post-printing screenshot window freeze fixed
Resolved in Pega Version 7.3.1
When an attached screenshot was clicked open and displayed in a pop-up window, the window was freezing after a print operation was performed. This was an issue with closing the ActiveX control through Microsoft Internet Explorer. To resolve this, the ActiveX control previously used has been changed to Silverlight.
INC-181401 · Issue 665935
Added handling for MS SQL datestamp format
Resolved in Pega Version 8.6.2
When using an Microsoft SQL Server, the browse operation was failing with an SQL error for the pyIHSummary dataset. Investigation showed there were some datasets that generated SQL statements with a date timestamp format that SQL was not able to handle implicitly, affecting browsing but not functionality. This has been resolved.
INC-181401 · Issue 665936
Added handling for MS SQL datestamp format
Resolved in Pega Version 8.7
When using an Microsoft SQL Server, the browse operation was failing with an SQL error for the pyIHSummary dataset. Investigation showed there were some datasets that generated SQL statements with a date timestamp format that SQL was not able to handle implicitly, affecting browsing but not functionality. This has been resolved.
SR-B55628 · Issue 315581
New check added for stale clipboard data in StarDependencies
Resolved in Pega Version 7.3.1
When both pyWorkCover and pyTopCaseWork were on the clipboard, the pzStartDependencies function renamed the pyWorkCover to pyTopCaseWork and again back to pyWorkCover after calling pzStartSubCases. However, pyWorkCover had stale data due to this renaming when multiple resolve activity calls happened, leading to pxcoveredcountopen to not decrease when a child case was auto resolved. This stale data occurred due to a known issue with the milliseconds of date time property being rounded when stored in the database column of an SQL server. The resolution is to provide a new overloaded method of OpenIfStale with parameters to skip the deferred list and maintain locking strategy; this will be used in the out-of-the-box Resolve activity instead of Obj-Browse to see if the page is stale.
INC-201334 · Issue 690735
ADMinputsource field population updated to handle transactional decisions
Resolved in Pega Version 8.7
The CaptureResponse flow was failing while writing to AdaptiveAnalytics with the error "IllegalArgumentException - argument does not represent JSON object". This occurred while running an outbound campaign where a few decisions were treated as transactional and did not have Model executions. Attempting to set a response for these decisions resulted in a JSON parse exception being thrown due to pxADMInputs not being populated (no models executed). This occurred only when using transactional actions in CDH, and was caused by the system only including predictive models during the make decision flow due to common inputs not being stored. While there was a workaround of overriding the property pzADMInputSource to use modelReferences instead of admInputContainer, this has been resolved by correcting how the pzADMinputsource field is populated. When there is no modelInput, the system will not populate that field so the page is ignored.
INC-194657 · Issue 682005
ADMinputsource field population updated to handle transactional decisions
Resolved in Pega Version 8.7
The CaptureResponse flow was failing while writing to AdaptiveAnalytics with the error "IllegalArgumentException - argument does not represent JSON object". This occurred while running an outbound campaign where a few decisions were treated as transactional and did not have Model executions. Attempting to set a response for these decisions resulted in a JSON parse exception being thrown due to pxADMInputs not being populated (no models executed). This occurred only when using transactional actions in CDH, and was caused by the system only including predictive models during the make decision flow due to common inputs not being stored. While there was a workaround of overriding the property pzADMInputSource to use modelReferences instead of admInputContainer, this has been resolved by correcting how the pzADMinputsource field is populated. When there is no modelInput, the system will not populate that field so the page is ignored.
INC-185434 · Issue 674053
Page group property passed correctly for complex questions
Resolved in Pega Version 8.7
When the Pega Survey Smart shape was used to configure a list of complex set of questions using Question rules and invoked using the Survey shape, the reload system was not passing the subscript value for the Page group property pyQuestionnaire. This caused an Invalid Reference exception and displayed an error pop up for the end user. Investigation traced this to a call to RefreshList to load a section holding pyQuestionnaire(Subscript) page content which was in place as part of a legacy fix but which has since been made unnecessary due to infrastructure changes in the DOM utilities. To resolve this, the ComplexQuestionCheckboxTemplate and pzComplexQuestionCheckBoxTemplateRowDetails section rules have been updated to remove the RefreshList action on checkbox.
SR-B44833 · Issue 311138
"Close All" tabs function made more robust
Resolved in Pega Version 7.3.1
When many tabs are opened in a support portal session using Microsoft Internet Explorer, the "Close all" dropdown became unresponsive did not list all open tabs. This has been fixed by modifying the pega_yui_tabview.js file "showTabsMenu" method to escape special characters.