INC-168935 · Issue 645397
CalendarGadget updated to display events in Saudi locale
Resolved in Pega Version 8.6.1
When using the pxCalendar section with the locale setting ar_SA, the calendar was correctly converted to a Saudi calendar but the events which were showing in the English version of the calendar were not showing up in in the Saudi Calendar. This was caused by the CalendarGadget page not populating properly due to the localized Hijri calendar failing a datetime check that was looking for a Gregorian calendar with time in GMT format, and has been resolved by updating the when rule "pzShouldDisplayEvent " to use the proper function for the localized calendar.
SR-D81341 · Issue 546006
Scroll bar scrolls to element automatically with Set Focus
Resolved in Pega Version 8.1.8
An issue with the Scroll bar not scrolling automatically to the correct element when using Set Focus has been resolved by including element select logic in settimeout.
INC-174020 · Issue 650888
Performance improved for Directed Web Access (DWA)
Resolved in Pega Version 8.6.1
Slowness when using a Directed Web Access (DWA) link has been resolved by refining the code of the PZPEGA_UI_DOC_EVENTSCONDITIONSCHAINING script to improve performance.
INC-150395 · Issue 625069
Tokenizer updated to handle commas
Resolved in Pega Version 8.6.1
The Text Analyzer was not working as expected in cases where the number was combined with a comma (,) with it but was working when a space was used between the number and the comma. This was traced to the tokenizer not correctly processing and splitting the input text when there was a special character before or after the token. This has been resolved by updating the tokenizer logic.
SR-D76291 · Issue 541013
Check added for Repositories before saving attachment
Resolved in Pega Version 8.1.8
When creating or updating a case through email listener, the Link-Attachment defaulted the pxStorageType to 'WebStorage'. This caused an issue when using PegaS3, which needs pxStorageType 'Repository'. To resolve this, a check has been added to see if Repositories are enabled, and if they are the storageType will be set accordingly.
INC-172124 · Issue 651292
Improved Operator ID selection in Mobile Logs Retrieval section
Resolved in Pega Version 8.6.1
Data-Admin-Operator-ID.pzOperatorsByApplication returns only the first 500 operators, which is insufficient for large-scale use. There was a workaround of turning off paging for this report definition and setting maximum records to a bigger value, but this caused potential performance issues when opening very large users list. To resolve this, an autocomplete control will now be used to select Operator ID in the Retrieve Device Logs section of Mobile Channel. When part of an operator ID is typed into this control, the first 100 best results are shown and may be selected.
INC-171257 · Issue 651733
Expanded results for Proposition Filter Relevant Record Properties
Resolved in Pega Version 8.6.1
Previously, a maximum of 500 records were returned from pr_data_tag_relevantrecord when using Edit Parameters for the report definition proposition filter rule. In order to accommodate more complex needs, an update has been made to use the D_pxGetClassDataModel data page to fetch all the records and make them available in the dropdown.
INC-169186 · Issue 655538
Disconnect button availability extended
Resolved in Pega Version 8.6.1
A case was not refreshing when the disconnect button was selected while using the standard section for authorization grant type authentication. This was traced to a query executed to find a div with attribute pzInsHandle, but that attribute was not applicable in the user portal. To support this use, the query has been extended to be applicable for user portal (attribute data-ui-meta) and Dev Studio landing page.
INC-156758 · Issue 629938
ExpandStream called before Page-Merge-Into to ensure correct merge
Resolved in Pega Version 8.6.1
The Page-Merge-Into method was not merging the source page into the target page when the use case was run without tracer, but merged properly when run with tracer. This was traced to an intermittent issue with expanding properties, and has been resolved by calling expandStream on the source property if it is unknown prior to checking if the source and target properties are merge compatible.
INC-175707 · Issue 655348
Multi-level strategy gives correct rules during Batch run
Resolved in Pega Version 8.6.1
When using a nested page structure with multi-level strategies that loop through each page and process the customer, a customer with two linked customers A and B had the results of A overridden by B during Batch Processing while single case canvas testing showed the correct results. This was caused by the DSM clipboard page method of carrying the parent page info not supporting the re-use of pages, and has been resolved by adding an enhancement that will sanitize the strategy stage processor to ensure the correct page reference is used.