SR-B34028 · Issue 329193
Resolved error message on mandatory property in grid with Microsoft Internet Explorer
Resolved in Pega Version 7.4
When using Microsoft Internet Explorer, a property marked as mandatory inside a grid layout was firing its validation when the section was loaded. This caused an error icon to appear for a mandatory column on the first row when adding a new row from an always editable grid. This was traced to focus happening twice on the mandatory column, and has been fixed.
SR-B73244 · Issue 332729
mParams changed to local maps in PresenceSessionStateTrackerDaemo.java
Resolved in Pega Version 7.4
In order to resolve a managed connection CME error and memory leak for java:/eis/PRAdapterConnectionFactory when using JBoss 6.4 EAP with Oracle 12c DB, the mParams member variable in PresenceSessionStateTrackerDaemo.java has been removed. Local maps in startThreadInETier() and requeueETierInvocation() will be used instead.
SR-A3008 · Issue 219945
Check added to handle Next button disable for repeat grid
Resolved in Pega Version 7.2
The 'Next' button on a modal dialog was not disabled correctly when launched from a repeat grid due to the wrong "currentPageSize" being passed to the server when using an expand pane grid. A check has been added that will handle the expand pane grid and return the right "currentPageSize".
SR-B96109 · Issue 344391
Calendar control fixed for Buddhist dates
Resolved in Pega Version 7.4
The Calendar control was not showing the Buddhist calendar when using the Thai locale (th_TH). This was an inadvertent result of an implementation update in calendar, and has been fixed.
SR-A733 · Issue 207631
Edited Propositions retain format
Resolved in Pega Version 7.2
When updating a Proposition using the "Edit" button, the format was lost, however updating the proposition using the "Bulk Edit"-> 'Edit in Excel' button preserved the formatting. This has been addressed by making the default UI control for the text values a Text Area, which maintains the multi-line format.
SR-A5880 · Issue 216627
Updated error label highlighting for reused sections
Resolved in Pega Version 7.2
The error highlighting was inconsistent when a section was being re-used in the same screen. This was an issue with the use of multiple controls with the same label (label for=xxx) in the form, leading to only the first control?s label being highlighted in red. This has been fixed by looking at the label closest to the error element.
SR-A8520 · Issue 217466
Updated error label highlighting for reused sections
Resolved in Pega Version 7.2
The error highlighting was inconsistent when a section was being re-used in the same screen. This was an issue with the use of multiple controls with the same label (label for=xxx) in the form, leading to only the first control?s label being highlighted in red. This has been fixed by looking at the label closest to the error element.
INC-192769 · Issue 683001
Removed incorrect role from accessible filter logic
Resolved in Pega Version 8.7
When using JAWS, tabbing out from Close(X) and setting focus on the "filter by" section resulted in JAWS reading out "use arrows to move". This was not an available action, and has been resolved by removing role="listitem" from the RRFilters_logic.
SR-C6074 · Issue 349037
Indexing doc clarifies JVM setting ramifications
Resolved in Pega Version 7.4
The Indexing section of the install / upgrade guides recommended setting the -Dindex.directory JVM argument, but did not explain the consequences of not doing so. The help document and PDN have now been updated to clarify that if this setting is not used and if a custom index file directory is used on the Search Settings Landing page, the system will revert to using the default directory if no other index host nodes are online when a server starts.
SR-B84184 · Issue 334535
Removed unnecessary save button for delegated data types
Resolved in Pega Version 7.4
A blank ActivityStatusError message appeared and an error was logged when attempting to edit and save a delegated Data Type. This was traced to an unnecessary Save button: this Save button is used in Data designer to save the Data class and its settings, but records added or updated in the Delegation screen are auto saved. This led to the save generating an exception when it was unable to find the properties which it would use in Data Designer. This has been corrected by changing the display conditions for the Save button so it will not appear for delegated Data types.