SR-A77524 · Issue 255216
Removed undesired lock in Read-only Expand Pane
Resolved in Pega Version 7.2.2
Expand Pane was locking the work object in a Repeating Grid Layout even when the Display Details Read-Only check box was selected. This lock was acquired when the row was expanded and a thread was created. This was not the desired behavior, and has been resolved with modifications to the ui_modaldialog js function to handle the case of read-only Flowaction.
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-B6770 · Issue 280879
Cleanup improved for embedded page properties
Resolved in Pega Version 7.3
pyPreviousValues was retaining embedded page properties that were no longer used in pyWorkPage, causing the field level auditing to fire and write to the audit history every time the work object was updated. This has been resolved by changing the function rule pzAddHistoryMemoForScalar to remove an embedded page property in pyPreviousValues when the property is removed from pyWorkPage.
SR-B64265 · Issue 314375
Tab key navigation focus fixed for Silverlight
Resolved in Pega Version 7.3.1
When using a word merge functionality in the modal dialog with Tab key navigation, after the "Loaded Silverlight" text highlight, the three subsequent tabs did not focus anywhere on the screen. This improper tab movement was caused by missed handling in the pyPegaSilverlight file that caused tabindex to not be properly set for the hidden controls, and has been fixed.
INC-140789 · Issue 597801
Added handling for validation after inactivity
Resolved in Pega Version 8.5.2
A Validate rule was configured to add an error to a field if MyPageList had any page where MyProperty was not empty. The rule worked correctly if there was no pause in using the UI, but if the UI was left for a few minutes and then the field was changed, the Validate rule always evaluated the expression to true. This has been resolved by adding a null check in Utilities.countInPageList() function.
INC-140789 · Issue 597799
Added handling for validation after inactivity
Resolved in Pega Version 8.4.4
A Validate rule was configured to add an error to a field if MyPageList had any page where MyProperty was not empty. The rule worked correctly if there was no pause in using the UI, but if the UI was left for a few minutes and then the field was changed, the Validate rule always evaluated the expression to true. This has been resolved by adding a null check in Utilities.countInPageList() function.
INC-145939 · Issue 606898
Updated handling for ID value change during REST connection creation
Resolved in Pega Version 8.4.4
When using the REST Connector Wizard to create a connector, if the ID was changed on the 4th (last) step of the Wizard and then the Create button was pressed, the screen would freeze and a display a javascript error. Investigation showed that when the ID was changed on the screen, the new value was not updated properly and subsequent function calls threw errors. This has been resolved.
INC-145939 · Issue 606896
Updated handling for ID value change during REST connection creation
Resolved in Pega Version 8.5.3
When using the REST Connector Wizard to create a connector, if the ID was changed on the 4th (last) step of the Wizard and then the Create button was pressed, the screen would freeze and a display a javascript error. Investigation showed that when the ID was changed on the screen, the new value was not updated properly and subsequent function calls threw errors. This has been resolved.
SR-C2637 · Issue 345584
Date control defaults to current year if data is invalid
Resolved in Pega Version 8.1
When given a Random number as input to Date Control, it was considering it as a year and showing the same year when opening the Calendar icon of the Field. This was caused by the processDate function in calendar.js was incorrectly returning the date, and has been fixed by updating the processDate API of pzpega_ui_calendar.js to display the current year if it is given an invalid date.
SR-C41461 · Issue 386651
DateTime control fixed for year selection with unlimited Date Range
Resolved in Pega Version 8.1
After upgrade, there was a difference in behavior in the datetime control -> year range selection. With default configuration, it was possible to select a maximum of 10 years backwards and forwards, but if the Date Range option was not checked it was not possible to select any year. This has been corrected by implementing spinner functionality for an infinite number of years if the Date Range restriction is not used.