SR-D39264 · Issue 518839
Multiple files uploaded using "select file" will be handled asynchronously
Resolved in Pega Version 8.3.2
In order to resolve an intermittent error when uploading multiple files using the "select file" button, each file will be uploaded asynchronously to avoid overloading the browser threshold.
INC-207996 · Issue 709663
Check added for parent case dependency if deferred-save is used
Resolved in Pega Version 8.6.4
After updating the status of a parent case to "Pending-ChildCaseDependency", the wait shape for the child case that should have been triggered by the status did not work and the child case remained on hold. This was a missed use case for the pxCheckFlowDependencies activity where defer-save operations on Index-AssignDeps class was not considered, and may happen when the Queue Processor is evaluating the dependencies while instances to Index-AssignDeps are not committed yet. To resolve this, code has been added to check the entry of the parent case dependency in deferred-save if its not present in Index-AssignmentDeps table.
INC-207996 · Issue 709664
Check added for parent case dependency if deferred-save is used
Resolved in Pega Version 8.7.2
After updating the status of a parent case to "Pending-ChildCaseDependency", the wait shape for the child case that should have been triggered by the status did not work and the child case remained on hold. This was a missed use case for the pxCheckFlowDependencies activity where defer-save operations on Index-AssignDeps class was not considered, and may happen when the Queue Processor is evaluating the dependencies while instances to Index-AssignDeps are not committed yet. To resolve this, code has been added to check the entry of the parent case dependency in deferred-save if its not present in Index-AssignmentDeps table.
INC-207996 · Issue 709665
Check added for parent case dependency if deferred-save is used
Resolved in Pega Version 8.8
After updating the status of a parent case to "Pending-ChildCaseDependency", the wait shape for the child case that should have been triggered by the status did not work and the child case remained on hold. This was a missed use case for the pxCheckFlowDependencies activity where defer-save operations on Index-AssignDeps class was not considered, and may happen when the Queue Processor is evaluating the dependencies while instances to Index-AssignDeps are not committed yet. To resolve this, code has been added to check the entry of the parent case dependency in deferred-save if its not present in Index-AssignmentDeps table.
SR-122809 · Issue 182677
Application Wizard updated to use long-form function name
Resolved in Pega Version 7.1.8
When using the Application Wizard in some environments, clicking 'Preview' or 'Create' on the Data Objects screen caused a refresh and no summary of the created rules was generated. This issue was traced to an error in the library/function rule resolution where the short-form reference to a function was finding more than one suitable rule resolution candidate if there was more than one version of a ruleset function with the same formal parameters and the function was called using the short form of the function name. In this particular scenario the PageListContains function was causing a problem as this function exists in both the PegaSurvey framework and the Pega-AppDefinition ruleset. There was a workaround of doing a private checkout of the CopyFrameworkClassGroup activity and changing the short function rule reference to the long function rule reference (specifying ruleset and library, but the Wizard has been updated to use long-form function name to prevent this issue.
SR-116908 · Issue 168347
When rules now display all text fields for function aliases
Resolved in Pega Version 7.1.7
Creating a new Access When rule failed to show the text fields for most available function aliases when a condition was added to the rule. This was an error in the passing of the classname to the function, and has been fixed.
SR-D32525 · Issue 505467
Dirty check added to offer save/discard changes when closing tab
Resolved in Pega Version 8.2.4
With the OOTB section enabled, performing a change in the form (changing a text value, selecting a option in a dropdown, etc.) and closing the case generated an unexpected alert indicating that the case was changed and the modifications were lost. This differs from the previous behavior of showing the section pyDirtyCheckConfirm which offered the opportunity to save the work. This was a missed use case and has been resolved by updating the system to perform a check for the dirty state when closing the interaction and show a modal dialog asking the user to choose either save/discard if dirty.
INC-154189 · Issue 617247
Harness used to determine read-only for button/text input
Resolved in Pega Version 8.4.4
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.
INC-154189 · Issue 617246
Harness used to determine read-only for button/text input
Resolved in Pega Version 8.5.3
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.
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.