SR-D42583 · Issue 514487
Label of a field is correctly rendered when a section is re-used with a visiblity condition
Resolved in Pega Version 8.4
The label of a field was not being rendered/visible when a section with a 'visible when' condition was re-used in different Page Contexts. The label was displayed correctly if 'Run visibility condition on client' was checked. As part of performance improvements made in a previous version, label generation was moved under the dlcellvisibility flag. Because of this, if a section was re-used at multiple places with different contexts and one place had visibility false and another had visibility true, the labels were not getting generated for the visible section. To resolve this, Label Generation has been moved out of dlcellVisibility to ensure label metadata will always be generated. Updated performance improvements have been made instead by way of a DSS setting (generateCellMetadata) so that when generateCellMetadata is true, the label generation will honor dlcellvisibility to generate the label metadata.
SR-C44375 · Issue 387180
Check added for multiselect object type when using Microsoft Internet Explorer 11
Resolved in Pega Version 8.1
Using the multi select control worked fine in Google Chrome but was throwing JS errors when used in Microsoft Internet Explorer 11 and causing the whole flow action to hang. Object.keys on a non-object throws error as per ES5, but on ES6 a non-object argument will be coerced to an object. This error was seen because the older version of Microsoft Internet Explorer still uses ES5. To better handle this, the system will check for the object type before using object.keys in pzpega_control_multiselect.js.
SR-C36057 · Issue 387665
Required field error message appears under multiple controls when using multiple multiselect
Resolved in Pega Version 8.1
Error messages for multiple controls in a repeating dynamic layout displayed only for first control instead of the expected behavior of an error message displayed under all controls. The required error messages were not showing up when multiple multiselectlist control was being used due to a missing name attribute for multiselectlist control, and this has been added to correct the problem.
INC-168837 · Issue 646972
CSRF token updated for use with OKTA login
Resolved in Pega Version 8.7
An issue seen while connecting via OKTA has been resolved by updating the CSRF token validation for use with IDP initiated SSO login.
SR-C19285 · Issue 358754
Blacklist when performance improvement
Resolved in Pega Version 8.1
When running a performance test, the when delta sync blacklist when rule generated 1.6BG of garbage. In order to improve performance, a data page will be created to hold blacklisted delta sync data pages.
INC-192464 · Issue 681751
PackageComponent updated for use with repositories
Resolved in Pega Version 8.7
Exporting a zip file created by the Component wizard to a repository resulted in an error, however the same process worked as expected when the zip file was created by the Product wizard. Investigation showed that pxPackageComponent was not kept up to date with new metadata requirements for Artifactory export. This has been resolved by modifying pxPackageComponent step 7 to set Param.ArtifactType to "component" and Param.ArtifactName to [component name]_[component version]. A privilege check has also been added to zipMoveExport.
INC-143036 · Issue 599192
SurveyPage loads when ruleset is locked
Resolved in Pega Version 8.4.4
When the ruleset containing the survey rules was locked D_pzSurveyPage did not load and errors were generated. Investigation showed that if the flow was in a locked version, the PopulateShapeNodesFromFlowData activity did not call EvaluateConnectorState, causing the mapping of the transitions for connectors to fail in the activity MapBranchShapeConnectors. This has been resolved.
SR-D21569 · Issue 491705
PUT and WHEN support added for REST
Resolved in Pega Version 8.4
Data layer rules in Pega were not getting generated through the Wizard- ‘Create Rest Integration’ when invoking the Rest service though the PUT method. This has been resolved by adding support for PUT and DELETE in pypresentdatapageoptions.
SR-D56373 · Issue 518885
Mutiselect can localize "Use"
Resolved in Pega Version 8.4
Localization has been added for the value "Use" in the multiselect control.
INC-163452 · Issue 631831
Validation correctly triggered when skipping flows
Resolved in Pega Version 8.4.5
When using a screen flow which allowed users to navigate the flow freely, validation was not triggered on submission. In addition the server or client side validation was being cleared when the case used optimistic locking. Investigation showed that pzShowConflicts was called for optimistic locking on FinishAssignment, which was clearing off the messages and allowing the flow submission. To correct this, a check has been added to pzShowConflicts to check for defer errors in screenflow while clearing page messages.