SR-124473 · Issue 186179
Added handling for unauthenticated asynchronous SOAP service
Resolved in Pega Version 7.1.8
After implementing changes to work around an error with SOAP authentication, the unauthenticated asynchronous SOAP service generated an error and failed to complete. This was due to the changes to the authentication process omitting the asynchronous mode case when a SOAP service that intended to not use authentication ends up calling a sub-activity that requires authentication. This use case is now covered.
SR-124580 · Issue 192241
Changes made to Save preferences option in SummaryView to retain filter values
Resolved in Pega Version 7.1.8
In the reports filter section, even after clicking on save preferences button the selected filter values were not retained the second time. In the SavePreferences activity, pyAdvicetext was set to pyLabel and caused the selected filter value to not be stored. To correct this, changes were made to the SavePreferences and getPreferences activities: In getPreferences, pyAppName is set to advicetext if its length is more than zero or set to pyAppname from primary page if not. Also, in the SavePreferences activity, pyAdvicetext is set to local.adviceText (previously it was set to pyLabel).
SR-125210 · Issue 189127
Customization corrected for RRHeader section of RD
Resolved in Pega Version 7.1.8
If the RRHeader section item was customized and renamed, opening Report Definition and clicking "Edit Report Title" did not produce the expected results even with the "Edit Report Title" command enabled. This was due to the RRHeader section being hard-coded; this is now loaded dynamically to allow for customization.
SR-125245 · Issue 187386
Search ability corrected for rule names containing spaces
Resolved in Pega Version 7.1.8
While a space was allowed in the rule name of a report category rule, searching for a rule name with a space generated the error "Unable to open instance Error: Can't find record". This was due to a missing JavaIdentifier validator for the "pyCategoryName" property in "Rule-Category" class, and this has been added.
SR-125751 · Issue 194311
Updated scroll bar generation for rule forms
Resolved in Pega Version 7.1.8
Calling WBOpen in a list view on click event allows a pop up to show. For rule or data instances which have forms bigger than the pop up size, no scrollbar was shown. This was caused by the previous ruleset regulating the scrollbar, RuleFormFrameset, being marked as deprecated but not removed from the function. To replace this rule, Window.open Attributes resizable and scrollbars have been set to true.
SR-125910 · Issue 194305
Corrected data population in report for exposed column
Resolved in Pega Version 7.1.8
Data was not being populated in a report for an exposed column when it was dragged and dropped from the data explorer of Report Editor. This was caused by the CreateColumnPage fieldName being hard-coded to Param.FieldName for embedded page properties, and has been changed to set FieldName conditionally.
SR-126335 · Issue 192177
Added support for custom mixed property types for listview filter
Resolved in Pega Version 7.1.8
When the out-of-the-box listview pySearchResultsWork was modified to add two columns with one property having Datetime control and the other having Date Control, the data was retrieved but the filter criteria was not working. This issue was specific to Date/Datetime control, and was traced to missing configurations for this scenario. Those have been added.
SR-126335 · Issue 194307
Added support for custom mixed property types for listview filter
Resolved in Pega Version 7.1.8
When the out-of-the-box listview pySearchResultsWork was modified to add two columns with one property having Datetime control and the other having Date Control, the data was retrieved but the filter criteria was not working. This issue was specific to Date/Datetime control, and was traced to missing configurations for this scenario. Those have been added.
SR-126719 · Issue 177348
Added fallback keyinfo handling
Resolved in Pega Version 7.1.8
When a SAML assertion response is received in the authentication activity, an error indicated the KeyInfo was missing in the signature. This was caused by a lack of redundancy in the keyinfo handling that caused an exception when keyinfo was not included in the SAML response. Support has now been added to check the certificate in the truststore where the certificate from IDP metadata would have been imported, and there is an added null check in the debug logs.
SR-126719 · Issue 178793
Added fallback keyinfo handling
Resolved in Pega Version 7.1.8
When a SAML assertion response is received in the authentication activity, an error indicated the KeyInfo was missing in the signature. This was caused by a lack of redundancy in the keyinfo handling that caused an exception when keyinfo was not included in the SAML response. Support has now been added to check the certificate in the truststore where the certificate from IDP metadata would have been imported, and there is an added null check in the debug logs.