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.
SR-122197 · Issue 182685
Resolved Connect SOAP header mapping issue
Resolved in Pega Version 7.1.8
In the Connect SOAP rule, a Request tab configured with a Request Header field using XML Stream option was missing the PEGA tag in the generated SOAP header. This was caused by an error in the Axis stack and has been corrected to ensure all elements defined in the MapFrom XML rule are correctly generated.
SR-122213 · Issue 184299
Cache clearing corrected for muti-tenant environments
Resolved in Pega Version 7.1.8
A problem with the caching system in a multi-tenant environment led to a situation where a change in a rule in the shared layer did not invalidate that rule's entry in the tenants' rule cache. This was caused by the clearing of the cache not being fully propagated to all tenants, and the system has been updated to ensure the SMA clear cache fully clears all shared and tenant instances.
SR-122215 · Issue 180037
Resolved installation errors for DB2 Z/OS with WebSphere
Resolved in Pega Version 7.1.8
A problem was encountered while installing split schema on a DB2 z/OS system with WebSphere. This was caused by an erroneous system setting where the ports to the DB2 database were not open in this environment. While the Admin could correct the environment to open the ports and allow the application server node to connect to the DB2 database, this has been changed in the software to default to the correct settings.
SR-122230 · Issue 180223
Datetime properties format improved for backwards compatibility
Resolved in Pega Version 7.1.8
After upgrading, the search API was returning datetime properties in an incorrect format, causing a page error that was sometimes visible to an end user. The error only occurred if additional processing was happening in that page that caused the validation dictionary to launch. The root cause of this problem was a backwards compatibility defect related to Elastic Search, and it has been corrected.