SR-C19835 · Issue 360026
Refresh fixed for data pages
Resolved in Pega Version 8.1
A refresh was causing empty data pages due to a sequencing error in the code. This has been fixed by rearranging the evaluations.
SR-C20061 · Issue 362706
Logic changed to improve pr_assembledclasses use on multi-node systems
Resolved in Pega Version 8.1
Previously, each time an RUF was generated on a multi-node system a pulse event was sent to other nodes to re-generate the library as well. When these nodes would get the message, they would regenerate the library as well as in some cases send out the pulse event. In complex installations, this resulted in ~1.4 million updates per hour to the database table in pr_Assembledclasses. In order to improve performance, the system will no longer generate the library on a generate pulse event if eager population is enabled. The library is simply invalidated.
SR-C20064 · Issue 359982
Streamlined truststore.jks creation
Resolved in Pega Version 8.1
Many folders were being created in the Tomcat temp folder that each contained the file "truststore.jks" used to hold the certificates used in Kafka connection security settings. The implementation has been changed to streamline this: a new KafkaSecurity class was created for a KafkaInstanceImpl which holds 1 truststore file instead of the previous method which created the truststore file in getProducer and getConsumer.
SR-C20240 · Issue 361514
Display caption checkbox control honored
Resolved in Pega Version 8.1
In some configurations the Check Boxes control was not respecting the "Display caption when read only" setting. This has been fixed,
SR-C20466 · Issue 361005
Security/privacy enhancement added to allow overriding URL parameter values being logged
Resolved in Pega Version 8.1
The Connect-REST method/engine class throws an exception when it times out; the standard behavior is to disclose the entire URL string including URL parameter values, but in some cases the parameter values may contain sensitive data. To support greater security and privacy, an enhancement has been added to override this behavior when desired by adding an extra check to filter the data being displayed in the PegaRULES log.
SR-C205 · Issue 354134
Special character handling improved for field value rule description fields
Resolved in Pega Version 8.1
When special characters such as valor do preÝ âê ($) were used as part of the description field in a field value rule, the description field was empty or not visible after the field value rule was saved. This was an issue with the way the encoding API was applied to special characters, and has been corrected.
SR-C20839 · Issue 367745
Performance improved for screen rendering and checkbox action in Microsoft Internet Explorer
Resolved in Pega Version 8.1
After upgrade, Screen rendering and checkbox action was slow in the Microsoft Internet Explorer Browser. To improve performance, the following updates have been made: 1) Conditionally skipping multiple flex resizes on harness resize event. 2) Replaced $ calls in getCorrectPropertyElemFromDOM() with native querySelector. 3) Grid's getScrollParent() (~200ms) was erroneously comparing element’s scrollWidth with scrollWidth (instead of clientWidth) each time. 4) ui_inspector.js was making multiple attempts to get the closest element. The results are now cached. 5) In client expr evaluation, getAllRefreshableTargets() queries for the entry were handled three times. The query is fired only once now and the results are cached.
SR-C20923 · Issue 370325
Added explicit cleanup of non-serializable objects in the Connect-SOAP ParameterPage
Resolved in Pega Version 8.1
In investigating an application continuously logging error messages for Serialization, it was found that Connect-SOAP execution leaves non-serializable objects in the ParameterPage, which in-turn caused this the error logging upon requestor passivation. To resolve this, code has been added to remove the pyServiceClient, soapHdr, and activityParamPage parameters from the ParameterPage after use.
SR-C21009 · Issue 362404
New implementations for pzClearAllRecentItems activity
Resolved in Pega Version 8.1
A new implementation has been added to allow for greater customization when clearing all non-dirty document threads by configuring pzClearAllRecentItems activity. This will clear all the threads in one request instead of using multiple requests. pzPooledDoClose - This is a new activity to execute the pzDoCloseWrapper activity for each thread. This uses executeActivityInContext engine method to execute the doCloseWrapper activity on a particular thread context. Input to this activity is the documents information to be closed. pzDoCloseWrapper - This is updated, to maintain the portal data model in sync. After execution of doClose activity, pzFindAndUpdateElement. pzClearAllRecentItems - Updated to get the pooledDoClose parameter value of pzClearAllRecentItems (Runactivity action) and sends back to the client. webwb pzpega_ui_doc_lifecycle js - Updated harnessOnBeforeUnload method for not to send pzDeleteDocumentPg request in case of Microsoft Internet Explorer . webwb pzpega_ui_doc_ajaxengine js - Added new method, getAjaxTrackerID, to return the tracker id. webwb pega_desktop_api.js - Updated updateRecentList method, to pass pooledDoClose parameter for desktopaction("UpdateRecentList"). webwb pzpega_ui_dynamiccontainer js - Updated to collect all documents information and make request to pzPooledDoClose activity when pooledDoClose is enabled for pzClearAllRecentItems (Runactivity action). webwb pzpega_ui_doc_tabsupport js - Updated onActivate method, to send the request to maintain portal data model in sync with client. UMicrosoft Internet Explorer lementModel pzFindAndUpdateElement - Updated to not make any data model element as active element when invoked from pzDoCloseWrapper activity. pzUpdateCapturedDCModel - This activity is called only on tab switching/closing cases to update pyDisplay's pyUIActive and pyUMicrosoft Internet Explorer lements pages and Recent Gadget. It also includes change tracker's div.
SR-C21036 · Issue 369503
Report definitions with 'Include descendant classes' repaired
Resolved in Pega Version 8.1
The behavior for report definitions was unexpectedly changed as a result of work done to address another issue; if the checkbox for "include descendant classes" was set to true on a report definition, descendant classes with directed inheritance were not included. This regression has been fixed.