SR-A22183 · Issue 249190
Elements given correct default value in XML
Resolved in Pega Version 7.2.2
An issue was found where blank tags were being created for node elements given a default value in the XML Stream rule. Analysis showed that when the optional element in the XML Stream rule was set with "" and had a default value, the "StreamXML/DetectEmptyProperties" empty string was getting displayed in the output XML instead of default value. This has been fixed.
SR-A76148 · Issue 251342
Documentation updated for running BIX from the command line
Resolved in Pega Version 7.2.2
When attempting to run BIX from the command line within a Linux environment, an error is thrown: Error: Could not find or load main class com.pega.pegarules.data.internal.access.ExtractImpl This was a local error in the setup of the bix.sh script, and the BIX documentation has been updated to clarify the requirements.
SR-A77307 · Issue 260263
Null check added for selectNodes extraction
Resolved in Pega Version 7.2.2
When an assignment contained a field with custom control that included 'ClientValidation' with 'Activate input formatting' selected for this field, attempting to change the field or submit the assignment generated the JS error 'Unable to get property 'selectNodes' of undefined or null reference'. This has been resolved by adding a null check to the selectNodes extraction function to handle empty values for the returned object.
SR-A77307 · Issue 260728
Null check added for selectNodes extraction
Resolved in Pega Version 7.2.2
When an assignment contained a field with custom control that included 'ClientValidation' with 'Activate input formatting' selected for this field, attempting to change the field or submit the assignment generated the JS error 'Unable to get property 'selectNodes' of undefined or null reference'. This has been resolved by adding a null check to the selectNodes extraction function to handle empty values for the returned object.
INC-144917 · Issue 598201
Healthcheck will only initialize after successful node startup
Resolved in Pega Version 8.4.4
Nodes were not starting up, but because the Healthcheck service was initialized even though the node was not started properly, errors related to that were overriding the actual exception causing the node startup to fail and it was not possible to diagnose the startup issue. To resolve this, an update has been made that will ensure the Healthcheck service is only initialized when the node is initialized successfully.
SR-D63668 · Issue 525479
Access Control Policy updated to handle NotEqual with valuelist
Resolved in Pega Version 8.1.8
When editing the Access Control Policy Condition rule in Designer Studio and setting condition to 'is not equal', comparing it to a list generated the error "function not found". The same configuration worked as expected for the 'is equal' condition. This has been resolved by updating policycondition to handle a not equal scenario combined with a valueList property.
INC-208516 · Issue 705098
Patchdate values made unique
Resolved in Pega Version 8.8
The hotfix manager was incorrectly indicating that a previous hotfix was not installed or was partially installed and should be reinstated. This scenario was created during security updates where the missing/incomplete hotfix had been deliberately deleted from the database, and has been resolved by adding an update which will force patchdate to be unique when adding duplicate code resources during tests.
SR-A96425 · Issue 262660
Cassandra enhancements
Resolved in Pega Version 7.2.2
The following enhancements and updates have been made to Cassandra usage: all independent services initialize in parallel, nodes will not start (Add node) while there is another node leaving, auto_snapshot is disabled on truncate, nodes will join the DDS cluster properly when booted together, and a check has been added to ensure Cassandra is up before adding the node in DDS.
SR-B339 · Issue 270442
Enhancement added to place icons on tabs with client-side errors
Resolved in Pega Version 7.2.2
When client-side errors occurred on inactive tabs in a tabbed screenflow, there was no indication (for example an alert icon) of which tab had an error, only the pop-up error message "Please correct flagged fields before submitting the form!". An enhancement has been added to place an error icon on the tabs where the client-side errors have occurred.
INC-150407 · Issue 605842
Validation error messages correctly cleared in nested markup
Resolved in Pega Version 8.4.4
A UI Freeze issue was seen whenever mandatory input was missed and the form was submitted. Continuing was possible after browser refresh, but a new Next>> button appeared. This was an unintended side effect of work done to correctly clear validation messages when areas had captions, and has been resolved by modifying that work so it performs as expected on nested markup.