SR-A91682 · Issue 260252
Repeat grid properly refreshed with add icon when no rows to display
Resolved in Pega Version 7.2.2
The repeat grid was not getting refreshed when the add icon was clicked. Analysis showed that when "Do not display grid header when there are no rows to display" was checked in the repeat grid property panel presentation tab, the grid 'no results' div was placed outside of the grid content div. This caused removeGridNoResultsMsg to fail and the toggleGridStylesForNoResultsCase function was never called after loading the new row. To fix this, the pega_ui_grid JS removeGridNoResultsMsg function has been modified to call the toggleGridStylesForNoResultsCase function when bHideGridHdrWhenNoRows is true.
INC-162122 · Issue 633067
Create modal is accessible when creating case from Create menu
Resolved in Pega Version 8.6
After creating a new case in the Cosmos User Portal, the “Create” screen Modal Dialog opened but focus did not move to any element within the modal dialog but instead stayed on the “Create” button on the left side menu of the User Portal. It required approximately 50 tabs to reach any actionable element within the modal dialog. Investigation showed that the create modal launched the section in an AJAX container that looked like a modal, but the focus was not being correctly set on the first element. This has been resolved by ensuring there is a focusable element when launching an AJAX container.
INC-139085 · Issue 589553
Documentation updated for using Custom Stored Procedure after upgrade
Resolved in Pega Version 8.6
Documentation has been updated to reflect that when upgrading an environment to Pega 8.3+, the following two prconfig/DSS settings should be removed. This is the preferred approach to use the new ID generation mechanism. Additionally, if a database sequence was previously used to generate IDs, pc_data_uniqueid should be added or updated to make sure each case type has a row defined, and that the pyLastReservedID matches the maximum of the relative database sequence value plus 1. env name="pega/sequenceid/useOldOOTBIDGenerator" value="true" or DSS: prconfig/pega/sequenceid/useoldootbidgenerator/default env name="database/databases/customUniqueIDproc" value="sppc_data_uniqueid_custom" or DSS: prconfig/database/databases/customuniqueidproc/default To keep using the old custom stored procedure, the following settings should be given either through prconfig or DSS setting (prefixed with "prconfig/"). The sppc_data_uniqueid_custom can be replaced with a custom procedure name with the same signature as the standard stored procedure. env name="pega/sequenceid/useOldOOTBIDGenerator" value="true" env name="database/databases/customUniqueIDproc" value="sppc_data_uniqueid_custom"
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.
INC-150325 · Issue 616993
Child case has correct context when created from smart shape
Resolved in Pega Version 8.6
The Cosmos Summary Panel was not always updating as expected when a child case was created via a smart shape in the current case flow; the new case opened, but the summary panel still showed the details of the previous case. This occurred when using a create case smart shape in a flow where the case is assigned to the current user, and was due to the child case assignment being opened inside the parent context. This has been resolved by ensuring the child case is opened in the correct context.
SR-A96679 · Issue 265658
Date/Time fixed for calendar icon selection using es_MX
Resolved in Pega Version 7.2.2
An the hour value was disappearing when attempting to select a date from the calendar icon when the locale was set to 'es_MX'. when we try to select a date from the calendar icon. To resolve this, the logic used when certain date formats are applied has been modified to avoid a race condition with the appendToDate function of calender_Util.js
SR-116331 · Issue 171181
Corrected file generation using Rule Base Comparison for product
Resolved in Pega Version Pega Platform, Resolved in Pega Version 7.1.7
Running the Rule Base Comparison wizard on any product rules that have applications rules / data instances included caused a FileNotFound exception error. This was found to be a coding error where the system exported a .jar file but then looked for a .zip file. The export utility has been modified to correctly export a .zip file.
INC-138840 · Issue 599978
Data-Summary reports default will not use the rule resolved setting
Resolved in Pega Version 8.5.2
An intermittent issue was seen where a query could become stuck for ~2 hours in the database. This has been resolved by setting the default for Data-Summary reports to not use the rule resolved setting.
INC-148006 · Issue 605581
Enhancements added for very heavy use of strategy decision logic
Resolved in Pega Version 8.5.2
Recent updates were made to improve memory performance for scenarios where a single request primary page had tens of thousands of pages under an embedded pagelist property and the decision logic involved a strategy running on all the pages in that page list. To further improve performance, the array iterator has been modified and a DSS has been added that makes the threshold (50) in SSAExecutionContextIteratorFactory tunable.
INC-154189 · Issue 617245
Harness used to determine read-only for button/text input
Resolved in Pega Version 8.6
If a button/text input was configured to always be editable in a section by using the /v1/cases/{ID}/pages/{pageID} API (say i.e PageID as Review), the button/text input was always returned as readonly. This was due to the API being hardcoded to return readonly info, and has been resolved by updating pzGetPageDetails to not force read-only and let the harness configuration decide the behavior.