SR-C89628 · Issue 430885
Correct values are selected in auto-complete in list configuration after scrolling
Resolved in Pega Version 8.2.2
When a value from the second page of the source list in the auto-complete was selected, the prior value was getting selected and posted. As an example, if the (n)th value was selected by scrolling down the results in the list, the (n-1) value was getting selected and posted to clipboard. Investigation showed this occurred if autocomplete was configured with allow free form input ' no', and that results were not getting selected properly after first scroll when using list configuration. This has been corrected.
SR-C91274 · Issue 481698
Corrected Base64Decode calculations
Resolved in Pega Version 8.2.2
Testing indicated that a file encoded using Base64Encode generated the error "The Operation completed successfully, but returned no content" when decoding with Base64Decode. Validating the content of the text file via a JSON validator using text formatted as JSON worked as expected. Investigation showed that extra padding characters were being appended due to calculations around CRLF characters, and this has been corrected.
SR-C96406 · Issue 482945
Corrected default parameter passing to fetch childcases audit details
Resolved in Pega Version 8.2.2
After upgrade, Child case audit details in a Parent Case were not visible even after checking the Show Subcases option. This was traced to refactoring work done in an earlier version; in earlier releases, the parameter ShowSubCases defaulted to true if it was not already present. Later during refactoring, a call to pzFetchCaseStatusUpdate was added but did not include support for passing the parameter page if the parameter had been set by default instead of explicitly being included. Since the parameter was missed, the subcase audit details would not be fetched. This has been corrected so the parameter needed will be passed and fetch the subcases.
SR-C92195 · Issue 431137
Corrected harness for webchat console in mobile and incognito StartCase
Resolved in Pega Version 8.2.2
After configuring a webchat and using the mashup code to load the chat interface, refreshing and starting a new chatbot session caused the wrong harness to be rendered. This was also seen in an incognito window. To correct this,the New and Perform harnesses in Work-Channel-Chat.pyStartCase have been updated.
SR-C94914 · Issue 436301
Cursor position retained after password field refresh
Resolved in Pega Version 8.2.2
If a section was created which contained a Password control with an "Any Key" event that included "Post value" and "Refresh-Other section" actions, the cursor always stayed at the beginning of the line. This has been resolved by adding code to ensure the caret position is retained after a refresh for the password field.
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".