INC-145535 · Issue 600785
Corrected layout group overlapping content
Resolved in Pega Version 8.5.2
When an editable Table with Master Detail Edit has a section that contains a Layout group (Tab) inside the Master Detail Flow Action, if there are more layout group headings than that can be contained in the screen, a left and right arrow are displayed to toggle between headings in the layout group heading bar. However, timing issues sometimes caused the contents of the layout group to overlap on top of the content below the layout group and the screen was freezing with a loading icon. This was traced to console errors, and has been resolved by adding an 'undefined' check to prevent those errors.
SR-D59106 · Issue 526917
File Listener null-pointer exception resolved with context check
Resolved in Pega Version 8.3.2
A service file rule associated with a file listener was encountering a Null Pointer Exception. Investigation showed that the system successfully processed the first record in the service file, then it encountered the null-pointer exception indicating that the listener state was null. This was traced to functionality introduced in an earlier version to ensure File Listeners are succinctly shut down when a Cloud Node is moved to queiscing. As part of that work, the Rule-Service-File was linked to ListenerStateManager and did not work in a scenario where the rule could be executed outside of that context. This has been resolved by adding a check for context before directing the activity.
SR-D71041 · Issue 537894
Default compiler pool size increased
Resolved in Pega Version 8.3.2
An issue was seen where the nodes were continuously terminating and Stream service was not started. Error messages indicated a "WARN - Long running request detected for requestor", and that tasks were waiting for the generic object pool. Analysis showed that it was possible for a deadlock to form during the startup of the system or during the first few rule executions and compilations when there were more than five rules trying to compile. Once the variable LibraryMetadata.TypeEnvironment.resolver (ClassLoader) is initialized, the problem would resolve. To prevent the deadlock, the default compiler pool size has been increased from 5 to 10.
SR-D75003 · Issue 538338
File Listener null-pointer exception resolved with context check
Resolved in Pega Version 8.3.2
A service file rule associated with a file listener was encountering a Null Pointer Exception. Investigation showed that the system successfully processed the first record in the service file, then it encountered the null-pointer exception indicating that the listener state was null. This was traced to functionality introduced in an earlier version to ensure File Listeners are succinctly shut down when a Cloud Node is moved to queiscing. As part of that work, the Rule-Service-File was linked to ListenerStateManager and did not work in a scenario where the rule could be executed outside of that context. This has been resolved by adding a check for context before directing the activity.
INC-173436 · Issue 648821
Performance improvement for Application Save: Node Level Data Pages
Resolved in Pega Version 8.7
As part of new functionality introduced in 8.3, data types defined in the application record will be turned into data objects on Application save. As part of this process node level pages are invalidated and reloaded and there is an explicit commit that marks the Application record as dirty and sends any calls for the application record to the database for fresh records. In a multi-node environment, the number of queries to get the application record being saved became exponentially higher and performance impacts were seen. This has been resolved by updating the system to skip eager loading of the data page definition when an access rule or application definition is saved.
INC-192979 · Issue 678361
Performance improvement for Application Save: Node Level Data Pages
Resolved in Pega Version 8.7
As part of new functionality introduced in 8.3, data types defined in the application record will be turned into data objects on Application save. As part of this process node level pages are invalidated and reloaded and there is an explicit commit that marks the Application record as dirty and sends any calls for the application record to the database for fresh records. In a multi-node environment, the number of queries to get the application record being saved became exponentially higher and performance impacts were seen. This has been resolved by updating the system to skip eager loading of the data page definition when an access rule or application definition is saved.
INC-190708 · Issue 688134
Save works on Ajax container without Dynamic container
Resolved in Pega Version 8.6.3
After opening a work object and making changes to a required field, pressing the save button did not give any visual indication that the save was performed. Hitting cancel generated a dirty pop up saying changes will be discarded, indicating no save was done. When an Ajax container is configured without a Dynamic Container, all the content is rendered inside a fieldset tag instead of a form tag. While performing the save, the API was looking for the form element in the document and could not find any, and the save failed. This has been resolved by updating the submitWhenFail() API to handle both fieldset and form elements in the dom.
SR-B76989 · Issue 327639
Informational text added to "No suitable driver" error message
Resolved in Pega Version 7.4
After configuring Pega to connect to an external database using Data-Admin-DB-Name with a JDBC URL configuration that had the appropriate jar for the driver in the application server classpath, unexpected behaviors were seen. The first time the Test Connectivity button was clicked, a "No suitable driver found" error appeared. The second click ran the test as expected. This confusion was related to an undocumented enhancement: because adding a new database JDBC driver in Pega may require configuration to get the driver class loaded to the classpath, the 'No suitable driver' exception was enhanced with the configuration required to get the JDBC driver loaded at the next restart. In order to avoid confusion, informational text will now appear as part of the "No suitable driver" error message to explain this.
INC-185266 · Issue 676581
Index table correctly populates after migration
Resolved in Pega Version 8.7
After creating a product file with work instances, only some records were populating in the index-workpartyuri class through index rule. Investigation showed that if the IDs specified for the Work Range started with the same digits as were seen after the case prefix (e.g. W-1, W-1000, or W-22, W-2201) then only the indexes for cases that start with W-1 or W-22 were included in the export. This was traced to a step in AddPartyIndexWhenCondition where the EstimatedWorkPrefix local variable was calculated: the java step extracted anything that was the same from the start of the To and From range without taking into account the possibility that some digit characters after the "-" could be the same. To improve the accuracy of the prefix estimation, "-\d" will be used to make an educated guess.
INC-138348 · Issue 599770
Added parameter skipPropertyEvaluation to handle CSS in email HTML
Resolved in Pega Version 8.5.2
While sending an email with custom HTML appended to the email body, a "+" sign in the body was causing the correspondence generation to fail. Investigation showed that if there were CSS classes with braces in the message body, the braces were being removed and replaced via "+" symbol in step 21 of CorrCreate activity. To resolve this, a new Boolean parameter skipPropertyEvaluation has been added in the CorrCreate activity to handle the decision to either evaluate the logic or not, and the pre-requisite will be to resolve all the property references before calling this activity so custom CSS braces { } will be honored when the message body is sent.