SR-121969 · Issue 184370
Deleted attachments flow error fixed
Resolved in Pega Version 7.1.8
If an attachment was added and submitted and then deleted from the attachment tab, the application then generated an error. This was caused by the system passing an invalid FromFrame after closing the modal dialog, and the code has been updated to use the originalFromFrame value when launching the flow.
SR-121980 · Issue 181118
Microsoft Internet Explorer 11 support added for auto-complete with multiple line properties in Report Definition
Resolved in Pega Version 7.1.8
If a property in a column of ReportDefinition that contains a carriage return (in order to input and display the value on two lines in the results) was then used as a source to Autocomplete control, then autocomplete control was not displaying the results. This was caused by a broken display with the Microsoft Internet Explorer 11 browser in compatibility mode, and code has been added to escape the new line character before converting the string to a JSON object so it will display as expected.
SR-121993 · Issue 181639
Fixed handling issues with substitutions enabled Parse XML rules
Resolved in Pega Version 7.1.8
Parse XML rules generated from an XML schema (xsd) saved in draft and "Not available" were generating Java errors when attempting to check out the rules and make them available. This happened when there were substitution elements and an embedded reference to the same element, and was caused by improper handling of the substitution helper method. This has been corrected.
SR-122025 · Issue 181153
Dropped rule added to DSM rules for SR properties
Resolved in Pega Version 7.1.8
A set of rules was inserted into the UI of Proposition LP and Strategy rules in DSM (Designer Studio) for use in retrieving a list of SR properties. This set was inadvertently missing the rule 'Activity Embed-Decision-SPContainer . pyRefreshSPList', and this has been added.
SR-122108 · Issue 182692
Fixed linking for work objects in CalendarViewGadget
Resolved in Pega Version 7.1.8
Using CalendarViewGadget to show calendar with work objects generated a Javascript popup with message "undefined" when clicking on the link of a work object. This "undefined" alert was added for situations where there is no handle passed to the openWorkByHandle desktop API, but there was an incorrect key in the hashtable of strings used to get the localized value. This has been fixed.
SR-122118 · Issue 180259
Improved condition handling for complex harnesses
Resolved in Pega Version 7.1.8
If a Review Harness had multiple embedded tab sections with includes, a read-only condition in the parent section was not being honored in a sub-section if the 'when' condition became false. This happened when a SectionIncludeInCell RUF passed an unquoted null value as a 3rd argument while invoking stream reference, and has been resolved.
SR-122118 · Issue 183909
Improved condition handling for complex harnesses
Resolved in Pega Version 7.1.8
If a Review Harness had multiple embedded tab sections with includes, a read-only condition in the parent section was not being honored in a sub-section if the 'when' condition became false. This happened when a SectionIncludeInCell RUF passed an unquoted null value as a 3rd argument while invoking stream reference, and has been resolved.
SR-122173 · Issue 184843
Expanded correspondence parameters for fax
Resolved in Pega Version 7.1.8
The parameters of Subject and AttachmentsToSend are passed to the CorrNew Activity to create correspondence for the actions Data-Corr-Email and Data-Corr-PhoneText. This has been expanded to also pass those parameters to Data-Corr-Fax.
SR-122176 · Issue 184992
Older button visibility conditions retained after upgrade
Resolved in Pega Version 7.1.8
After migration, older button controls set to visibility "ALWAYS" and when condition "canPerform" became visibility "WHEN" and when condition "canPerform". To resolve this, the logic for the activity Embed-Harness-Section!UpgradeOnOpen has been updated to check for "VISIBILITY" first before "visible when" to retain the proper settings.
SR-122191 · Issue 182679
Smoothed post-upgrade ApplicationSetup that uses previously generated LDAP configs
Resolved in Pega Version 7.1.8
An LDAP configuration created under a previous version of the software was generating an NPE after upgrading. This was traced to step2 of the ApplicationSetup activity where the system was expecting a page which was missing at that point due to the user not yet being fully identified. To avoid this, a step has been added to check if the page is available and avoid the NPE.