SR-C77625 · Issue 414766
Improvements made for the stability and reliability of the stream tier
Resolved in Pega Version 8.1.4
Several enhancements and fixes have been made to improve the stability and reliability of the stream tier with a focus on rolling restart. Issue 410567: When a stream node shuts down, it takes up to a minute for all client nodes to recognize the event and failover to other nodes due to large default timeouts. Timeouts have now been reduced to allow nodes to failover much earlier. Issue 413375: When a stream node shuts down, other stream nodes are notified and attempt to discover the new cluster topology. Since the cluster is still in flux, this operation may take a long time blocking all producers until a new topology is determined. This procedure has been changed to be less heavy and make the discovery only if required. Issue 401326: Kafka (running as a separate process as part of the Stream services) generates log files, but does not use log rotation with a maximum amount of log files. This means that the log files will eventually fill up the disk, leading to failures of the service and PRPC instance running on the same disk. To resolve this, the system will now limit number of generated log files to prevent high disk usage by using the parameters of file size = 2 MB and a max nr of size = 10. Issue 410280: A large number of "Processing override for entityPath" entries were seen in the Kafka logs. This has been addressed by ensuring message.timestamp.difference.max.ms is set to equal to retention.ms. In addition, the system will properly compare the Kafka Configuration created for the entire topic and the configuration retrieved for Partitions so the configuration is not unnecessarily updated. Issue 414765: During stream node restart, decision hub nodes may block for 15-30 seconds when writing to a stream data under certain conditions. This can cause high response times for a small period. This has been addressed by updating stream dataset logic to handle stream tier restarts properly and not cause response time degradation. Issue 401093: HttpMessageDecoder was throwing an exception regarding “TooLongFrameException” causing a 502 on HTTP stream tier requests going over 8192. The default max header size used by stream data set REST service was 8KB. In this particular case, the HTTP header contains a lot of cookies and other meta-info and exceeds 8KB. To resolve this, the default max header size has been increased to 16KB. A new prconfig setting to control max header size has also been introduced.
SR-C79482 · Issue 424537
DSS added to allow custom timeout for BIX query
Resolved in Pega Version 8.1.4
The BIX query to retrieve the blob column was taking up to 60 seconds for large volume, causing timeouts. Previously, the extract defaulted to using repost pzSample which is internal/final and has a default timeout of 30 seconds. In order to avoid timeouts, the new DSS "BIX/selectQueryTimeout" has been added to allow setting a custom value. Further refinements will be made for multi-tenant environments in a future release.
SR-C79851 · Issue 430385
Filter logic updated for Warning Summary guardrail report
Resolved in Pega Version 8.1.4
After scheduling a Guardrail report for Warning Summary, the warning summary reports received in email were blank irrespective of the filter criteria. The logic filters have been modified to resolve this issue.
SR-C80129 · Issue 421417
Data type search adjusted to handle text query
Resolved in Pega Version 8.1.4
After creating a data type and adding a class join and then delegating the data type to a user, the data type search bar in the configuration tab was not working. This was traced to the decision search filter using "=", which did not handle a text query. This has now been changed to use "Contains" to resolve this issue.
SR-C80948 · Issue 421766
ProfileLink control updated to resolve opening issue
Resolved in Pega Version 8.1.4
The profile was not opening when the Operator Profile link was clicked. This was traced to certain functions having been moved to javascript files that were not included by default in the ProfileLink control. To correct this, the control has been modified to include the needed javascript files and the appropriate references have been updated to match.
SR-C81410 · Issue 422138
Radiobutton aria-label enhanced to retrieve localized field value
Resolved in Pega Version 8.1.4
Localization code has been added to the pzpega_ui_template_radiogroup file to support using RadioButton aria-labels for Field value.
SR-C81855 · Issue 421404
Check added to format simplified Chinese date generation to match system expectations
Resolved in Pega Version 8.1.4
When the browser language was set to Chinese (simplified) and a template was used for an application, an invalid date exception was generated. This was caused by a difference in handling between the moment.js function used to format the datetime, and Pega. The moment javascript formats dates with the below 6 meridiem for Chinese locales (zh-cn, zh-hk, zh-tw):凌晨 - Early morning 早上 - morning 上午 - morning (AM) 中午 - noon 下午 - in the afternoon (PM) 晚上 - at night But the Pega server only accepts two standard meridiem i.e. 上午 - morning (AM) and 下午 - in the afternoon (PM). Due to this, using an unsupported setting resulted in an error. To resolve this, a check has been added for the Chinese locales (zh-cn, zh-hk, zh-tw) that will adjust the non-supported formats to be either 上午 - morning (AM) or 下午 - in the afternoon (PM).
SR-C82254 · Issue 421057
Support added for saving draft survey flows in production level 5
Resolved in Pega Version 8.1.4
With production level set to 5, creation of a survey was generating two errors: in UI, "Default survey flow creation failed", and in trace, "Update record failed: .pyDraftModeON". Because in most cases Survey authoring would be done in a system with a lower production level where users would not see any issues, the code did not include support for saving draft mode flows when the system was set to production level 5. This ability has now been added to support this use.
SR-C82549 · Issue 422848
Check added to getRuleNameFromInsKey to clip version name from rulseset name in the dataflow
Resolved in Pega Version 8.1.4
After changes were pushed to the datasets, dataflows were failing on a DT2 environment with an error related to rule resolution and a failure to find a specific property. The dataflows did not fail on a DT1 environment. Investigation showed that if the ruleset name was empty and the ins key was used to get the rulesetname, a mismatch occurred with the returned value due to the version information being included in the name. To resolve this, when a rule name is retrieved by getRuleNameFromInsKey, the system will check if aObjClass is Rule-RuleSet-Version. If so, the version part will be trimmed.
SR-C83050 · Issue 422978
IE width calculation fixed for imported built-on with dymanic layout
Resolved in Pega Version 8.1.4
After upgrade, the Built On input for the application screen in Designer Studio was not rendering in the Microsoft Internet Explorer 11 browser if dynamic layout was used. This was caused by a browser-specific issue with width calculation for pzDefinition, and code has been added to handle this issue.