SR-126775 · Issue 189860
Resolved HTMLtoPDF font load error
Resolved in Pega Version 7.1.8
When using a Fonts directory during HTMLToPDF conversion, the StaticContent folder resolved to an incorrect properties file and generated an error that appeared to indicate the fonts had not correctly loaded even when they had indeed loaded. The error was traced to the function used to open the Static Content folder with the direct file handle, and this has been updated to resolve correctly.
SR-127932 · Issue 194420
Paragraph rules library modified for JSP tags
Resolved in Pega Version 7.1.8
A paragraph Rule created with some 'when' conditions and property references showed random contents updates after saving and check-in using the source button. This was traced to the use of a newer library for Paragraph rules that was not able to handle Pega JSP tags like "pega:when" or "pega:foreach", causing ckeditor to remove the content. This has been addressed.
INC-215582 · Issue 712285
Cosmos calendar icon handles allow entry set to no
Resolved in Pega Version 8.7.2
When using the Cosmos theme, the Calendar icon became disrupted when "allow text entry" option was set to "no". This has been resolved.
SR-121825 · Issue 181670
Multiple annotations now allowed for swimlane objects
Resolved in Pega Version 7.1.8
When two annotations were used with swimlanes, the description in the annotation is unexpectedly changed or the annotation itself disappeared due to an ID conflict. There was a workaround of adding the shapes using the right click, but the annotation shape is now correctly added to the work flow using the proper unique ID.
SR-123595 · Issue 184394
Resolved issue with extraneous leading "." in attached properties
Resolved in Pega Version 7.1.8
When attaching a file, there were two extra (duplicate) properties created in the Link-Attachment page: .pxCreateDateTime and .pyCategory, each with a dot in front of the name. This caused an error when attempting to modify or copy the page: "The reference .pxCreateDateTime is not valid. Reason: invalid property name: '.pxCreateDateTime'". This was found to be an issue where 'pxCreateDateTime' and 'pyCategory' were being corrupted when set using the put() API. To correct this, the code has been changed to use the PutString() API instead of Put() in the java for the pyCategory property.
SR-123595 · Issue 184318
Resolved issue with extraneous leading "." in attached properties
Resolved in Pega Version 7.1.8
When attaching a file, there were two extra (duplicate) properties created in the Link-Attachment page: .pxCreateDateTime and .pyCategory, each with a dot in front of the name. This caused an error when attempting to modify or copy the page: "The reference .pxCreateDateTime is not valid. Reason: invalid property name: '.pxCreateDateTime'". This was found to be an issue where 'pxCreateDateTime' and 'pyCategory' were being corrupted when set using the put() API. To correct this, the code has been changed to use the PutString() API instead of Put() in the java for the pyCategory property.
SR-120780 · Issue 178357
Corrected text input focus highlighting for accessibility
Resolved in Pega Version 7.1.8
When using an accessible application, the fields with pxTextInput control were not highlighted on focus. This has been corrected.
SR-123741 · Issue 186119
Collapsible header text updated for accessibility
Resolved in Pega Version 7.1.8
When a UI layout/section used a collapsible header, JAWS read the field values "Click to expand" and "Click to collapse." Using the word "Click" is not optimal for accessibility, and this field has been changed to "Disclose contents" and "Hide contents."
SR-126986 · Issue 197102
Added class handling for creation of embedded pages with page-new method
Resolved in Pega Version 7.1.8
After upgrade, an error was generated while using page-new method to create a new page unless the default page class was present. This occurred when an embedded property was created using page-new with a class that is a child class of the defined embedded class and the parent property of that embedded property was auto-populate/special-java. This was caused by the class being different than the defined embedded class, meaning it was considered as a change to pxObjClass (which is not allowed) and it was not handled. To resolve this, a check has been added to set the right class when creating a embedded page by page-new, using the class of the input page when setting value of a embedded property instead of the defined class if present in input page.
SR-127880 · Issue 193696
Rest Connector wizard updated for custom naming conventions
Resolved in Pega Version 7.1.8
After migrating, a data model generated using the Rest wizard would fail when attempting to map a response using pxResults of Code-Pega-List. The mapping logic has been updated to better handle custom naming conventions.