INC-213918 · Issue 714452
Discard button works consistently
Resolved in Pega Version 8.7.2
After check out, the discard button was not working consistently for decision tables or MapValue. Investigation showed this occurred when an exported file was being downloaded in the same window, as the thread would be busy with the file and not able to perform the discard action on the window. To resolve this, the configuration for the download on the same window has been removed, exportToDecisionTable has been modified to handle an iframe, and a runScript action has been added to register the exportToExcel activity and download in iframe.
INC-208629 · Issue 704589
ReviewArchivedCase shows case hierarchy
Resolved in Pega Version 8.7.2
After update, opening the archived cases in the ReviewArchivedCase harness did not show the case hierarchy dropdown. Investigation showed this was caused by the D_CaseBreadCrumb data page calling the source activity with wrong instance key, along with the pxCaseBreadCrumbPopulate activity not supporting breadcrumbs for archived cases. This has been resolved by changing the method how the parent case item is being fetched from storage, using Obj-Open-By-Handle instead of Obj-Browse as the latter doesn't support checking the second storage. The pxBreadcrumbsCount Declare Expression has also been removed in order to facilitate the data page loading.
SR-A92631 · Issue 270068
VBD Actuals Query works correctly on WebSphere 8.5
Resolved in Pega Version 7.2.2
Nested JDBC metadata calls were not working in WebSphere 8.5/DB2 due to the nested metadata query causing the initial query's ResultSet to close prematurely. This was traced to unexpected behavior in IBM WebSphere 8.5 when querying DB column metadata while iterating another DB metadata ResultSet, and has been resolved by modifying the DSM/VBD code that queries the DB for dimension metadata so it will load the metadata in two stages to avoid nesting of metadata queries.
SR-A92952 · Issue 262158
Proposition filter validates all rows on save
Resolved in Pega Version 7.2.2
On changing the name of the strategy component , the proposition filter was not validating the change for all the propositions but was only validating for the first proposition which had focus. The initial design was intended to skip validation when the proposition row was not viewed by the user with the goal of saving time by skipping the propositions that were not edited. However, this posed a problem that if the referenced rules were removed then the rule continued to pass validation. To resolve this, the system will force validate all the rows even though they may not have been edited.
SR-A82001 · Issue 255793
Keyed access data pages consider grid sort
Resolved in Pega Version 7.2.2
Page properties populated from keyed data page access were not taking into account grid sorting when passing the page list keys. This did work with the data page set to "Reload once per interaction" on the Refresh strategy, but this caused performance issues (as the SOAP service source was invoked with every single interaction on the data page). The cause was the hash table of keys in keyed page list not being rehashed after sorting, and this has been fixed.
SR-A76645 · Issue 253467
Added variable catch to IAC validation
Resolved in Pega Version 7.2.2
Whenever there was a pattern of aaa/$aaa/$aaa for thread name (more than one occurrence of delimiter "/$" ) in IAC, the request failed when submitting the modal dialog with the error "There has been an issue; please consult your system administrator". This was due to the intended validation for the IAC first request (does not have Access group) being performed on every request. To correct this, a catch has been added to ensure the validation happens only for a request without access group and with appname.
SR-A96096 · Issue 264802
Tenant hash preserved for SOAP to accommodate load balancer SSL termination
Resolved in Pega Version 7.2.2
With Cloud 2.1, there was a need to set prconfig settings in order to accommodate SSL termination at the load balancer side, but the SOAP messages between a client (tenant) and PDC were having their tenant hash stripped by the engine. This was due to SOAP requests made to a specific Tenant by a monitored node (client) of PDC(MT) being redirected to a Shared tenant in PDC. To resolve this, even when "initialization/contextrewriteenabled" is set to true, the value for "pxReqPathInfo" will be set by HttpRequestMapper.buildRequestorDataFromHttpRequest() in the Map returned by it.
SR-A24147 · Issue 249164
Google Chrome check added for character count
Resolved in Pega Version 7.2.2
Unlike Firefox and Microsoft Internet Explorer , Google Chrome considers new line/carriage returns as two characters. This resulted in different character count values on refresh than when entering the text on the text area. This also could cause unexpected truncation of the text due to exceeding the max character value. To account for this, a condition specific to Google Chrome has been added to the rule utility function pzGenerateTextArea to take into consideration two characters for a line break or a carriage return.
SR-A67518 · Issue 251304
Google Chrome check added for character count
Resolved in Pega Version 7.2.2
Unlike Firefox and Microsoft Internet Explorer , Google Chrome considers new line/carriage returns as two characters. This resulted in different character count values on refresh than when entering the text on the text area. This also could cause unexpected truncation of the text due to exceeding the max character value. To account for this, a condition specific to Google Chrome has been added to the rule utility function pzGenerateTextArea to take into consideration two characters for a line break or a carriage return.
SR-A24147 · Issue 253601
Google Chrome check added for character count
Resolved in Pega Version 7.2.2
Unlike Firefox and Microsoft Internet Explorer , Google Chrome considers new line/carriage returns as two characters. This resulted in different character count values on refresh than when entering the text on the text area. This also could cause unexpected truncation of the text due to exceeding the max character value. To account for this, a condition specific to Google Chrome has been added to the rule utility function pzGenerateTextArea to take into consideration two characters for a line break or a carriage return.