SR-116761 · Issue 169833
FormatNumber use clarified
Resolved in Pega Version 7.1.7
Attempting to use the "pxFormatNumber" function in an activity step generated the error message "com.pega.pegarules.session.internal.mgmt.Executable cannot be cast to com.pega.pegarules.pub.runtime.StreamBuilderToolKit". Formatter RUF were not intended to be called directly from activities, but RUF has been enhanced to work with reduced functionality in case it is called from activity. The documentation has also been updated to reflect preferred usage.
SR-116769 · Issue 174513
Case narrative ordering enhanced
Resolved in Pega Version 7.1.7
The Case Narrative ordering appeared incorrectly when the events are very close together (multiple events within the same second), though the History items displayed in the correct and expected order. When more than one event occurred within the same second, the DATE datatype did not provide a lower level of distinction to allow more granular sorting or ordering. To resolve this, the time value for sorting is now extracted from InsKey.
SR-116778 · Issue 168295
JavaScript error resolved for repeat grids in IE8
Resolved in Pega Version 7.1.7
When using IE8 and Master / Detail editing with a modal window, hitting the enter key to submit a button attached to a repeat grid caused a JavaScript error. This was traced to tabbing forward from the header of a grid: if the grid has no records, the 'no results' message was getting selected as a row and causing a miscalculation. The code has been updated to ensure the 'no results' message is not selected.
SR-116893 · Issue 169075
Corrected browser display errors for large decision tables
Resolved in Pega Version 7.1.7
A browser logic flaw with IE9 caused a condition where large tables would not display the decision table, the 'Show Completeness' button, or the 'Edit in Excel' button if there were more than 500 records. These could be made to be visible with modification to the DecisionTableSizeThreshold and DecisionTableSizeThreshold2 system setting, but the logic has been corrected.
SR-117937 · Issue 173922
Corrected browser display errors for large decision tables
Resolved in Pega Version 7.1.7
A browser logic flaw with IE9 caused a condition where large tables would not display the decision table, the 'Show Completeness' button, or the 'Edit in Excel' button if there were more than 500 records. These could be made to be visible with modification to the DecisionTableSizeThreshold and DecisionTableSizeThreshold2 system setting, but the logic has been corrected.
SR-116899 · Issue 169326
Edit validation displays literal characters
Resolved in Pega Version 7.1.7
If a property with edit-validate defined on it is included in a section with the control TextArea used, an error message is shown on top of the property if the edit validate returns false. However, the error was not shown as literal but rather displayed the encoded characters and was difficult to understand. This was traced to double encoding of characters like ">" in the displayed string, and has been changed so the literal character will appear.
SR-116908 · Issue 168347
When rules now display all text fields for function aliases
Resolved in Pega Version 7.1.7
Creating a new Access When rule failed to show the text fields for most available function aliases when a condition was added to the rule. This was an error in the passing of the classname to the function, and has been fixed.
SR-116936 · Issue 167898
Discarded threads set to properly clear on refresh or tab close
Resolved in Pega Version 7.1.7
When the browser was refreshed or an inactive recent tab was closed on the client side, the discarded threads were not getting properly cleared at the server end. To remedy this, the JavaScript has been updated to cleanly remove the threads.
SR-116950 · Issue 167458
Rule name validation checks relaxed for draft mode
Resolved in Pega Version 7.1.7
In order to facilitate flow design, Decision shape properties will no longer require rule name validation when using Draft Mode.
SR-116950 · Issue 168328
Rule name validation checks relaxed for draft mode
Resolved in Pega Version 7.1.7
In order to facilitate flow design, Decision shape properties will no longer require rule name validation when using Draft Mode.