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.

Date range option added to DateTime control

Valid from Pega Version 8.2

The autogenerated DateTime control, used in forms, now features a custom date range option in the calendar picker. To specify a time period, click the From date and To date fields on an interactive calendar overlay. This input method is both convenient and mobile-friendly.

Enhancements to the AJAX container

Valid from Pega Version 8.2

It is now possible to set a document limit for an AJAX container, between 2 and 16 to control the number of documents opened by users. To reduce development time, you can also choose a new option to have no default view. The multidocument mode features tabbed navigation so that users can switch between open documents. A tabless container, on the other hand, includes an out-of-the-box navigation action for Home, which helps application users move within the portal.

For more information, see Configuring the AJAX container.

Moderate and severe guardrail warnings require justification

Valid from Pega Version 8.2

When checking in a rule, all moderate and severe warnings must be justified. Guardrail warnings now appear in a warning header when you save a rule that has warnings. Requiring justification encourages developers to address guardrail warnings. For more information see Application guardrails require justification.

 

Updates to creating and cleaning the test data for automated tests

Valid from Pega Version 8.2

Creating test data for automated tests is now easier and more customizable. During test case or suite creation, you can now create objects, load work and data objects, and add user pages from the clipboard. These objects and pages can be further configured and will be available in the clipboard when you run the test.

For test cases, you can now define a separate set of actions to perform after the tested rule is run, such as applying a data transform, loading a data page or object, or running an activity,

You can also prevent test data from being removed from the clipboard after a test is run so that subsequent tests can use the same test data.

For more information, see Setting up your test environment and Cleaning up your test environment.

Include region headers on forms

Valid from Pega Version 8.2

When you create or modify forms, you can now include region headers for sections that are based on design templates. You can enter a title for the region, select a container format for the header, add icons, and select styles. This greater flexibility enables you to create a more intuitive user interface.

For more information about modifying a design template, see Design templates.

Add Robotic Automation capabilities to your application by using the Connect Robot rule

Valid from Pega Version 8.2

Pega Platform™ supports a new Connect Robot rule that you can use to integrate robotic automation capabilities into your application. You can publish information about automation bundles from Robotic Automation Studio directly to Dev Studio and automatically generate and display new rules. Also, when you source data pages from robotic desktop automations (RDA), Pega Platform displays a list of automations from which you can choose.

For more information, see About Connect Robot rules.

Default support for the OAuth 2.0 framework in custom mobile apps

Valid from Pega Version 8.2

You can now build custom mobile apps by using Pega Infinity Mobile Client or Pega Mobile Client 7 with the OAuth 2.0 authorization code grant flow that is enabled by default. This industry-standard authorization framework increases the security of custom mobile apps. Set up your application to either redirect to a login screen of a specific identity provider, or display a selection of available identity providers upon login. Settings for authentication services are now applied automatically when you build your app. You can ensure that a custom mobile app is secure by using a protection schema, such as a biometric sensor or a custom pin.

For more information, see Build secure custom mobile apps with the OAuth 2.0 framework.

Enhanced SLA settings in App Studio

Valid from Pega Version 8.2

You can now reuse existing service-level agreements for assignments and approvals in App Studio without switching to Dev Studio. For example, you can select an action that the system performs when a task goal or deadline is past due, such as reassigning the task to a different user.

For more information, see Setting goals and deadlines for task completion and Defining an escalation action for an incomplete task.

Support for rich HTML text in IVA for Email

Valid from Pega Version 8.2

Pega Intelligent Virtual Assistant™ (IVA) for Email now supports rich HTML text in email conversations, which enhances the overall user experience. You can enable this option in the Email channel configuration in IVA for Email to display rich text in email conversations for case triaging. Natural language processing (NLP) analysis works flawlessly in scenarios for all email content that contains rich HTML text.

For more information, see Enabling rich HTML text in emails.

Multiple actions triggering during intelligent email routing

Valid from Pega Version 8.2

Pega Intelligent Virtual Assistant™ (IVA) for Email now supports triggering of multiple actions during the intelligent routing of incoming emails, which improves the artificial intelligence capability of IVA for Email so that it is more responsive to user input. For example, you can set up intelligent routing for an Email channel to trigger multiple actions, such as creating a case and automatically replying to an email for the content that you receive.

For more information, see Intelligent email routing, Configuring routing conditions for automatic email handling, and Setting up intelligent routing in Intelligent Virtual Assistant for Email.

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