SR-D89071 · Issue 569733
Case status label localized in export to Excel
Resolved in Pega Version 8.4.2
The Case status(.pyStatusWork) value was not localized in export to Excel. Investigation traced this to Report definitions not passing default parameters specified on the property ruleform for the "default control". Therefore, the first 'when' condition in WorkStatus was evaluating as false, which caused the wrong field value to be used for reports. To resolve this, the first 'when' condition of WorkStatus control has been updated to succeed if the useStatusWorkFieldValue parameter is not passed. The default is true when it is not present.
SR-D86429 · Issue 551373
Badge text Control Format supports declare expression target
Resolved in Pega Version 8.4.2
In the user screen, some properties are shown in 'Text' control with 'Badge text' control format. When the value of this property was set in Data Transform, it appeared correctly. When the property value was set in Declare Expression, no background color was set. This was traced to a missed use case in the implementation work for vtable, which resulted in the control format mentioned in presentation tab of control not being applied on markup when the property was a declare expression target. This has been corrected.
SR-D3405 · Issue 439258
URL construction logic updated for Tracer
Resolved in Pega Version 8.3
When trying to trace a requestor from the requestor management landing page, a 400 bad request error was generated. Investigation showed that when forming the tracer URL, the pxRequestor.pxRequestorPathInfoInReal property was being appended to it. Because the property contained unencoded characters([), the request was not being processed. To resolve this, the URL construction logic has been changed to use pxThread.pxReqBaseURI.
SR-C89463 · Issue 433820
Corrected tab name handling in Report Browser
Resolved in Pega Version 8.3
When using the report browser, refreshing the page after subscribing and unsubscribing to a report changed the tab name to the task id (eg. "PX-ST-123") and an extra tab appeared. This has been corrected.
SR-C84231 · Issue 422665
Merge multiple branches tool updated to resolve selection error
Resolved in Pega Version 8.3
When an application was configured to not allow branches to be merged without being reviewed, the "Merge multiple branches" tool did not allow any branches to be selected even if they had been reviewed. This was traced to the pzLoadBranches activity using local.reviewStatus even though the local variable was not required in this case. To resolve this, the activity has been modified to use Param.reviewStatus to pass the parameter page to pzSetBranchReviewStatus activity. If the 'when' rule pyAllowMergeWhenNotReviewed is set to false, the checkbox will be enabled for branches which are reviewed. For branches which are not reviewed, the checkbox will be disabled and the message "Please review the branch before merge" will appear.
SR-D17318 · Issue 489605
Enhancements added to Proposition Filter
Resolved in Pega Version 8.3
Previously, when propositions were filtered based on only specific criteria, then propositions based on both the specific and default criteria were shown. An enhancement has been added to address this, as well as to create a better user experience for the proposition filter with a simpler UI and some additional features. In this revision, there is one data model that supports the platform proposition filter as well as Pega marketing's eligibilities. The condition builder is used in the Proposition filter rule to align user experience with marketing, and the new proposition filter supports parameters for when rules. DMSample contains an example proposition filter rule that uses and showcases the new UI, including available values.
SR-D64558 · Issue 527678
AttachmentContent supports S3 storage
Resolved in Pega Version 8.4.2
Using a D_AttachmentContent data page to display the contents of an attachment by way of the pyGetAttachmentContent activity worked when using the Pega database for storage, but generated an error stating CMIS access was disabled after switching to S3 storage. This was traced to restrictions on Link-Attachment pages in Step 2, Line 64 of pyGetAttachmentContent to enable attachment stream retrieval from web storage and repositories by D_AttachmentContent, which has now been removed. In addition, pyGetAttachmentContent has been updated to behave the same whether a Link-Attachment page or Data-WorkAttach page is provided when populateAttachStream is set to false, and the rule documentation (description/usage) has been updated accordingly.
INC-142557 · Issue 600532
Accessibility added to Recents
Resolved in Pega Version 8.4.4
Under all recent items, the work object was not opened when using the keyboard and the focus was on the work object. Clicking with the mouse worked. Investigation showed that on pressing the enter key, actions were not triggered because the action string was not on the same SPAN tag (but in child node). This has been resolved with an update to add tabindex on the same span where action-string is added. In addition, accessibility was not enabled on the out-of-the-box Recents table because the work object elements in the table used a formatted text control; this has been updated to use a link control which will enable the accessibility feature while using keyboard navigation.
INC-142557 · Issue 600529
Accessibility added to Recents
Resolved in Pega Version 8.4.4
Under all recent items, the work object was not opened when using the keyboard and the focus was on the work object. Clicking with the mouse worked. Investigation showed that on pressing the enter key, actions were not triggered because the action string was not on the same SPAN tag (but in child node). This has been resolved with an update to add tabindex on the same span where action-string is added. In addition, accessibility was not enabled on the out-of-the-box Recents table because the work object elements in the table used a formatted text control; this has been updated to use a link control which will enable the accessibility feature while using keyboard navigation.
SR-C87881 · Issue 427101
Additional dropdown options exposed for RD column definitions
Resolved in Pega Version 8.3
When using Column formatting in Report Definition ruleform, the "Negative format" option was losing its custom style after opening and submitting the "Format" popup using the magnifying glass. This was caused by the submitted popup overwriting the inherited style reference. Previously, the style ref options were hidden from the dropdown because the same UI is shown in the ruleform and the end user portals and the desire was to avoid end user confusion. In order to support developer use, pzPopulateNegativeFormat has been updated to expose the missing options in the dropdown.