Published Release Notes

Question template added to surveys

You can now import a question template to create multiple questions at once. By providing question data in a format that your application processes in bulk, you can speed up the development of your surveys.

For more information about the types of questions that you can import, see Question templates.

Update activity for button and link formats

To update existing Button controls or Link controls to current, simplified formats (Strong, Standard, and Simple), use the pzUpdateButtonLinkFormats activity. Using the report definition and other parameters that you specify, the system retrieves the sections to be converted, loops through each section rule to find Button controls and Link controls, and updates their formats.

For more information, see Updated button and link formats and Update-Button-Link-Formats.

Ability to edit questions in the Facebook channel preview console

You can now edit questions directly in the preview console when you simulate a Facebook chatbot conversation. This feature eliminates the need to edit Case Manager settings when you want to modify the text of a question for a configured Facebook channel interface.

For more information, see Simulating a chatbot conversation.

The Upload responses action is not supported for adaptive models with customized context

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.

Changes to User Interface menu in Designer Studio

The User Interface menu in Designer Studio has changed. For example, menu options related to localization are now grouped under Application readiness.

For more information, see Designer Studio - Landing Pages.

Decision Analytics portal renamed to Analytics Center

The Decision Analytics portal is renamed to the Analytics Center portal. In this work area for predictive analytics and text analytics, the business scientist can control the full model life cycle by building predictive models, importing PMML models, building sentiment analysis and text classification models, creating and monitoring adaptive models, and updating any existing models.

For more information, Analytics Center portal.

New alert for distinct values query

The PEGA0093 alert identifies performance issues when a distinct values query from virtual reports or the getDistinctValuesForProperty API take longer than the threshold. For more information, see PEGA0093: Distinct values query took more than the threshold.

Use fast processing option does not work

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.

Behavior changes when reporting on descendant classes

Report Definitions that use the Report on descendant class instances option with the Include all descendant classes option apply only to the Applies to Class. Join classes are not included as they were in previous Pega^® Platform versions. The following example shows what happens for each possible scenario for Report on descendant class instances when the report is defined on ClassA with a class join with Work-.

• If Report on descendant class instances is disabled, the report runs against ClassA and the join happens with Work-. The behavior is the same in Pega 7.3.1 as it is in previous Pega Platform versions.
• If Report on descendant class instances is enabled, and Include single implementation class is selected, the report runs against ClassA and the join happens with the MySampleClass implementation class. The behavior is the same in Pega 7.3.1 as it is in previous Pega Platform versions.
• If Report on descendant class instances is enabled, and Include all descendant classes is selected, the report runs against ClassA and its descendants and the join happens with Work-. In previous Pega Platform versions, the join happened with the MySampleClass implementation class.

Upgrading Adaptive Decision Manager data mart tables might fail

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.