SR-D79181 · Issue 551125
OKTA receives parameters on logout
Resolved in Pega Version 8.4.2
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.
SR-123595 · Issue 184394
Resolved issue with extraneous leading "." in attached properties
Resolved in Pega Version 7.1.8
When attaching a file, there were two extra (duplicate) properties created in the Link-Attachment page: .pxCreateDateTime and .pyCategory, each with a dot in front of the name. This caused an error when attempting to modify or copy the page: "The reference .pxCreateDateTime is not valid. Reason: invalid property name: '.pxCreateDateTime'". This was found to be an issue where 'pxCreateDateTime' and 'pyCategory' were being corrupted when set using the put() API. To correct this, the code has been changed to use the PutString() API instead of Put() in the java for the pyCategory property.
SR-123595 · Issue 184318
Resolved issue with extraneous leading "." in attached properties
Resolved in Pega Version 7.1.8
When attaching a file, there were two extra (duplicate) properties created in the Link-Attachment page: .pxCreateDateTime and .pyCategory, each with a dot in front of the name. This caused an error when attempting to modify or copy the page: "The reference .pxCreateDateTime is not valid. Reason: invalid property name: '.pxCreateDateTime'". This was found to be an issue where 'pxCreateDateTime' and 'pyCategory' were being corrupted when set using the put() API. To correct this, the code has been changed to use the PutString() API instead of Put() in the java for the pyCategory property.
SR-D87709 · Issue 552400
Default context check added for saving adaptive model with locked rulesets
Resolved in Pega Version 8.4.2
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.
SR-120780 · Issue 178357
Corrected text input focus highlighting for accessibility
Resolved in Pega Version 7.1.8
When using an accessible application, the fields with pxTextInput control were not highlighted on focus. This has been corrected.
INC-137100 · Issue 605837
Added predictive text handler for Japanese on iOS
Resolved in Pega Version 8.3.5
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.
SR-123741 · Issue 186119
Collapsible header text updated for accessibility
Resolved in Pega Version 7.1.8
When a UI layout/section used a collapsible header, JAWS read the field values "Click to expand" and "Click to collapse." Using the word "Click" is not optimal for accessibility, and this field has been changed to "Disclose contents" and "Hide contents."
SR-126986 · Issue 197102
Added class handling for creation of embedded pages with page-new method
Resolved in Pega Version 7.1.8
After upgrade, an error was generated while using page-new method to create a new page unless the default page class was present. This occurred when an embedded property was created using page-new with a class that is a child class of the defined embedded class and the parent property of that embedded property was auto-populate/special-java. This was caused by the class being different than the defined embedded class, meaning it was considered as a change to pxObjClass (which is not allowed) and it was not handled. To resolve this, a check has been added to set the right class when creating a embedded page by page-new, using the class of the input page when setting value of a embedded property instead of the defined class if present in input page.
SR-127880 · Issue 193696
Rest Connector wizard updated for custom naming conventions
Resolved in Pega Version 7.1.8
After migrating, a data model generated using the Rest wizard would fail when attempting to map a response using pxResults of Code-Pega-List. The mapping logic has been updated to better handle custom naming conventions.
INC-125136 · Issue 575999
Topic name prefix support added for Kafka
Resolved in Pega Version 8.4.2
An enhancement has been added to support the use of site-specific standards for the naming of queues. This can be used to add clarification between Kafka Topics created by Pega and those created for internal topics when using a shared Kafka Cluster. This is done using the new setting: <env name=”services/stream/name/pattern” value=”prefix{stream.name}postfix”/> .As an example, if tenant.name is resolved into "myco" and the environment into "prod1", value="{tenant.name}-{environment}-{stream.name}" will result in stream myco-prod1-{stream.name} By default, when stream.provider = EXTERNAL, the default will be “pega-{stream.name}” .