INC-216927 · Issue 714495
Conditional handling added for perceived invalid valuelist reference in design time
Resolved in Pega Version 8.7.2
After adding a value list property '.pyDateTimeValue(2)' in a section configured in the view editor, the design time error "config issue" was shown. There were no errors at run time and the application's behavior was correct. Changing the subscript of the value list property to (1) ran without an error. In this scenario, the actual usecase configuration will populate .pyDateTimeValue(2), but the view editor believed there was an error in the section because there was no reference to pyDateTimeValue(1) first. This has been resolved by conditionally changing the pyValue to a template property in design time when a perceived invalid valuelist reference is provided as property in the panel.
INC-217304 · Issue 714588
Regex handling updated for non-empty inputs
Resolved in Pega Version 8.7.2
Expression evaluation for non-empty regex has been updated to include testing for unicode characters to align with recent updates made to CKEditor.
INC-219310 · Issue 717115
WorkSearchGadget updated in Theme-Cosmos-02-01
Resolved in Pega Version 8.7.2
The search icon was not working in Cosmos after update, which was traced to the search icon not having an action set. This has been addressed in Theme-Cosmos-03-01, but in this scenario Theme-Cosmos-02-01 was set as the Application definition instead of Theme-Cosmos-03-01. To resolve this, Theme-Cosmos 02-01-01 has been updated to use the newest version of the @baseclass.WorkSearchGadget section.
INC-220351 · Issue 715873
DSS added to control whether empty captions are skipped for display
Resolved in Pega Version 8.7.2
When the property used a prompt list table type and a prompt value for one of the fields was empty, it is not being shown in drop-down. This caused unexpected default values to appear in drop-down lists. To resolve this, a DSS has been added which may be used to skip empty values. The default behavior of skipEmptyCaption is false to show all values as-is.
SR-A5412 · Issue 219159
Error marking fixed for TreeNavigation7 screen flow
Resolved in Pega Version 7.3.1
When using the TreeNavigation7 harness in the screen flow to call the validation from the post action, any property error in any of the flow-actions caused only the first flowaction to be marked as having an error while the rest were marked as successful. This has been fixed.
SR-A92680 · Issue 263151
Removed duplicate repeat grid header
Resolved in Pega Version 7.3
An extra Grid Header Title was created when allow refresh on update was checked in a repeat grid configured for row editing via modal dialog. This was due to a place holder div error, and has been corrected.
SR-B385 · Issue 270797
ASCII characters properly displayed in dynamic layout headers
Resolved in Pega Version 7.3
When using a field value that contains special characters like + and = to display the header value of a dynamic layout the characters were being converted to their encoded ASCII characters on screen (ex [&] instead of [&]). This was traced to the Field Value text being encoded twice, and the GridHeaderElements function has been updated to correct this.
SR-A100118 · Issue 287256
Auto-populate updated for better page copy references
Resolved in Pega Version 7.3
After upgrade, an error was generated at a page-remove step on the Group information screen while running the quoting process. This happened in cases where a copy was made of a page containing an auto populate property and the data page referred by the AP had Common Parent references, and was traced to the parent page of the reference property having been removed from the common parent page. To resolve this, the auto-populate function has been updated to better maintain references in copies.
SR-A100292 · Issue 270065
Select Values from join properly displayed on chart
Resolved in Pega Version 7.3
In charts of report definitions using a join, properties with prompt select values were displaying the actual data rather than the prompt values. This was due to a handling difference for properties from joins: before rendering the chart, report data was copied to a page that did not have the correct pxObjClass, creating the assumption that the property applied to @baseclass. To resolve this, the class will be set on the page that contains the target property.
SR-A100558 · Issue 271513
Oversized file null-pointer exception resolved
Resolved in Pega Version 7.3
A 413 exception was being generated by uploading files with a size greater than the Initialization/MaxFileUploadSize DSS value. The controls have been modified with a check to restrict properly restrict file size during this process.