SR-133754 · Issue 203810
Enhanced handling for URLs with multiple Connect-REST parameters
Resolved in Pega Version 7.1.9
When there were two parameters present in a URL, the Connect-REST parsing was incorrect because only the outer braces were removed (the first brace from the first parameter and the second brace from the second parameter). To handle this correctly, the URL logic has been broken out into a separate activity. In addition, new information such as body and content type has been added to the results.
SR-133557 · Issue 202993
Schema URL' field in Parse XML rule now supports Global Resource Settings
Resolved in Pega Version 7.1.9
The 'Schema URL' field in Parse XML rule now supports Global Resource Settings (GRS), and the developer help documentation has been updated to reflect this.
SR-A1536 · Issue 205669
Fixed exception for read-only edit on data page
Resolved in Pega Version 7.1.9
Exceptions were being logged for a data page when edit mode was set as Read Only. This was caused by setIsReadonly in ClipboardPropertyImpl directly using the mPageValue which would be null for ref-type properties. The system has been updated to use getPageValue() instead of mPageValue directly.
SR-A3157 · Issue 207690
Corrected reference matching for relative pagegroup properties
Resolved in Pega Version 7.1.9
During page copy, the references in pagegroup property were becoming corrupted when given as a relative reference. Reference matching has been updated to resolve this.
SR-A3170 · Issue 213298
Stabilized encoding and decoding of Thai characters in imported CSV files
Resolved in Pega Version 7.1.9
While importing CSV files containing Thai characters, the methods of encoding and decoding were different and JVM differences could lead to output from the file being garbled. This has been updated to uniformly ensure the Thai characters will be properly recognized and converted.
SR-A3170 · Issue 212348
Stabilized encoding and decoding of Thai characters in imported CSV files
Resolved in Pega Version 7.1.9
While importing CSV files containing Thai characters, the methods of encoding and decoding were different and JVM differences could lead to output from the file being garbled. This has been updated to uniformly ensure the Thai characters will be properly recognized and converted.
SR-A3559 · Issue 208309
DataPage sourced Grids now able to launch local action
Resolved in Pega Version 7.1.9
An exception was being generated from SFA when attempting to copy a read-only data page of scope id requestor level during redirectAndRun. Copying of read-only data pages was not supported because it was expected the page would be loaded on a new thread when accessed, but for parameterized data pages this loading was not true because the parameters were missing. A read-only data page was also not copied because the lookup maps in the container would have to be populated. In order to support applications containing a grid sourced with DataPage and a section inside the grid contains an icon that launches a localAction, copying of read-only data pages is now allowed. During copy, if the page being copied is read-only the data page will get the parameter page for the instance from the container and do findPage() on new thread with this information. For other pages, it will continue to copy into new thread.
SR-A1199 · Issue 206250
Updated Email Listener mProtocol
Resolved in Pega Version 7.1.9
It was noticed that testing mail connectivity was working, but the Email listener was failing to start. This was happened when the "getStore" function on a Mail Session in the connection test passed a protocol argument that included [pop3, pop3s, imap, imaps]. EmailListener did not update the "mProtocol" variable to have the "s" for SSL, so it was only ever one of [pop3, imap]. To resolve this, the protocol name in Email Listener has been abstracted so that the 's' appears when telling java mail the protocol name.
SR-A1482 · Issue 204980
Enhancement added to support custom headers through REST
Resolved in Pega Version 7.1.9
The getObject(?pxHTTPServletRequest?) function was returning null when the authentication activity was run through the REST service. The retrieval of custom headers in the custom authentication activity was not previously supported as the object which stores the request map was null, but an enhancement has been added to make the servlet object available to HTTP/REST Service in the custom auth activity.
SR-A1484 · Issue 205662
Enhancements added to assist in migrating truststore information to new clusters
Resolved in Pega Version 7.1.9
An installation working on development both in the system and with set of trust for Connectors defined inside Pega that were specific to the development server and SOAP endpoint desired to have all of the trust configurations migrated along with the code base when setting up additional environments. Problems occurred during certificate validation that prevented the desired use, but no useful error information was generated. In order to support this function, enhancements have been added to produce an informative exception error in the checkServerTrusted method of CompositeX509TrustManagerwhen a certificate is not trusted, and to ensure that the signer certificates and then each of its intermediate certificates in the certification path are imported to Pega?s IBM WebSphere JVM?s truststore and all WebSphere JVMs participating in SSL communication on the PRPC cluster.