INC-202210 · Issue 740665
Resolved blind transfer error in Pega Call
Resolved in Pega Version 8.8
Attempting to do a blind transfer to another agent using Pega Call generated the run time exception message "Unable to perform ConvertStringToPage, due to invalid inputs." Investigation traced this to the event details not being passed to the UpdateCallFromEvent activity due to the Blind transfer event formatting received from Avaya. To resolve this, an 'if' condition has been added to inpzpega_ui_doc_ajaxengine_js in the PostData function.
INC-143865 · Issue 602198
Handling added for empty back link in BLOB
Resolved in Pega Version 8.4.4
A DirectStreamContainerV7 Exception (BLOB Corruption) was seen when opening a work object that expanded a certain property. This was traced to an empty back link present in the BLOB: during deserialization, the exception was thrown while trying to parse that empty back link. To resolved this, an update has been made which will parse the empty back link information properly.
INC-182152 · Issue 667396
Special character handling updated for export MapValue to Excel
Resolved in Pega Version 8.7
The Excel download was failing when the Row/Column definition or column configuration of a map value contained an equals sign (=) or < > brackets inside quotation marks. This has been resolved by adding an update that will evaluate the comparator value at the start of the row condition value, and row condition value and row condition operator will be set separately.
INC-184419 · Issue 669619
Checks added to prevent EditingMode null value
Resolved in Pega Version 8.7
When trying to open a section rule in developer portal in Pega Cloud, "Error" was displayed instead of the section details. Investigation showed the pyEditingMode property was present but did not have a value, and this has been resolved by adding checks to the UpgradeSequoiaGrid activity to ensure the pyEditingMode of "" does not invoke a data transform of that name.
INC-229921 · Issue 738629
Corrected duplicate repository delete request
Resolved in Pega Version 8.8
The delete request to remove a document from the repository was duplicated. This was caused by the 'pzDeleteFromRepository' activity instantiating the D_pxDelete in its own thread and then again in the current thread due to the D_pxdelete data page being loading asynchronously, and has been resolved by making the calling activity synchronous when loading the data page.
INC-210639 · Issue 705345
Query limit removed from Scenario Planner
Resolved in Pega Version 8.8
Scenario Planner was not correctly finding or opening some Audience Simulations. Investigation showed that when there are 500+ completed data flows, the system was failing to load next 500 records from pegadata.pr_data_decision_ddf_runtime. This has been resolved by removing the query limits, and additional debug logging has been added.
INC-210837 · Issue 707178
DateTime property correctly formatted in Report Editor
Resolved in Pega Version 8.8
When a list report was created via the Report Editor, dragging and dropping a date time property which was embedded inside another page and choosing the format as Date and Time resulted in the property taking pxTextInput instead of pxDateTime. This has been resolved by updating the pzMergeAutoGenForProp activity to get the correct class name for embedded page properties.
INC-221722 · Issue 739201
Menu button no longer steals focus on dismissal
Resolved in Pega Version 8.8
Action menus in the portal harness were stealing focus from input fields in the work harnesses. This was an unintended side effect of work done to correct an issue where focus was not correctly remaining in the table layout, and has been resolved by updating the control menu to avoid the explicit focus in the hideNode function when the menu is already dismissed.
INC-230101 · Issue 738063
Menu button no longer steals focus on dismissal
Resolved in Pega Version 8.8
Action menus in the portal harness were stealing focus from input fields in the work harnesses. This was an unintended side effect of work done to correct an issue where focus was not correctly remaining in the table layout, and has been resolved by updating the control menu to avoid the explicit focus in the hideNode function when the menu is already dismissed.
INC-232518 · Issue 741154
Menu button no longer steals focus on dismissal
Resolved in Pega Version 8.8
Action menus in the portal harness were stealing focus from input fields in the work harnesses. This was an unintended side effect of work done to correct an issue where focus was not correctly remaining in the table layout, and has been resolved by updating the control menu to avoid the explicit focus in the hideNode function when the menu is already dismissed.