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.

Collaborate on shared content by using documents

Valid from Pega Version 8.1

You can now share additional information about cases with all users in your application by using documents. Documents enable you to view shared content on a landing page and collaborate on the content with other users in Pulse so that you can resolve cases more quickly.

For more information, see:

Protect a custom mobile app with a device lock

Valid from Pega Version 8.1

Custom mobile applications that use an external identity provider (IdP) that is compatible with OpenID Connect or SAML for login are now protected with the device's personal identification number (PIN) or biometric lock. The app user does not have to set up an additional application-specific password and can unlock the app quickly and easily. You can configure the behavior of the locking method and implement custom locking methods by using a custom native module implementation.

For more information, see Protecting your custom mobile app with a device lock.

Ability to search case attachments in Pega Cloud Services

Valid from Pega Version 8.1

File repositories in Pega Cloud Services are now indexed. Indexing allows your application users to search case attachments from end user portals based on content and metadata.

Add and manage landing pages in App Studio application menus

Valid from Pega Version 8.1

When working in App Studio, you can now create landing pages that are not directly associated with a case flow to make your application more informative. The landing pages are a good place to display the resources that are related to a case, images as well as text. Configure them to provide an overview of the work, workers, teams, reports, or any information that is available.

For more information, see Creating a landing page

Mobile apps now use custom-generated skeletons for page transitions

Valid from Pega Version 8.1

Mobile harnesses are now configured with custom-generated skeletons. Used during page transitions, skeletons render a temporary placeholder UI that closely matches the actual UI while data is being loaded from the data store. The use of skeletons enhances the user experience by providing a smooth transition while data is being loaded.

Skeleton transitions work with both dynamic and Ajax containers on the mobile client but work only with the Ajax container on tablets and desktops.

For more information, see Transition effects on actions.
 

Enabling access to upgraded help

Valid from Pega Version 8.1

After upgrading to Pega Platform ™ 8.1, the default URL to the upgraded help files might be incorrect. To enable access to the latest help files, reset the URL:

  1. In the header of Dev Studio, click Configure > System > Settings > URLs.
  2. Enter the Online Help URL:
    https://community.pega.com/sites/default/files/help_v81/
  3. Click Save.
  4. Log out and log back into Pega Platform.
Note: If client browsers on your network are restricted from Internet access for security reasons, you can also follow these steps to set the Online Help URL to a location on your local host.

For Microsoft SQL Server deployments, change settings to create data types in Integration Designer

Valid from Pega Version 8.1

For on-premises deployments that use Microsoft SQL Server, set the Pega-Reporting/reporting/useMergeHintForRRquery dynamic system setting to true. If you do not configure this setting, you might not be able to create a new data type in Integration Designer that uses Pega as the system of record. Configure the setting as follows:

  • Owning ruleset: Pega-Reporting
  • Setting purpose: reporting/useMergeHintForRRquery
  • Value: true

For more information about configuring dynamic system settings, see Creating a dynamic system setting.

Translation support added to application guides

Valid from Pega Version 8.1

You can now localize the content in your application guides. By referencing paragraphs instead of rich text in your chapters and tasks, you can provide guidance to users in their native language.

For more information about application guides, see Creating a guide for end users.

Data entered in a new harness is lost after a sync operation

Valid from Pega Version 8.1

If you create a case in an offline-enabled application and enter data in a new harness, this data is lost after you click Submit and the sync operation takes place. For more information, see Offline capability and Enabling offline support for cases.

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.

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