INC-154205 · Issue 618735
Corrected wrap text for Cosmos radio buttons
Resolved in Pega Version 8.4.4
When using Cosmos, radio buttons with large labels were displayed with the text overlapping even when wrap text was enabled and the radio button placement was incorrect. This was traced to a height of 32px being set as the default, overriding the wrap text setting, and has been resolved by adding CSS to set the height as auto when wrap text on radio label is used.
SR-D78274 · Issue 544091
Handling added for dual privileges with MSSQL
Resolved in Pega Version 8.3.3
After setting up dual privileges, the Admin user was able to create a table but the base user received an "insufficient privileges" error. Investigation showed this was an issue when using MSSQL: the generated grant statements used the server login name as the user in the grant statement, instead of the database user. For all other databases, the username passed into the connection is the correct user to use for grants. Only MSSQL has a distinction between this connection user name (the login) and the database user, and since the login did not exist in the user table, the grant failed. To resolve this, when MSSQL is used, the system will fetch the underlying database user when determining the user for grant statement generation.
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.
INC-142084 · Issue 599877
Support added for expression in strategy scorecards
Resolved in Pega Version 8.4.4
When invoking REST against a dataflow that had a strategy containing a scorecard that used an expression and the "Include model explanations option" was enabled in the Strategy configuration, the system failed with the error "PropertyValueInvalid .pxMaxScore Cannot cast the value (unknown) to double". This was traced to the Scorecard explanations failing during serialization when an expression was used, and has been corrected.
SR-D79181 · Issue 551123
OKTA receives parameters on logout
Resolved in Pega Version 8.3.3
When using an OIDC logout endpoint with a parameter set as a data page value, the data page retrieved the ID Token from the database, but when logout was clicked the datapage name was being displayed in the browser instead of the IDToken. To resolve this, code has been added to support sending ID token parameters for logoff endpoint for OKTA logoff using OpeniD connect.
INC-146174 · Issue 602868
Chevron vs Back button in screen flow made consistent
Resolved in Pega Version 8.4.4
When using the TabbedScreenFLow7 harness with the "Enable navigation Link" and "Only allow navigating back to step" settings for the flow along with client-side validations, the validations were ignored when using the back button but using the chevron displayed a validation error. Investigation showed that the case action area buttons and bread crumb navigation were out of sync during the back button operation. This has been resolved by updating the ProcessStep function in BreadCrumbTrial library to pass skipValidations while calling gotoprevioustask.
SR-D85339 · Issue 548180
Calendar AM/PM corrected for Chinese locale
Resolved in Pega Version 8.3.3
When using the Chinese locale (zh_CN), opening a calendar control in the Report definition to select filter values resulted in the Calendar tab dropdown showing "上午" (AM) when the system time was in "下午" (PM). Investigation showed that when generating a non-auto date time control, ampm text (i.e. string value) was compared with the generated select component using locale specific values which did not match any time, so AM was always selected as it was the first value in the dropdown. To resolve this, the system has been updated to use the locale specific AM PM values for non-auto-generated date time control.
SR-D87709 · Issue 552397
Default context check added for saving adaptive model with locked rulesets
Resolved in Pega Version 8.3.3
When updating an adaptive model rule in Prediction Studio, the error message "No unlocked Rulesets/Versions found that are valid for this record. Unlock at least one Ruleset/Version that can contain records of this type." appeared when clicking Save. This occurred when a branch was used in the default context of the Prediction Studio settings. Although there was a workaround to use Dev Studio to Save As the adaptive model rule to the required branch, this has been resolved by adding a check for default context and then saving the model there if it is mentioned.
INC-137100 · Issue 604060
Added predictive text handler for Japanese on iOS
Resolved in Pega Version 8.4.4
The autocomplete function was not working well in MobileView when using Japanese IME on iOS. This has been resolved by adding a new input handler for IOS mobile, which will be triggered when predictive text is selected in mobile.