INC-185847 · Issue 669526
Handling added for disabling weekends when no weekends are available
Resolved in Pega Version 8.7
A browser exception was generated while selecting the option “Disable weekends”. This was traced to a malformed array of weekends in a scenario where the Data-Admin-Calendar instance had all business days checked (i.e., no weekends). To resolve this, DatePickerAssembly and pzGenerateDatePicker have been updated to handle the case when there are no weekends available in the Data-Admin-Calendar instance.
SR-D68235 · Issue 534782
Stale WorkSearchPreference data cleared when switching apps
Resolved in Pega Version 8.5
The D_pyWorkSearchPreferences data page data was not refreshing while switching between apps, causing stale data to be populated under the case search dropdown for all the applications after switching the application from one to another. This has been resolved by removing the D_pyWorkSearchPreferences data page as part of pzProcessApplicationSwitch.
INC-177323 · Issue 672420
Search string wildcard use documentation updated
Resolved in Pega Version 8.7
The support article for the search API has been updated to clarify the ability to use the wildcard character "*" by manually adding it to the prefix of each term in the search string.
INC-173162 · Issue 650795
Certificate match will use Subject Distinguished Name
Resolved in Pega Version 8.7
Signature verification was failing due to the system not finding the matching root certificate for the chain. The root certificate was in the trust store, but the system found a different certificate first and that other certificate (an intermediate certificate) was not considered a valid certificate for validating the whole certificate chain. This was traced to filtering on the Issuer Distinguished Name (DN) instead of the Subject DN and was due to intermediate certificates potentially having the same Issuer as a root certificate (e.g. if that root certificate was used to create the intermediate certificate). To resolve this, an update has been made to check the Subject DN instead of Issuer DN.
INC-189047 · Issue 674759
Session timeout adjusted for use with Apple Safari
Resolved in Pega Version 8.7
A configured browser session logout timer was not working with the Apple Safari browser. This was traced to browser-specific handling for self.location.href and has been resolved by adjusting the logic and moving it inside a setTimeout to improve cross-browser compatibility.
SR-D89428 · Issue 550392
Data Flow StartTime uses locale timezone
Resolved in Pega Version 8.5
The start time of the dataflow was displayed in GMT instead of the operator locale timezone. This has been corrected.
SR-D77157 · Issue 544472
DataSet preview will use date instead of datetime
Resolved in Pega Version 8.5
While using a DataSet preview functionality, the date appeared as reduced by one day. This has been resolved by parsing date as 'date' instead of 'datetime' to avoid issues with timezone interactions.
SR-D68328 · Issue 557750
Unload handler added for use with custom popups
Resolved in Pega Version 8.5
A memory leak seen in Microsoft Internet Explorer was traced to a custom script to close windows which bypassed window unload and continued to hold some objects in memory. This has been resolved by introducing a new file which will load only for popup harnesses and which registers the unload handler to remove the popup window references.
INC-189259 · Issue 674820
Big Decimal used while converting List to Page
Resolved in Pega Version 8.7
Previous work done to handle precision numbers in the JSON response that were being rounded or truncated when parsed for the DataSource page has been updated to also handle the case of mapping a list to a page.
INC-175892 · Issue 651962
Updated logic for Spinner API used in DateTime control
Resolved in Pega Version 8.7
When selecting 11, 22, 33, 44 in minutes in the DateTime picker, 11 was rounded off to 10, 22 was rounded off to 20, 33 was rounded off to 30, etc. This was due to the match and increment behavior in the UI Spinner Js API used by the DateTime control, and has been resolved by modifying the logic used to calculate the nextIndex in the keydownHandler API under ui_spinner.js .