SR-124245 · Issue 188290
Clarified handling of unlocked work objects in multinode environments
Resolved in Pega Version 7.1.8
Release lock was not working correctly on a multinode environment. When trying to release the lock from same operator different requestor from different nodes, the error "Unable to unlock this work object" was generated. In a multinode environment, system pulse takes time to update the cache across the nodes, hence the option is not effective immediately. Messaging has been updated to reflect this delay. Once System pulse executes then other requestor will be able to work on this item.
SR-124246 · Issue 185967
Added NPE check for empty indexed pyID properties
Resolved in Pega Version 7.1.8
Certain searches resulted in a null pointer exception that appeared to be occurring in the FTSContentExecutor class. This issue was caused by a null (empty) pyID property in the indexed instance and has been corrected by inserting handling for any NPE generated in this circumstance.
SR-124269 · Issue 185473
Smoothed mode derivation for properties on adopted pages
Resolved in Pega Version 7.1.8
In certain situations, adopting a page onto a Light weight list row might fail if the adopted page had some dummy undefined page properties. To resolve this, while adopting properties from adopted page, the system will derive the mode from properties on adopted page if they are not defined.
SR-124290 · Issue 185890
Added check for error in LDAP logins
Resolved in Pega Version 7.1.8
When a user logged in as external authenticated user over LDAP, a null pointer exception was seen. This exception was generated by the ApplicationSetup activity because the system was missing a page due to the user not being fully identified at that point. To fix this, a null check has been inserted for this condition.
SR-124298 · Issue 186402
SQL Merge use clarified for custom Tomcat installations
Resolved in Pega Version 7.1.8
Logic was added to ML7 to disable the SQL Merge command in environments that do not support it, but this was failing with an exception trying to parse the Tomcat name/version string if the installation was using a custom version of Tomcat and the string was not in the expected format. To handle this, the logic has been updated to to handle a custom Tomcat Name/Version string that may or may not contain version information. However, please note the following important information: The system will disable Merge if the out-of-the-box Tomcat version is detected where version If the system is using a custom Tomcat instance
SR-124313 · Issue 190024
FCM remote case type function restored
Resolved in Pega Version 7.1.8
FCM (Federated Case Management) has a button to discover remote case type, but attempting to use it out-of-the-box generated the error "Remote System is not available. Please check the settings". This was due to a lack of authentication in the Service HTTP rules CaseManagement, and the authentication requirement has been removed.
SR-124382 · Issue 187227
Corrected image resize for RTE
Resolved in Pega Version 7.1.8
In some cases, it was not possible to resize an image in RTE. This was traced to the image plugin setting the height and width for auto resize, and has been changed so the setup and commit function in ckeditor_extras do not set dimensions for auto resize and retain the width and height if specified.
SR-124382 · Issue 185471
Corrected image resize for RTE
Resolved in Pega Version 7.1.8
In some cases, it was not possible to resize an image in RTE. This was traced to the image plugin setting the height and width for auto resize, and has been changed so the setup and commit function in ckeditor_extras do not set dimensions for auto resize and retain the width and height if specified.
SR-124384 · Issue 185899
Stream XML generation and runtime handling enhanced for optional nodes in schema
Resolved in Pega Version 7.1.8
When a stream rule was executed using connect-SOAP and blank data was passed from the UI, a tag corresponding to the XML element marked as optional was being generated. This resulted in those optional properties being unexpectedly created in source systems. To change this, the generation of the Stream XML rule has been enhanced such that at runtime it ignores optional nodes/attributes mapped to properties which do not exist or which have an empty value. NOTE: this new behavior in Stream XML rule generation is effective only with the below DSS configuration (to avoid backward compatibility issues ): Owning Ruleset : Pega-IntegrationEngine Purpose : StreamXML/DetectEmptyProperties Value : true
SR-124385 · Issue 187273
Clicking checkboxes smoothed for Bulk Processing
Resolved in Pega Version 7.1.8
While performing Bulk Processing, if the checkboxes used to select items for processing were marked in rapid succession, not all of the selected items were processed by the bulk action. This was due to the timing of the refresh on the boxes, and this has been adjusted so all boxes are refreshed by a refresh list instead of post value process.