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-B35942 · Issue 295191
Grid filter column localization fixed
Resolved in Pega Version 7.3.1
The repeating grid's column filter was not displaying the localized pyStatusLabel value. This has been fixed.
SR-B64971 · Issue 315219
Added alt text attribute to paperclip icon for accessibility
Resolved in Pega Version 7.3.1
A paperclip icon in the pzMultiDragDropControlStandard rule did not have alternative text, impacting its accessibility. An alt="" attribute has been added to the image tag to correct this.
SR-B51367 · Issue 311023
Resolved stack overflow for three level nested WO
Resolved in Pega Version 7.3.1
A StackOverflow exception was generated when using three levels of nested work objects due to a recursive looping of the parent pzInskey looking for its children. To fix this, the pyLoadMyCasesNested activity has been updated to set the RD based on whether a parameter sent to it is blank.
SR-B58009 · Issue 312838
Updated removeAssignment call for Assign- class
Resolved in Pega Version 7.3.1
After upgrade, some cases were becoming corrupted with the error "trying to calculate the handle of an instance may not be written to Database". This was traced to an unnecessary removeAssignment call to the ProCom flow library when work objects class is of Assign- ; this is old and has references to named pages like newAssignPage which may be empty. To correct this, the call to pega_procom_flow.RemoveAssignment has been replaced with pega_processengine_flowutilities.RemoveAssignment.
SR-B64353 · Issue 313990
Resolved assignment error when competing with SLA
Resolved in Pega Version 7.3.1
An Assignment error was occurring when the SLA competed with the user for an assignment. This was an error with setting the success indicator in the EstablishContext Activity, and has been fixed.