SR-D10309 · Issue 482478
Custom datetime controls correctly appended to Excel export
Resolved in Pega Version 8.2.2
The timezone was not being appended to datetime when exporting to Excel if a custom control was used. This has been corrected.
SR-C86607 · Issue 436441
getProperty API updated to use the pega.ctx.dom API for get element by name
Resolved in Pega Version 8.2.2
When multiple tasks (S- Cases) were added from an interaction (I- Case) and the Service Cases had three auto complete controls which were sourced by parameterized data pages, it was expected that upon selection of the first auto complete, the second and third auto complete values would be populated. However, parameters passed to the Data Pages from the second and third S- Cases, had the same value as the first S- Case even though the clipboard was correct. Investigation showed that with MDC, the pega.util.dom API was failing to get the correct dom element and the needed data pages were not called. This has been corrected by updating the getProperty API to use the pega.ctx.dom API instead of the ega.util.dom API to get element byname.
SR-C74652 · Issue 422902
Grid alignment and headers corrected for Opportunities screen in RTL locale
Resolved in Pega Version 8.2.2
When using the RTL locale, the Opportunity detail screen and search screen had grid alignment and header issues. This has been resolved by updating the py-portal-stages css attached to the enduser skin.
SR-C74650 · Issue 422908
Grid alignment and headers corrected for Opportunities screen in RTL locale
Resolved in Pega Version 8.2.2
When using the RTL locale, the Opportunity detail screen and search screen had grid alignment and header issues. This has been resolved by updating the py-portal-stages css attached to the enduser skin.
SR-D5079 · Issue 438381
Handling added for empty UILabel in grid fields
Resolved in Pega Version 8.2.2
When using a Datetime property with a default format, opening the filter popup and clicking on the 'select all' check box caused the format of the values to break. This was traced to ".pyUILabel" being passed as empty, and handling has been added for that in "pzUniqueValuesGridFields".
SR-C88711 · Issue 439596
Handling added for exception caused by empty page list
Resolved in Pega Version 8.2.2
Attempting to map an auto-populated pageList property in a data transform was throwing a java IndexoutofBoundException. Investigation showed that the system was trying to access the second element of an empty Page List. To resolve this, the system has been updated to use a flat list DataProvider which will return null if the list does not exist rather than return a list that is not associated with the parent page.
SR-C86457 · Issue 482083
Handling added for identifying and passivating disconnected Requestors
Resolved in Pega Version 8.2.2
An issue was seen with restarted nodes where disconnected Requestors were not being properly passivated due to Passivation Blocker permissions persisting with a non-zero value. Requestors are passivated only if permissions are zero. To correct this, code has been added to identify and correctly reset permissions for Requestors that have not been properly decremented to zero.
SR-D8650 · Issue 475300
Handling added for null sort order in file import metadata
Resolved in Pega Version 8.2.2
A NullPointerException was seen while fetching the sort order of indexes during a file import. This was caused by a null being returned for an index that did not have the sort order in the metadata, and has been resolved by adding a null check; if the metadata of the index returns "null" as sort order, then the order will be set to "A".
SR-D9119 · Issue 481687
Handlng improved for rollback of Hfix with dependent HFixes
Resolved in Pega Version 8.2.2
Attempting to rollback an HFix with dependent HFixes resulted in a Hazelcast jar exception. Investigation showed the DL included the same jar multiple times in the dependent hotfixes, which was a result of how the DL was created via the hotfix process. In order to better handle this scenario, when there are multiples of the same entries to delete the message will be logged and the process will continue if the entry is not found in the database.
SR-C93264 · Issue 437310
Inference engine enabled to resolve JourneyManager data flow exception
Resolved in Pega Version 8.2.2
Customer environments were intermittently seeing an exception with the error "Could not get ultimate primary destination for data flow .DF_JourneyManager" when trying to compile an activity that ran a dataflow that ultimately called the DF_JourneyManager data flow. This error was traced to the Inference engine being in a disabled state so the system was not able to get the dataflow output class via declare expressions. The Inference engine has now been enabled to resolve this issue.