INC-191902 · Issue 677412
Updated security for importing Excel to a decision table via a delegated rule
Resolved in Pega Version 8.7
An error was seen when attempting to import an Excel file into a delegated decision table when using the case manager portal. This has been resolved by correcting a BAC issue for decision table import in the pzRuleDeclareDecisionTableStandard.js file.
INC-172521 · Issue 651553
Email template content visible in user application
Resolved in Pega Version 8.7
An issue was seen with email templates functionality where the body content given during the email template creation was not visible when the template was used in the application by an end user. This was a missed use case for recent security updates, and has been resolved.
INC-178116 · Issue 660566
Article on configuring display options for a harness updated
Resolved in Pega Version 8.6.2
The documentation around the load behavior of a harness has been updated to reflect that the initialization settings only apply when using the harness as a landing page from the channel config. Applications that use Cosmos React do not use harnesses for landing pages. You can modify Cosmos React landing pages only in App Studio.
INC-178116 · Issue 660565
Article on configuring display options for a harness updated
Resolved in Pega Version 8.7
The documentation around the load behavior of a harness has been updated to reflect that the initialization settings only apply when using the harness as a landing page from the channel config. Applications that use Cosmos React do not use harnesses for landing pages. You can modify Cosmos React landing pages only in App Studio.
SR-C77121 · Issue 423113
Looping issue with CyberArk resolved
Resolved in Pega Version 8.2.2
In order to avoid looping issues when using CyberArk integration, the reference to PRMiniLoader has been removed from PRBaseLoader.
INC-176158 · Issue 664347
Max number of rows setting properly honored
Resolved in Pega Version 8.6.2
The setting for the maximum number of rows to retrieve was still used in a report definition even when it was disabled. This was traced to the report definition being sourced from a data page and having pagination enabled, and has been resolved by updating the handling for this use case.
INC-176158 · Issue 664348
Max number of rows setting properly honored
Resolved in Pega Version 8.7
The setting for the maximum number of rows to retrieve was still used in a report definition even when it was disabled. This was traced to the report definition being sourced from a data page and having pagination enabled, and has been resolved by updating the handling for this use case.
SR-C93555 · Issue 431599
BulkMover updated to not treat Numerics as strings
Resolved in Pega Version 8.2.2
When attempting to update Pega platform 8.1.1 to 8.1.3 with Oracle on a Windows machine with German locale using the out-of-place upgrade of the rules schema, the migration failed at the migration step with the error message "ORA-01722: Ungültige Zahl". This was traced to BulkMover failing when trying to convert a string to a Numeric due to the locale using commas as the decimal separator, and has been resolved by updating BulkMover to not treat Numerics as strings.
INC-170514 · Issue 653762
Lock conflict resolved for AssignmentCheck
Resolved in Pega Version 8.7
The error "Unable to unlock this work object" sporadically appeared in both the runtime log and Pega RULES log when the robot was trying to create a case in Pega using an API call. Investigation showed that as the case was created, it was pulled by another robot (another requestor) which was using the GetAssignments API. This caused the perform assignment check to fail. To resolve this, a 'when' rule has been added to the performAssignmentCheck Activity.
INC-146429 · Issue 602292
Disabled control status made accessible to JAWS
Resolved in Pega Version 8.4.4
When using the Security Event Configuration page (tab) within Pega Dev Studio, the link elements used for 'Select All', 'Clear', 'ON' and 'OFF' were not providing the current State of the element to JAWS. In template rendering of Link control with a 'disable when' condition (server-side evaluation), when the control is disabled it was still accessible and screen readers were not reading the link as disabled. This has been resolved by adding tabindex="-1" and aria-disabled="true" for disabled Link control.