SR-127799 · Issue 192294
Included CMIS library updated
Resolved in Pega Version 7.1.8
Using Connect-CMIS Rule form, attempting to get a list of Repositories from a CMIS Server that allows Web service binding with Basic Authentication was failing with 401 - Unauthorized error. The getRepository operation succeeded when using SOAPUI or Apache Chemistry CMIS client Workbench. This was a defect with the particular CMIS library version included with Pega 7.1.7, and has been corrected by updating to a revised version.
SR-121429 · Issue 187948
Encoded handling for Chinese characters in SOAP
Resolved in Pega Version 7.1.8
Signature verification failed when a SOAP message contained multibyte Chinese characters. This was due to the engine passing platform specific request bytes instead of sending UTF bytes to the third party metro webservices code when signature is enabled. The JAR encoding has been modified to use the style it gets in the request in order to bypass third party platform decisions.
SR-119648 · Issue 177559
JavaMAIL version updated for GMail compatibility
Resolved in Pega Version 7.1.8
A third-party product integrated with PRPC was causing mail and attachments to not appear properly when using Gmail due to an incompatibility with Gmail's interpretation of IMAP. To correct this, the provided JavaMAIL version has been updated from 1.4.1 to 1.5.2.
SR-129955 · Issue 199160
Extraneous 'save changes' popup removed from PDF viewer
Resolved in Pega Version 7.1.8
A popup asking "Do you want to save changes to pdf before closing" was appearing when closing an unmodified PDF generated from PRPC using the concatenateEforms feature. This was caused by an unneeded appearance setting, which has been removed.
SR-128970 · Issue 194366
Added logic for base class missing a hyphen
Resolved in Pega Version 7.1.8
When using connector and Metadata Wizard, if a base class was provided that doesn't end with '-', then the generated class name were appended into the base class name. To correct this, logic has been added to append a hyphen to baseclass if one is not present.
INC-182572 · Issue 663557
Support added for multiple host proxy architecture
Resolved in Pega Version 8.7
When using an architecture where certain types of users were sent through multiple proxy servers to get the Pega Cloud instance, an exception was generated at the point of accessing the environment. This was traced to the use of Apache 2.4 with mod_proxy. As the request passed through each proxy, the x-forwarded-host header had values appended to it by mod_proxy which resulted in the error "com.pega.pegarules.pub.context.PRSecurityException: Multiple host names in header X-forwarded-Host". This has been resolved by updating the code to support using a multiple host proxy configuration.
INC-163985 · Issue 635146
Class mapped to CustomerData is incrementally indexed as expected
Resolved in Pega Version 8.5.4
When using a class which mapped to customerdata, instances that were added/updated were not automatically getting indexed unless a full reindex was performed. If the class mapping was changed from customerdata to pegadata then the incremental indexing was done. To resolve this, the UpdateProcessor class that resolves CustomerData to the correct database name has been updated to use PegaData. ConfigurationMapImpl contains the resolution mapping and a call is made to ConfigurationMapImpl to retrieve the correct database name.
INC-169116 · Issue 654256
Correct time zone chosen for fr_Fr appointment functionq
Resolved in Pega Version 8.7
When using the "fr_Fr" location and and "Europe/Paris" time zone for appointments, a null pointer exception was seen related to the function getStartOrEndDateTime. Investigation showed that the incorrect time zone was being picked from the fr_FR.xml file when parsing the date. To resolve this, 4 letter time zone codes have been moved above the 3 letter time zone codes.
INC-194269 · Issue 681046
Added handling for Create Source and Target properties of Date
Resolved in Pega Version 8.7
A report definition was not displaying results after update, and a stack overflow was reported. This was a missed use case for Create Source and Target properties of Date, and has been resolved by adding a boolean flag to avoid autochain during validations when data type is Date.
INC-172546 · Issue 652877
Resolved classcast exception with assembled HTML controls
Resolved in Pega Version 8.5.4
A classcast exception was being generated on login. Investigation showed the Static Assembler was unexpectedly using a different Assembler to assemble the Html control rule. Standard behavior is that StreamBuilderAssembler assembles controls of type StreamBuilder and ControlAssemblerForVTable assembles controls of type ControlBuilder. In this case, static assembly for HTML controls using VTable was performed using StreamBuilderAssembler, causing a classcast exception when using VTable because the instance of the generated.html class was incorrectly inheriting from StreamBuilder (the parent class of ControlBuilder) instead of ControlBuilder which is the specified interface in the generated.html Java code. This has been resolved by updating the system to skip rules of type 'Rule-HTML-Property'(control) during Static Assembly.