SR-C74954 · Issue 413140
Fixed column search function for Report Browser Data Explorer
Resolved in Pega Version 8.1.2
Searching/filtering for columns in the Data Explorer in the Report Browser was not filtering the tabs by the search string. This was an error caused by the unique ID changes for controls, and has been fixed by updating the getSearchTextElement() function in pega_report_events.js to use the name attribute rather than the ID attribute to identify the search bar. The tabClickCallback() has also been updated to not rely on window.event as it was causing discrepancies in Safari.
SR-C75689 · Issue 413136
restored to correct "pg empty after db.open" errors
Resolved in Pega Version 8.1.2
When opening the data page D_RepositorySettings, the error "pg empty after db.open" appeared in the logs. This was due to the data page referring to the files webwb/zchecked.gif and webwb/zchecked.gif in many sections of the data page rule form despite these files having been removed as part of a recent cleanup meant to reduce storage requirements. In order to resolve this error, the zunchecked.gif and zchecked.gif images have been added back and the error message generated in the RUF pzGetbase64encodedImagehas been improved to add the target filename: "error occurred while opening the image:webwb/zunchecked.gif"
SR-C53866 · Issue 402883
Added handling for custom skin using the $ symbol for value
Resolved in Pega Version 8.1.2
After upgrade, using a custom style sheet to display the $ symbol prior to values being shown or entered caused the application skin to not log and throw an error. This was caused by a missed use case for adding $ in css :before or :after content due to a dependency on this "$" notation for fetching right mixin color from skin color. The array index out of bounds exception was generated by the statemachine parser while handling special characters because it considered the quotes of csscontent to be corrupted. To resolve this, an extra check has been added for handling """ and "'" cases in cssCustomParser.java and junits have been updated.
SR-C64243 · Issue 412374
Data flow region switching method added to prevent truncating event strategy data
Resolved in Pega Version 8.1.2
An enhancement has been added to allow customers to switch data flow execution from one region to another without clearing event strategy data. This process looks like (1) Dataflow is started on one region. (2) Dataflow is paused in same region. (3) Dataflow is started in second region. Previously, step 3 would delete the existing event strategy data. To prevent that, a new run option has been added named 'pyDataFlowStorageTruncateOnStart'. By default, this is set to true and truncation will occur. If set to false, the event strategy data will not be deleted.
SR-C51798 · Issue 412382
Modified pzPopulateTrainingandTestDetails to resolve input error in test model
Resolved in Pega Version 8.1.2
After creating a text model, trying to update it resulted in errors. This was caused by the input bean for pzPopulateTrainingandTestDetails getting reset and causing a nullpointerexception while trying to load the spell checker because the taxonomy data was empty. This has been fixed by ensuring the input param object is created after setting the taxonomy data. A null check has also been added in the creation process of the input param object in pzPopulateTrainingandTestDetails.
SR-C70539 · Issue 412522
Open API passes 'true' for aUnlockOnCommit parameter to minimize pr_sys_locks table filesize
Resolved in Pega Version 8.1.2
The Archive/Purge Wizard was not removing the locks acquired during the execution from the pr_sys_locks table, resulting in locks remaining in the table for up to three days. This could potentially cause an enormous filesize and lead to other processes failing to acquire locks due to contention on the table. To resolve this, the system will pass 'true' for aUnlockOnCommit parameter on the open API so that the lock is released on commit of the deferredDelete on purged instances.
SR-C61477 · Issue 418266
HTML conversion added to email IVA
Resolved in Pega Version 8.1.4
When sending through emails that are in HTML format, HTML tags were visible within the Analysis of the email under Entities. These tags also potentially had an impact on topic detection, as the same email sent through in HTML would be classified under a different topic from one sent through as Plain Text.This issue originated because Email IVA received text as HTML while it expected plain text without HTML tags, and was traced to the use of an IMAP setting which sends only HTML to the listener. This has now been fixed such that If any HTML is received by email IVA, it will be converted to plain text via JSoup APIs in the service method as the first step.
SR-C64192 · Issue 415847
Activity Run allows autocomplete control for data transform
Resolved in Pega Version 8.1.4
An enhancement has been added to allow changing the control from Dropdown to Autocomplete when an activity is Run and the "apply data transform" checkbox is checked.
SR-C65841 · Issue 425807
Added handling for cases where IE causes a SAXParseException
Resolved in Pega Version 8.1.4
Numerous SAXParseException messages were seen in the log file, and the queryString showed the pyDeleteDocumentPg being referenced. This was traced to the method used by Internet Explorer to construct an HTTP request: IE sends the header and body of the request in separate TCP packets, but for an unknown reason in this case the body packet goes missing. To resolve this, a toggle has been introduced which will send the pyDeleteDocumentPg request as GET if pega.u.d.GET_REQUEST_DELETEDOCUMENT is set to true in userworkform. In a normal flow without this variable, the request will pass through the normal flow.
SR-C69729 · Issue 415717
External Entity Injection security improved
Resolved in Pega Version 8.1.4
Several updates have been made to improve security against External Entity Injection.