INC-136208 · Issue 585226
Case history filter added for manual instantiation of Child Case
Resolved in Pega Version 8.5.1
After upgrade from v7.4 to v8.3, creating any child case from a parent case unexpectedly added the audit history "Child case xxxxx has been manually instantiated" to the parent case. In order to make this customizable, an "isHistoryAvailable" function has been added in the 'when' condition of "AddCoveredWork" Activity's "History-Add" Step. This will use the FilterHistory decision tree, which now has a setting for "ChildCaseInsAudit" to control whether or not the manual Instantiation of a Child Case will appear in the case history. The default is "true"; setting it to "false" will suppress the message.
SR-D75097 · Issue 539516
Improved handling against formula injection attacks in Export to ExcelJJ
Resolved in Pega Version 8.5
Every time a possibly vulnerable cell value was found during Export to Excel, the value on that cell was modified to prevent a formula injection attack. If the value was non numeric, it would still render an apostrophe, although it should be hidden. Previous work on this issue involved the addition of a DSS which allowed this security to be disabled if the Excel was going to be consumed by an external tool, but the security implementation used to protect against calculation injection has reworked the ExcelSecurity utility function to allow the ability to change the cell style of a cell that is potentially vulnerable to formula injection attacks. This change no longer changes the cell value but instead applies a new cell style that has quotePrefix enabled.
SR-D78467 · Issue 542318
Component rule check added to suppress unnecessary guardrail warnings
Resolved in Pega Version 8.5
After creating a component application using Configure > Application > Components, guardrail warnings were seen when saving the component. The component application allowed adding rulesets or other applications, but did not have all the tabs found in a normal application, so there was no option for adding the associated classes to define the UI class, Integration class and data class in the component application. As component is mostly a part of (or embedded inside) an application, this function was not given options to justify or suppress guardrail warnings like Rule-Application. To resolve this, a check has been added for component rule before generating guardrail warnings for Empty UI page, Empty Integration class, and Empty Data class.
INC-118926 · Issue 563807
ArtifactoryStorage URL construction with port updated
Resolved in Pega Version 8.5
After configuring a repository as a JFROG artifactory with a ruleform that provided a URL / port number and repository name, test connectivity worked as expected, but deploying the codeset using pipeline or importing the codeset using the import functionality generated the error "Unable to construct artifactory url due to invalid file path". The root cause of the issue was traced to the ArtifactoryStorage java class, which did not accept the port number in the format provided due to changes in the API. If there was no portNumber in the URL, the issue did not occur. To resolve this, the constructor has been changed to properly build the URI per https://docs.oracle.com/javase/8/docs/api/java/net/URI.html.
INC-125458 · Issue 562535
ArtifactoryStorage URL construction with port updated
Resolved in Pega Version 8.5
After configuring a repository as a JFROG artifactory with a ruleform that provided a URL / port number and repository name, test connectivity worked as expected, but deploying the codeset using pipeline or importing the codeset using the import functionality generated the error "Unable to construct artifactory url due to invalid file path". The root cause of the issue was traced to the ArtifactoryStorage java class, which did not accept the port number in the format provided due to changes in the API. If there was no portNumber in the URL, the issue did not occur. To resolve this, the constructor has been changed to properly build the URI per https://docs.oracle.com/javase/8/docs/api/java/net/URI.html.
SR-D78659 · Issue 545760
Resolved CSV validation overflow in Google Chrome
Resolved in Pega Version 8.5
When using Google Chrome, validation of records was getting stuck in the UI at 32000+ while importing a CSV file with many invalid records when using the import option in Data type’s local data storage. Investigation showed the Call Stack size limit was exceeded in the Google Chrome dev tools due to the ":first" selector being passed to the Jquery find() method to find the element from the first element child of the XML doc. This selector causes maximum callstack exception when the document is large, and this is a deprecated selector in later versions of Jquery. To resolve this issue, the XML function in pzpega_tools_asyncprocess has been updated to replace the ":first" selector.
SR-A6567 · Issue 216325
Specification data linking allowed for all decision types
Resolved in Pega Version 7.2
When entering specification data in the properties panel of a decision shape, a specification rule automatically created in the background could be opened and viewed but the specification rule was not linked correctly to the flow rule. The specification was not present in the 'For flow components' section of the Specification tab of the flow rule, and it was incorrectly documented in a section headed 'Other Specifications (outside the process)' in the Application Document. This was found to be inconsistent execution of the specifications function where the existing code supported use case linking only for few decision types while the UI allowed link specifications for all decision types. To resolve this issue, 'Data-MO-Gateway-Decision.Validate' has been updated to allow linking for all decision types.
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-139624 · Issue 595988
Validation error messages persist appropriately
Resolved in Pega Version 8.5.2
Whenever there was a Validation check on a flow action Validation Tab and Post Processing Activity, the error message appeared on the screen momentarily and disappeared. Intermittently, the validation error would stay on the screen after appearing a second time. This was traced to the refresh action happening in the wrong context due to the refresh action of the Ajax container being called twice, once in postacrenderac and another time in the harness unload function.The case error DOM was present in the markup, but because of the refresh in the harness unload, the error message was removed from the DOM. This has been resolved by changing the refresh call from onHarnessUnload callback to postAcRender callback. Logic has also been added to prevent refresh when error messages are present.
SR-D7798 · Issue 465259
Grid reordering has correct row numbers in embedded panes
Resolved in Pega Version 8.3
When using an expand pane grid with row numbering and row reordering enabled, normally reordering any rows handled the row numbers as expected. After a new record was added in the Embedded Pane and the rows were interchanged/reordered, the row numbers were not reordered with respect to the numbers. Expanding a row and reordering it with the previous row resulted in the numbers being correct and swapped, but collapsing that expanded row then showed its old number. Attempting to expand the above collapsed row/wrong number row instead expanded the previous row. To resolve this, the performModalAction function in ui_grid JS has been updated so the row page and primary page will be recalculated even for single expand reordering case.