INC-175630 · Issue 653863
Application selections only announced when visible
Resolved in Pega Version 8.7
The elements of the application switcher were being announced by the NVDA screen reader even when toggled off, i.e. not visible. The issue was occurring because the focus was remaining at the search bar even after closing the app switcher window, and has been resolved by adding the necessary logic to switch the focus.
INC-143861 · Issue 597558
pzIsScalar 'when' rule updated for Value list and Value group
Resolved in Pega Version 8.2.8
When using the GET/Cases/{ID} API to fetch details about a case, an intermittent HTTP 500 error appeared. This was traced to the 'when' condition pzIsScalar being returned as true for the ValueList property types and trying to set the value on the summaryData embedded page. This has been resolved by updating the pzIsScalar 'when' rule to better handle Value list and Value group.
SR-117674 · Issue 170571
Smart Shapes use properly limited to work class
Resolved in Pega Version 7.1.7
An error in the code made Smart Shapes visible when creating a data-class flow. Attempting to include them by dragging them into the flow design pane resulted in an "empty" utility shape that was missing many of the options normally offered. Because Smart Shapes are designed only for work classes, Smart Shapes will not be visible in shape menu when a flow is created in data class.
SR-108805 · Issue 149539
Help updated to explain When Rule "ALL" Evaluation behavior
Resolved in Pega Version 7.1.7
A 'when' rule evaluating all pages in page list will only evaluate the properties on pages in the list that contain that property. This may cause a "true" result that does not match customer expectations. The hover help has been clarified to explicitly state that the evaluation results apply only for those pagelist entries where the property exists and not for all the page list entries.
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.
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.
SR-116347 · Issue 166799
Error resolved for adding Stage Step Specifications using RTE and Google Chrome
Resolved in Pega Version 7.1.7
While configuring a stage behavior in Google Chrome, if a user had focus within the Rich Text Editor for a specification and submitted the modal, an error was generated. This was caused by an invalid post-value check, and the unnecessary post value has been removed.
INC-173725 · Issue 656480
Logic updated for DX API retrieving View/Action ID using embedded property
Resolved in Pega Version 8.7
While calling the DX API using Assignment ID and action ID, a 500 error response was logged indicating that the server encountered an unexpected condition that prevented it from fulfilling the request. Investigation traced this to the logic used for resolving an embedded property referenced in a control/field to identify the correct page class. In a non-work object context for flow actions the new assign page doesn't exist, but the system was checking for it and clearing off errors from the named page. This has been corrected.
INC-150172 · Issue 611774
Updated class handling for View field security
Resolved in Pega Version 8.4.4
When using a defined View which returned a page and its fields and used an inherited custom work party definition, trying to update the pyWorkParty(Customer) by calling the "post /assignments/{ID}/{actionID}" did not work as expected when Field Security was ON. This was traced to the field security relying on the design time page class information stored in the list/group property, and has been updated to resolve the view fields using actual class information from the work page.
INC-149823 · Issue 608354
DX API returns properly referenced icon class for embedded page
Resolved in Pega Version 8.4.4
When using the DX API to build an Angular JS UI, the response returned from the GET /cases/{ID}/actions/{actionID} api did not return the iconStyle for an icon class that uses a property reference when the flow is on an embedded page. This has been resolved by adding code to set the correct context for pzAPICreateJsonForModes and pzAPICreateJsonForField Rule-Utility-Function.