INC-210495 · Issue 708118
Left and right arrow keys work for tabbed Ajax container
Resolved in Pega Version 8.7.2
The left and right arrow keys were not working for input fields inside a tabbed Ajax container. This was traced to a disableArrowKey function in pzpega_ui_tabs js file, and has been resolved by adding an additional check for attribute "data-mdc-recordid" to ensure the arrow keys are active for an input field.
INC-210495 · Issue 708119
Left and right arrow keys work for tabbed Ajax container
Resolved in Pega Version 8.8
The left and right arrow keys were not working for input fields inside a tabbed Ajax container. This was traced to a disableArrowKey function in pzpega_ui_tabs js file, and has been resolved by adding an additional check for attribute "data-mdc-recordid" to ensure the arrow keys are active for an input field.
SR-119989 · Issue 176616
DateTime control logic improved for repeating grids
Resolved in Pega Version Pega Platform, Resolved in Pega Version 7.1.7
If a repeat grid was configured with 'pxDateTime' control for one of the columns, clicking the 'calendar' icon for the first time would not show the calendar. Thereafter, the calendar would appear on icon click. This was found to be an error in the javascript logic where the DatePicker function was returning false even if the event was from the DatePicker control. This has been corrected.
SR-A7750 · Issue 220071
Decision Tree Rule Form shows custom actions
Resolved in Pega Version 7.2
In some installations, values configured in the "Take Actions" or "Actions" dialog were not visible even though they had been configured. The values could be seen in the rule XML and the rules worked as expected. This was traced to the configuration using a custom Function "AddActionRecord" Alias, and a new step has been added to make such values visible.
SR-B8793 · Issue 278410
Flow warnings show consistently
Resolved in Pega Version 7.3
Due to conflicting handling of temporary pages by two different processes within the Rule-Save function, warnings were only displaying intermittently as flow rules were saved, refreshed, or checked in. To ensure consistent handling, a single internal parameter has been added that will be used for creating/removing temporary pages
SR-B8793 · Issue 278405
Flow warnings show consistently
Resolved in Pega Version 7.3
Due to conflicting handling of temporary pages by two different processes within the Rule-Save function, warnings were only displaying intermittently as flow rules were saved, refreshed, or checked in. To ensure consistent handling, a single internal parameter has been added that will be used for creating/removing temporary pages
SR-B53145 · Issue 317256
Back button on Survey screen works with validation
Resolved in Pega Version 7.3.1
If a Survey screen that validates a question failed that validation, the proper error was generated when the criteria did not match. However, clicking the 'Back' button on the screen caused the validation message to disappear while remaining on the current screen and not returning to the previous screen. This was due to a faulty IF condition in the setValue in SurveyAccessMethodBodyQuestion function, and has been fixed.
SR-B81527 · Issue 331290
Silverlight error fixed for LaunchWordMerge
Resolved in Pega Version 7.4
The WordMerge functionality was not working for a Mash-up on a website, displaying a Silverlight error. This occurred when using AppDynamics software for the user environment, and was traced to the pyheadercookiesset including an ADRUM cookie. Because there was an unescaped character added in the cookie, it failed on XML reader parsing in Silverlight. Handling has now been added for the special character.
SR-B81527 · Issue 331290
Silverlight error fixed for LaunchWordMerge
Resolved in Pega Version 7.4
The WordMerge functionality was not working for a Mash-up on a website, displaying a Silverlight error. This occurred when using AppDynamics software for the user environment, and was traced to the pyheadercookiesset including an ADRUM cookie. Because there was an unescaped character added in the cookie, it failed on XML reader parsing in Silverlight. Handling has now been added for the special character.
SR-D31751 · Issue 504653
SQL query performance improvement
Resolved in Pega Version 8.4
Multiple queries were being framed with an UPPER function in the 'where' clause, causing performance issues. Investigation showed that report definitions related to audit (i.e., pyGetWorkHistory and pyGetWorkHistoryWithLatLong) were enabled to retrieve records by ignoring case. To avoid this, the system will compute the correct class name and pass it to the report definitions.