SR-114670 · Issue 166258
JMS MDB listener updated to support JMS 1.1
Resolved in Pega Version 7.1.7
A compatibility issue with SonicMQ generated the error "Caused by: javax.jms.JMSException: [JMSPool:169823]Failure occurred on createQueueConnection" during initialization of the response connection. To remedy this, PRPC has been updated to support JMS 1.1.
SR-114670 · Issue 169790
JMS MDB listener updated to support JMS 1.1
Resolved in Pega Version 7.1.7
A compatibility issue with SonicMQ generated the error "Caused by: javax.jms.JMSException: [JMSPool:169823]Failure occurred on createQueueConnection" during initialization of the response connection. To remedy this, PRPC has been updated to support JMS 1.1.
SR-114917 · Issue 166117
Alignment issues with IAC resolved
Resolved in Pega Version 7.1.7
When a dynamic layout of stacked style was used in conjunction with IAC, resizing the window caused the elements to not be properly aligned. CSS issues in the HTML handling of overflow properties have been corrected with the resizing harnesses.
SR-118050 · Issue 169612
Alignment issues with IAC resolved
Resolved in Pega Version 7.1.7
When a dynamic layout of stacked style was used in conjunction with IAC, resizing the window caused the elements to not be properly aligned. CSS issues in the HTML handling of overflow properties have been corrected with the resizing harnesses.
SR-115104 · Issue 165556
IAC functionality enhanced for secure environments
Resolved in Pega Version 7.1.7
In order to ensure IAC functionality in a secure environment, the following updates were made: HTTPOnly support has been enabled for prGatewaySESSIONID cookies; encryption and obfuscation have been set up for web nodes; added a check for login-config.xml to add default-users.properties and default-roles.properties to the other application-policy.
SR-115392 · Issue 164192
Added customization for PDF page numbers
Resolved in Pega Version 7.1.7
Previously, it was not possible to designate the initial page number in the PDF generated by HTMLToPDF activity. Two parameters have been added to allow for greater customization: "header" activates page number support in the document header, and "startPage" is used to set the initial page number for the document. The "startPage" parameter can be used for both the header and footer.
SR-115492 · Issue 169327
Obj-save and commit working for fully-exposed classes
Resolved in Pega Version 7.1.7
If an exposed class was implemented by creating an underlying database table, trying to perform an Obj-Save (or commit) on an exposed class generated errors regarding some properties not having corresponding database columns. This happened when one of the Page names was also the beginning part of a name of one of the simple types, and was caused by a flaw in the logic used to determine if the property is an embedded reference. This has been corrected.
SR-116101 · Issue 166813
Improved handling of multipart data input
Resolved in Pega Version 7.1.7
HTTP Service uses a Parse XML to map message data, but issues were found with the handling of the "multipart/form-data" format. For example, not all of the parameters were made available in the Parameter page: while the multipart data was parsed, causing the name value pair to not be properly set. To better handle multipart data, changes have been made to the Fileupload method of the HttpUtilities java file.
SR-114595 · Issue 164792
Improved handling of multipart data input
Resolved in Pega Version 7.1.7
HTTP Service uses a Parse XML to map message data, but issues were found with the handling of the "multipart/form-data" format. For example, not all of the parameters were made available in the Parameter page: while the multipart data was parsed, causing the name value pair to not be properly set. To better handle multipart data, changes have been made to the Fileupload method of the HttpUtilities java file.
SR-116286 · Issue 168017
Corrected a race condition with Lock Manager
Resolved in Pega Version 7.1.7
In some cases, attempting to open an existing Work Object that was assigned to a workbasket with a SLA on it generated the error "The flow this assignment corresponds to has been removed". This was due to a race condition with the Lock Manager where two threads attempted to update an instance at the same time, and has been fixed.