SR-131430 · Issue 200005
Resolved error from empty repeating grid
Resolved in Pega Version 7.1.8
If a repeating grid is opened and no rows are added, the Microsoft Internet Explorer 8 browser was generating an error. When the grid is collapsed in the header its dimension parameters such as offsetHeight etc. are zero, so certain calculations in setHeadersWidth function in ui_grid js would fail and wrong dimension values would be assigned to the grid. Other browsers were failing silently in this situation, while Microsoft Internet Explorer 8 showed errors. To avoid any failure, a check has been added to the setHeadersWidth function in ui_grid js.
SR-A4227 · Issue 209904
Fixed History-Add API error
Resolved in Pega Version 7.1.9
Within a For loop calling History-Add to add Audit information resulted in the error: "Class not defined in dictionary: History-Code-Pega-List. Details: Invalid value for aClassname passed to .createPage" . This was caused by an incomplete implementation of the function; when History-Add method is called in the method generation for an embedded page, context is switched to the Top Level Page, but when the Top Level Page is Code-Pega-List the current page context is used. This context was not correctly reflected in the History-Add function, and has been fixed.
SR-B44878 · Issue 301248
displayHarness context maintained if established before passing pageName
Resolved in Pega Version 7.3
The runDataTransform() was running in the context of what was considered an incorrect page when called from the pre-js function of a Question shape when opening the case from the worklist. This was caused by using pega.offline.runDataTransform and passing the pageName parameter as null in an attempt to use the primary page context, but the system defaults to using the context of pyDisplayHarness instead of pyWorkPage when the pageName parameter is null. In order to support this configuration, the PreJS function of a question shape called from the displayHarness will maintain the context as displayHarness for pega.u.d.PrimaryPageName when passed.
SR-D67321 · Issue 532627
ShowXML activity deprecated
Resolved in Pega Version 8.3.2
The activity @baseclass.ShowXML has been blocked for security reasons. If the functionality is needed, a a single line step of "Show-Applet-Data" may be used.
SR-D82490 · Issue 547364
Invoke Connect-SAP method of IDoc type repaired
Resolved in Pega Version 8.3.3
Attempting to implement SAP connection via IDoc type connector failed and an empty error message was shown. This has been resolved with modifications to the SAP Connector functionality.
SR-D82490 · Issue 547366
Invoke Connect-SAP method of IDoc type repaired
Resolved in Pega Version 8.4.1
Attempting to implement SAP connection via IDoc type connector failed and an empty error message was shown. This has been resolved with modifications to the SAP Connector functionality.
INC-225257 · Issue 730293
Pega DateTime supports pre-1970 timestamps
Resolved in Pega Version 8.8
The function getTimeStampAsDateStamp from Pega DateTime class was not working correctly for dates before Jan 1st, 1970. Support has now been added for this use.
SR-D82490 · Issue 547365
Invoke Connect-SAP method of IDoc type repaired
Resolved in Pega Version 8.5
Attempting to implement SAP connection via IDoc type connector failed and an empty error message was shown. This has been resolved with modifications to the SAP Connector functionality.
SR-A11563 · Issue 224698
XSS security added to data table edits
Resolved in Pega Version 7.2
When editing a data table and saving the record, the request could be intercepted and a vulnerable string added to the pageIndex parameter. XSS security has been added to this function.
SR-C3153 · Issue 345296
Manage review team error fixed
Resolved in Pega Version 7.4
Any action in "Manage review team" function inside branch review was showing an error. This has bene fixed by passing a missing parameter as AssociationClass:"Link-Association".