Extension attributes are not supported in PMML models
Valid from Pega Version 7.3.1
Models in the Predictive Model Markup Language (PMML) format version 4.3 that contain extension attributes with the x- prefix are not valid. These extension attributes are deprecated; you must use extension elements instead. In addition, if the output type of any output field in the model is set to FLOAT, change it to DOUBLE.
For more information, see PMML 4.3 - General Structure in the Data Mining Group documentation.
The Upload responses action is not supported for adaptive models with customized context
Valid from Pega Version 7.3.1
A default instance of the Adaptive Model rule contains five model identifiers (.pyIssue, .pyGroup, .pyName, .pyDirection, .pyChannel) that are used to partition adaptive models. If you add other identifiers in your Adaptive Model rule instance, you cannot upload responses to this instance with the Upload Responses wizard and the following error is displayed: The Flow Action post-processing activity pzUploadCSVFile failed: Cannot parse csv file.You can still train such adaptive models with data flows.
For more information, see Training adaptive models in bulk with data flows, Model context, and Uploading customer responses.
Use fast processing option does not work
Valid from Pega Version 7.3.1
The Use fast processing option on Connect REST and Service REST rule forms does not work unless you obtain the HFix-43000 hotfix from Global Customer Service.
Use the following data model guidelines when using fast processing:
- The JSON property names and the clipboard property names must match.
- The JSON tree structure and the clipboard tree structure must be similar.
- The scalar arrays in JSON must be mapped to the clipboard as page lists.
- Multi-dimensional arrays must be mapped into page lists of page lists with the same embedded property names.
In addition, page groups, value groups, and Java objects are not supported by fast processing.
Upgrading Adaptive Decision Manager data mart tables might fail
Valid from Pega Version 7.3.1
Issue: Upgrade from 7.3 to 7.3.1 fails if the data contained in the pxInsName column of the PR_DATA_DM_ADMMART_PRED_FACT table is longer than 128 characters.
Reason: During the Pega Platform™ upgrade from 7.3 to 7.3.1, data in the Adaptive Decision Manager (ADM) data mart tables is migrated from the PR_DATA_DM_ADMMART_PRED_FACT table to the PR_DATA_DM_ADMMART_MDL_FACT table. In Pega 7.3.1, ADM uses only the PR_DATA_DM_ADMMART_MDL_FACT table where the pxInsName property can store values that are 128 characters long. In Pega Platform 7.3, the pxInsName property in the PR_DATA_DM_ADMMART_PRED_FACT table can store values that are 255 characters long. If the pxInsName property contains values that are longer that 128 characters, the upgrade fails.
Resolution: Issue an ALTER TABLE statement to change the pxInsName column size to 255 characters and resume the upgrade. For example:
ALTER TABLE rules.pr_data_dm_admmart_pred ALTER COLUMN pxInsName TYPE varchar(255);
For more information, see Adaptive Decision Manager data model.
Improved UI accessibility
Valid from Pega Version 8.6
Pega Platform™ now supports W3C Web Accessibility Initiative guidelines more fully, which creates a better user experience for people who rely on assistive technologies, such as screen readers.
The user interface now features the following enhancements:
- Improved keyboard navigation and updated ARIA attributes for layouts, including dynamic, repeating, and table layouts.
- Updated navigation for AJAX and dynamic containers.
- More precise keyboard navigation and focus control for pop-up components, such as SmartTips.
- Fixed accessibility gaps in out-of-the-box actionable controls and form components, such as buttons and text fields.
- More accessible error messages with improved color schemes and focus control. To meet the WCAG ARIA guidelines, the Show next Error bar has been retired and substituted with more accessible error symbols.
- Accessibility code included in the Pega Platform ruleset by default, without the need for additional configuration.
For more information, see Supported keyboard navigation.
Improved scroll functionality in vertical tabs
Valid from Pega Version 8.6
When you scroll content in an application that uses the Cosmos theme, the UI now remembers the scroll position even if you switch between vertical tabs, for example, in the case details section. Previously, the application reset the page to the topmost position every time you switched tabs. This update improves the user experience by reducing context switching.
Embedded properties in DX API v2 requests are no longer removed
Valid from Pega Version 8.6
In Pega Platform version 8.5, when you use the POST and PATCH v2 DX API methods with an embedded page property included in the content element of the request, the system removes all properties in the embedded page that are included in the case but are not a part of the request. Now, the merge logic has been modified to update embedded page fields sent up in the request, and keep other fields unchanged.
This feature simplifies client code and prevents data corruption.
End of active support for Cosmos React version 8.6
Valid from Pega Version 8.6
As of the release of Pega Platform™ version 8.8 in October 2022, the early adopter Cosmos React (now Constellation) UI is no longer supported. Consequently, Pega support teams no longer accept assignments and incident reports for the 8.6 version of Cosmos React and DX SDK. Upgrade to a later version of Cosmos React or Constellation to maintain support.