SR-C57557 · Issue 402906
Work Object lock released correctly when modal dialogue is canceled
Resolved in Pega Version 8.1.1
The Work Object lock was not being released when the modal dialogue cancel button was clicked. This was due to the primary page not being switched to the pyWorkPage during the cancel, and has been fixed.
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-C50284 · Issue 402874
Top level activity steps are numbered correctly when child steps exist
Resolved in Pega Version 8.1.1
Top level activity steps were showing as being numbered incorrectly when child steps existed, but saving the rule or refreshing the rule corrected the numbering. This was caused by CSS that was added to the rule form harness to increment the step number; while expanding a top level node the reset happened and then the counter initialized the value. To address this, the code has been changed from CSS counter to CSS attr which will use the index attribute of the current row. Additional CSS cleanups were also done to remove IE9 and other browser-specific styling that is no longer needed.
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.
SR-C53680 · Issue 402914
Filter value Autocomplete uses localized text for the 'Case Type' string
Resolved in Pega Version 8.1.1
The Filter value autocomplete field of the Case Manager portal bulk action landing page was not working as expected while using the Japanese locale setting. If the locale setting was English or empty, the filter value was displayed correctly in the autocomplete. This was an issue with comparisons being hard-coded to use the literal text string 'Case Type', which was failing in localization. To fix this, a 'when' rule has been added to compare localized text against pyFilterName and use it in the appropriate rules.
SR-C57025 · Issue 402913
Filter value Autocomplete uses localized text for the 'Case Type' string
Resolved in Pega Version 8.1.1
The Filter value autocomplete field of the Case Manager portal bulk action landing page was not working as expected while using the Japanese locale setting. If the locale setting was English or empty, the filter value was displayed correctly in the autocomplete. This was an issue with comparisons being hard-coded to use the literal text string 'Case Type', which was failing in localization. To fix this, a 'when' rule has been added to compare localized text against pyFilterName and use it in the appropriate rules.
SR-118053 · Issue 172515
Added edit format for Designer Studio integer control in read-only when
Resolved in Pega Version 7.1.7
In the Integer Control for Designer Studio, it is not possible to set properties on the Edit Format when the presentation is ReadOnly based on a when rule. Both the Formats appear when the Edit Options is selected as Auto. Options have now been added to set the properties.
INC-142223 · Issue 598647
Handling added for new case type using reuse case life cycle
Resolved in Pega Version 8.5.2
Creating a new Case Type in a branch ruleset using the 'Reuse case life cycle' option was not working, and the error "branch rulseset not a candidate" was generated. pxCreateCaseDataPages that are called as part of creating a case rely on Param.RuleSetName; generally this parameter is set in the param page when other assets are created. When Reuse case life cycle was selected, other assets were not created and param.RuleSetname was not set. This affected pxCreateCaseDataPages when branch parameter was provided. This was a missed use case, and has been resolved by setting param.RuleSetName from param.ruleset to fix the issue.