Published Release Notes

Guided tours and online help added to application guides

You can now create application guides that display content from a Pega^® Platform help topic or a sequence of tour stops in a guided tour. By providing supporting information in an interactive format, you can help users complete tasks more quickly.

For more information about displaying help topics, tour stops, and other types of information in a task, see Interactive tasks in an application guide.

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.

Precision of Oracle Timestamp property when using RDB-Save

DateTime properties that are mapped to an Oracle Timestamp column will experience a loss of precision when they are saved using the RDB-Save method. When you use RDB-Save for an Oracle Timestamp, precision will be accurate to the second. For example, a value of 20171119T124745.006 will be saved as 20171119T124745. When you use Obj-Save, precision will be accurate to the millisecond. For more information, see DateTime property mapping in Oracle for Pega 7.

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.

Internal rules in search results and explorers

Using old: is no longer supported in search. You can include internal rules in search results and make them available in the Application and Records explorers. Include internal rules in search results either by adding the PegaDevelopmentruleset to your application or by clicking the Enable diagnostic features option in your operator preferences.

Ability to include all properties in search results

You can now include all properties in a class in search results so that they can be used in report filtering. When the Enable search results for all properties option is selected on the Custom Search Properties rule form, all top level and embedded page scalar properties for the class are indexed and returned in search results, and all embedded page list, page group, value list, and value group properties for the class are indexed but not returned in search results. Selecting this option might affect performance.

In addition, by default, properties defined in the Data-Tag-RelevantRecord instance for a class are indexed and returned in search results and do not need to be explicitly configured.

You must reindex search after selecting or clearing Enable search results for all properties and after changing the properties that are defined in the Data-Tag-RelevantRecord instance.

For more information, see Specifying custom search properties.