SR-A15627 · Issue 230719
JBoss shutdown errors resolved
Resolved in Pega Version 7.2.2
During a controlled shutdown, database-level exceptions occurred and a hard reset was required. This was traced to the container not correctly detecting dependecies, leading to JBoss prematurely terminating JMS and JDBC resources that were needed during Pega shutdown. Pega applications on JBoss now contain information to ensure the application server understands that this resource has dependent processes and the lookup-name (with the JBoss specific namespace) is maintained correctly to make sure it isn't cleaned up prematurely. The web.xml file has also been updated to include a lookup-name in the entry for ResourceRef_1 to handle cases where the datasources are injected using CLI scripts after JBoss is started and before Pega is deployed.
SR-A88329 · Issue 258343
JBoss shutdown errors resolved
Resolved in Pega Version 7.2.2
During a controlled shutdown, database-level exceptions occurred and a hard reset was required. This was traced to the container not correctly detecting dependencies, leading to JBoss prematurely terminating JMS and JDBC resources that were needed during Pega shutdown. Pega applications on JBoss now contain information to ensure the application server understands that this resource has dependent processes and the lookup-name (with the JBoss specific namespace) is maintained correctly to make sure it isn't cleaned up prematurely. The web.xml file has also been updated to include a lookup-name in the entry for ResourceRef_1 to handle cases where the datasources are injected using CLI scripts after JBoss is started and before Pega is deployed.
SR-A15627 · Issue 232738
JBoss shutdown errors resolved
Resolved in Pega Version 7.2.2
During a controlled shutdown, database-level exceptions occurred and a hard reset was required. This was traced to the container not correctly detecting dependencies, leading to JBoss prematurely terminating JMS and JDBC resources that were needed during Pega shutdown. Pega applications on JBoss now contain information to ensure the application server understands that this resource has dependent processes and the lookup-name (with the JBoss specific namespace) is maintained correctly to make sure it isn't cleaned up prematurely. The web.xml file has also been updated to include a lookup-name in the entry for ResourceRef_1 to handle cases where the datasources are injected using CLI scripts after JBoss is started and before Pega is deployed.
SR-A38580 · Issue 252790
Improved Extended Interaction History cache handling for column removal
Resolved in Pega Version 7.2.2
The Interaction History Component was generating an error when IH was extended with additional attributes in the transform rule:Data-Decision-IH-Configuration -pyInteractionHistoryConfiguration and then deleted at a later stage. Once the new property was mapped and the IHFact table was altered to add the new column, the Interaction History component in the strategy which retrieves the IH data was not able to handle the removal of that column from the IHFact table or from the data transform due to a static marker in the rule not being updated with the deletion. The cache function has been modified to correctly reflect the deletion of the column.
INC-198725 · Issue 707484
Elasticsearch will split queries to avoid URL length limits
Resolved in Pega Version 8.7.2
Elastic Search Functionality was not working and showed the status as Offline. Investigation showed that when an external Elasticsearch setup had an index prefix length = 200 and a large number of dedicated indexes, the error "too_long_frame_exception, reason: An HTTP line is larger than 4096 bytes" was generated. In this case, the system was working with approximately 87 dedicated indexes and the name for each of them was sent over the URL, resulting in this error message. This has been resolved by updating the system to split queries so as to not exceed the HTTP line limit in Elasticsearch.
INC-216358 · Issue 712229
Auto Complete working in Mobile Browser configuration
Resolved in Pega Version 8.7.2
Autocomplete was not working in the mobile browser when logged in as a user and configured with display mode:"in-a-table" and "display as full screen in mobile" disabled. Autocomplete results will always display in List mode in the mobile browser, but with the configuration "in a table" selected and "Display results full screen on phone" unchecked, pzGetACData (which gets called for List mode) was not registered and returned a 403 response. To handle this, the conditions file ActionAssembly.java has been removed so pzGetACData will always be registered.
SR-A67716 · Issue 251384
Updated ruleset determination for saving copied reports
Resolved in Pega Version 7.2.2
When a new report was made from a copy, it was not properly assigned to the ruleset it should be saved in (the "design time" ruleset configured on the operators Access Group). Instead, it was residing in the same ruleset as the template report definitions (Pega-Reporting), causing property validations to fail if they were in the subset of rulesets which were in the design time ruleset's stack but not in Pega-Reporting until the report was saved successfully once. This has been fixed by adding a step to Rule-Obj-Report-Definition!pxShowReport that sets the ruleset name and version of a new report to match the Access Group's configured design time ruleset.
SR-A88892 · Issue 266454
Restored nested sections show repeating grid header
Resolved in Pega Version 7.2.2
In a section that has repeating grids configured, rule check-out and check-in caused the repeat grid headers and cells to disappear in Designer Studio. Analysis showed that when a rule was deleted from a section with nested layouts, only the properties which had values were committed to the database. On restoring the rule, only committed properties were re-created on the section XML, leaving the XML incomplete and generating an error and layout rendering failure. To fix this, the pzpega_ud_gridlayout_structure JS has been updated to handle the non-existence of empty nodes and initialize them.
SR-A100693 · Issue 270076
Checkboxes retain context in Repeating Dynamic Layouts
Resolved in Pega Version 7.2.2
Issues were found with properties in Repeating Dynamic Layouts that lose their context based on user interaction and out-of-the-box configuration, most notably with Checkboxes. On checkboxes the action does not need to trigger a refresh, yet the UI for the checkbox HTML is was refreshed even when it should not be. In order to fix this issue, changes have been made to the initiatePost() method in "pzpega_ui_events" file to ensure the "RepeatDynamicIndex" param is sent to the server and generates the ID on the checkbox as expected. Note: This fix will work only for checkboxes in RDL only and only for "post value" action.
SR-A100725 · Issue 270058
Checkboxes retain context in Repeating Dynamic Layouts
Resolved in Pega Version 7.2.2
Issues were found with properties in Repeating Dynamic Layouts that lose their context based on user interaction and out-of-the-box configuration, most notably with Checkboxes. On checkboxes the action does not need to trigger a refresh, yet the UI for the checkbox HTML is was refreshed even when it should not be. In order to fix this issue, changes have been made to the initiatePost() method in "pzpega_ui_events" file to ensure the "RepeatDynamicIndex" param is sent to the server and generates the ID on the checkbox as expected. Note: This fix will work only for checkboxes in RDL only and only for "post value" action.