SR-D90331 · Issue 553608
Context-specific APIs used for RefreshHarness with AJAX container
Resolved in Pega Version 8.5
After creating an interaction case and letting it go idle, attempting to continue and process the service cases in that case was intermittently resulting in a transaction ID mismatch error. This was traced to handling in the AJAX container, and has been resolved by updating the system to use context-specific APIs for refreshHarness case in doc_submit.
SR-D81726 · Issue 544010
Corrected refresh section for grid dropdown using Google Chrome
Resolved in Pega Version 8.5
When using the Google Chrome browser on a Windows machine, an incorrect click event fired when dropdown options were changed inside a grid was causing refresh section to not work properly. This has been resolved by suppressing the 'click' action on dropdown in the 'ui_events.js' file.
INC-190130 · Issue 678541
Help information updated for using Elastic Search with Report Definition
Resolved in Pega Version 8.7
The support article "Configuring a report definition to run against an Elasticsearch index" has been updated to clarify that the search can pass multiple values with a space in pySearchString as it does OR operation on all the fields, and that filters in the report definition will be used when executing the report directly or when calling the report in the pxRetrieveSearchData activity. https://community.pega.com/knowledgebase/articles/system-administration/85/configuring-report-definition-run-against-elasticsearch-index
SR-A16398 · Issue 232765
UI-Kit updated to use Open Work by Handle in pyFavorites
Resolved in Pega Version 7.2.1
In the Manager portal, clicking on a parent case in the "Following" section opened the subcase instead of the parent case that was being followed. The issue occurred when utilizing the pyFavorites section in a UI-Kit that was configured with the Open Work Item action. To correct this, the UI-Kit for this release has been changed to use the Open Work by Handle option.
SR-A19421 · Issue 237693
Corrected tab group issue when '&' present in tab title
Resolved in Pega Version 7.2.1
Depending on the browser, the drop down function to view the list of tabs was performing inconsistently if '&' was present in a tab title. This was an issue with the character not being encoded, and the dynamic container handling has been updated to correctly display the tab with '&' and all tabs behind it.
SR-D23992 · Issue 494760
Null check added to handle portal refresh when first launched
Resolved in Pega Version 8.1.6
After configuring a button / dropdown in caseworker portal header with 'Refresh current action' onclick or onchange action, an exception appeared if the refresh harness was triggered and the Refresh did not happen. This was traced to the refresh harness happening after portal launch and before any DC action occurred. The portal 'history.state' is null at launch, meaning there was nothing to refresh. To handle this corner case, a null check has been added for the history state to avoid console errors.
INC-176757 · Issue 657785
Interaction History properly saved when running strategy on a different data flow
Resolved in Pega Version 8.7
Customized Interaction History properties that had been added to pyInteractionHistoryConfiguration and pyDefaultWorkingSet and saved into the PR_DATA_IH_FACT table were not being saved properly after upgrading from 7.3 to 8.3. This was a missed use case and has been resolved.
SR-A16621 · Issue 233386
Changed image tag to prevent auto-submit of calendar when parameters exceeded
Resolved in Pega Version 7.2.1
When user wanted to select the future date, he navigates by clicking the Year navigation link (arrow link). During this process of selecting a future date in the Year Navigation link, moving beyond the configured Number of years caused the page to be automatically submitted. This was caused by the input tag used for image causing a form submit, and tag has been changed to an anchor to fix this.
SR-A16638 · Issue 233607
Changed edit control to prevent Google Chrome adding zeroes when localizing
Resolved in Pega Version 7.2.1
When using Google Chrome in some locales, zeros were being added to values in the skin and corrupting entered values. This was due to Google Chrome defaulting to localizing input type numbers, which caused dual localization after the control had already localized the value after reload. When input type is text, only the control localization will happen, so a workaround for Google Chrome has been added where the type of control has bene changed to text in the editable mode for the pyItemAlignment section.
SR-D17825 · Issue 494703
PreSaveAs updated to set the correct ruleset value when saved into a different ruleset
Resolved in Pega Version 8.1.6
When using a BIX Extract rule already configured with properties and filter criteria, attempting to update the filter criteria system resulted in an "invalid property error" and inability to save the updated rule. This was traced to the extract rule being created from another extract rule with 'save as', resulting in the new extract existing in a different ruleset. Because the pxBixReportPage.pyRuleset had the value of the original ruleset instead of rule set in which it had been saved, the system was attempting to find the filter properties in the original ruleset. To resolve this, the Presaveas activity in rule-admin-extract has been modified to check and set the correct value when both the rulesets are not equal.