Skip to main content

Published Release Notes

Find release notes for the selected Pega Version and Capability

Browse resolved issues for Platform releases.

This documentation is for non-current versions of Pega Platform. For current release notes, go here.

Reporting & Data

Valid from Pega Version 7.1.4

This release fixed many existing unlocalizable elements in 7.1 reporting interfaces (The Report Viewer, Report Editor, Chart Editor, and the Report Browser) and now they are fully localizable. Changes were made to make Listview, summaryview,  and report viewer display possible WCAG 2.0 level A and AA support.

  • Parameters may now be used in a sub-report join condition.
  • Report Definition localization has been enhanced.
  • Standalone ListViews with embedded SmartInfo have been improved to resize appropriately when the SmartInfo section is expanded.
  • The data section of a report will now display in all of the available space when a fixed header option is selected.
  • When localizing a listview with filters, tool tips are translated.

Customize your report headers

Valid from Pega Version 7.1.5

You can customize the way that the header for all of an application's reports will be displayed by overriding the section pyReportEditorHeader. Save a copy of this section into the application's ruleset, then edit it to display the information, images, and layout that you desire. Once changes are saved, each of your application's reports will automatically use the updated header.

Advanced inline report filters

Valid from Pega Version 7.1.5

You can create a custom section and use it to display report filter controls at the top of the report, replacing the default display. The custom section can include basic controls (such as a drop-down menu or text entry field), and the controls can only provide values for the filter functions established in the Edit filters section of the Query tab for the Report Definition.

Ability to include all properties in search results

Valid from Pega Version 7.4

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.

Compact style sheet for creating PDF files

Valid from Pega Version 7.4

You can now use a compact style sheet when you create PDF files by using the Create PDF smart shape in a case type or when you use the HTMLtoPDF activity. This style sheet overrides the style sheet that is used by the harness skin and correctly renders certain elements such as headings and inline grid tables. It also renders PDF files more quickly.

For more information, see Creating PDF files by using a compact style sheet and PDF file rendering scenarios.

Data pages can source information from a robotic process automation

Valid from Pega Version 7.4

When you use robotic process automation (RPA), you can now configure data pages to source information from robotic automations so that you can connect your Pega® Platform application to legacy applications in your enterprise. By using automations to retrieve data and save it to a data page, you can use data virtualization to encapsulate your Pega Platform data model from the physical interface of a legacy system against which the automation is running.

For more information, see Obtaining information from robotic automations.

Case-insensitive filtering in reports

Valid from Pega Version 8.2

Filtering in reports is now case-insensitive, improving the reporting and searching experience. You can turn off case-insensitive filtering, for example, by using an activity. You might want to do this if your index is too big or if the length of time it takes for indexing impacts performance.

For more information on report filtering, see Editing filter conditions.

Improvements to email case triaging

Valid from Pega Version 8.2

Improvements to Pega Intelligent Virtual Assistant™ (IVA) for Email make the system more robust and user friendly. When you reply to emails in a triage case, you can forward the email, reply to all, and use the carbon copy (cc) and blind carbon copy (bcc) fields. You can also send Pulse messages to discuss an email case without exposing the information to external users. You are notified in the Email Manager and Case Manager portal if you receive Pulse messages. Even when an email case has been resolved and appears as read-only, you can still send Pulse messages.

For more information, see Email Manager portal and Email triage.

Improvements to the Email channel configuration and content analysis

Valid from Pega Version 8.2

To make the Intelligent Virtual Assistant™ (IVA) for Email more useful and easier to manage, you can track all the Email channel configuration changes that you or other operators make. The system now also detects defined entities and topics, not only in the contents of the email messages and its attached files, but also in the email subject field which improves the responsiveness of IVA to emails. You can map same text that appears in an email triage case to different entities. In previous versions of Pega Platform, only the email body was analyzed but with subject analysis, now the entire email is analyzed for topics and entities, including its salutation and signature.

For more information, see Tracking configuration changes in the Email channel and Enabling the analysis of subject field content during email triage.

Facebook and Web Chatbot configuration in the preview console

Valid from Pega Version 8.2

When you develop a Pega Intelligent Virtual Assistant™ (IVA) for Facebook or Web Chatbot, you can now teach interactive bot conversations by chatting with the bot in the preview console and guiding the artificial intelligence algorithm to the right responses. This ability greatly accelerates conversation development and simplifies configuration, while providing the developer with more transparency in the mechanisms that produce specific responses.

For more information, see Simulating a conversation and building a chatbot runtime and Testing and building a chatbot from the preview console.

We'd prefer it if you saw us at our best.

Pega.com is not optimized for Internet Explorer. For the optimal experience, please use:

Close Deprecation Notice
Contact us