SR-118604 · Issue 175098
Externally mapped class hierarchy given precedence over default mapping
Resolved in Pega Version 7.1.7
If a series of properties in the same class hierarchy were explicitly mapped to columns in the external database table and shared the names of some of the database columns, the Obj-save failed. Sporadically when the system restarted, the properties that share the names of the database columns were mapped to those columns. The code has been updated to ensure that external mapping takes precedence over PRPC's default property-column mapping
SR-118622 · Issue 175815
JMS-MDB Listener deployment descriptor updated for EJB 2.1
Resolved in Pega Version Pega Platform, Resolved in Pega Version 7.1.7
The generation of the MDB Deployment Descriptor has been modified to comply with EJB 2.1 specifications.
SR-118675 · Issue 172991
Corrected duplicated validation errors
Resolved in Pega Version 7.1.7
In some cases, validation error messages were being duplicated in the display. This was traced to code in the dynamic display being executed twice, and has been corrected.
SR-118692 · Issue 176658
Enhanced access to work object attachments
Resolved in Pega Version Pega Platform, Resolved in Pega Version 7.1.7
When a new work object is created and attachments are added in the advanced view, they are added to a list of all attachments that is sorted by the attachment type. A single-click on an attachment opened it normally, but a double-click opened the next attachment instead of the target attachment. Since this was not intuitive behavior, the system has been updated to accept both a single-click and a double-click to open the target file.
SR-118705 · Issue 174935
Corrected XML generation with element substitution
Resolved in Pega Version Pega Platform, Resolved in Pega Version 7.1.7
When an XSD schema with XML element substitution was imported using the Integration -> Connectors -> Create Other integration option and the option to generate substitution groups was chosen, the parse rule was generated properly, but when it was embedded within another element it was not outputting properly. Similarly, when parsing an embedded element that has type substitution, it only parsed the common parts and ignored elements of the specialized type. This was traced to incorrect mapping rule generation for element substitutions, and the rule generation has been enhanced to create the appropriate component rules.
SR-118722 · Issue 175625
Excessive length of filter window corrected
Resolved in Pega Version 7.1.7
In work object Audit window, the History table -> Description column filter window is appearing very long. This was caused by an inadvertent change to the listview function in conjunction with the Time column filter, and has been fixed.
SR-118725 · Issue 174420
Corrected focus for filter window using WAI
Resolved in Pega Version 7.1.7
With WAI enabled for work object - Audit window- History table - Time column, clicking on Filter window did not properly move the focus to the first element i.e., Add/Remove columns link. The getFirstInputElement API has been modified to fix the reported issue.
SR-118738 · Issue 172565
Handling corrected for drag and drop image attachments from Outlook
Resolved in Pega Version 7.1.7
If a document containing an image was added to a work object from Outlook via drag and drop, it would be corrupted when opened. This was caused by an encoding/decoding mismatch - the encoding differed depending on whether the file was first saved to the desktop or not, but the decoding did not take that into account. This has been corrected.
SR-118880 · Issue 172588
Change Password redirect loop fixed
Resolved in Pega Version 7.1.7
When URLEncryption is enabled along with Security Policies, redirection to the Change Password screen caused the browser to loop into an endless redirect (HTTP 302 loop). This was caused by Incorrect (un-obfuscated) data being used internally when obfuscation was enabled, and has been fixed.
SR-118884 · Issue 172536
Create Work correctly encodes Japanese characters
Resolved in Pega Version 7.1.7
When Japanese characters are passed as parameter to Create Work action, the newly created work item was registering cryptic characters instead of the expected Japanese characters. This was traced to a deprecated API, and has been corrected.