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.

Data schema error on z/OS split schema upgrades from versions before Pega 7.1.8

Valid from Pega Version 4.1

When upgrading to a split schema on Pega 7.x with IBM DB2 for z/OS, you see an error during the data schema upgrade when the system tries to drop the PRPC_Updatescache procedure. Because triggers on rules tables use PRPC_Updatescache, you must use the ZOSDisableTriggerScripts to disable these triggers before you update the data schema.

  1. Follow the instructions in the Pega 7 Platform Upgrade Guide to upgrade the rules schema, but stop immediately before you upgrade the data schema with the upgrade.bat or upgrade.sh script. The Pega 7 Platform Upgrade Guide is on the Support > Deployment Guides page.
  2. Copy the contents of the <distribution>\ResourceKit\ZOSDisableTriggerScripts directory into the <distribution>\scripts\ directory.
  3. Run fixZosTriggers.bat or fixZosTriggers.sh with the following arguments:
    --action preupgrade
    --dataschema <data schema name>
    --oldrulesschema <old rules schema name. If you are upgrading from a single-schema system, this is the data schema name.>
    --newrulesschema <new rules schema name>
    --automaticddl <Optional. Set to true to automatically apply the disable trigger SQL scripts.>

    For example:
    fixZosTriggers --action preupgrade --dataschema pegadata --oldrulesschema pegarules --newrulesschema newrules --automaticddl false

  4. If you did not set --automaticddl to true in the previous step, run the <distribution>\schema/disable.sql script to manually disable the trigger SQL scripts.
  5. Run the data schema upgrade as described in the Pega 7 Platform Upgrade Guide.

Add subspaces within spaces

Valid from Pega Version 8.2

You can now create subspaces within spaces. By adding a subspace, you can collaborate on a subtopic that is related to the topic of the parent space. For example, you can create an Annual Day subspace within the Events space.

For more information, see Creating a subspace.

Support for sourcing case and Pulse attachments from repositories

Valid from Pega Version 8.2

You can now source case and Pulse attachments from repositories, which provides a complete solution for attachment management. In addition, unlike other external sourcing solutions, repositories do not require OAuth 2.0 authentication, so that you can connect to repositories that use non-interactive authentication.

For more information, see Configuring external sourcing options for attachments

Add varied content to a case with Recent content gadget

Valid from Pega Version 8.2

In an end user portal such as Case Manager, you can now add any type of file to your case by using a Recent content gadget. You can create documents by using a rich text editor, uploading existing files, or attaching URL addresses. Collaborate on all types of content with other members of your team by providing the necessary documents for your case.

For more information, see Adding content to a space (for App Studio), Adding content to a space (for Dev Studio).

Pin enhancements in spaces

Valid from Pega Version 8.2

Improve discussions in spaces and stimulate effective communication by using enhanced capabilities of pins. For example, you can search, filter, and like pins, or pin content of a space to another space.

For more information, see Pinning content to a space.

All search data is encrypted

Valid from Pega Version 8.2

All search data in Pega Cloud deployments is now encrypted, both at rest and in transit. The encryption of search data makes search compliant with regulatory requirements.

For more information about search, see Full-text search.

Create and assign tasks in Pulse

Valid from Pega Version 8.2

You can now create and assign tasks in Pulse for case work that needs to be completed within a specific time frame. For example, you can assign a task to yourself as a reminder to upload proof of address documents to a Car Loans case by the end of the day.

For more information, see Creating a task in Pulse, Enabling users to post messages in the activity feed.

Authentication service for basic credentials

Valid from Pega Version 8.2

A new type of authentication service is available for authenticating operators by using basic credentials (user ID and password). The default Pega Platform™ login is now an instance of this type of authentication service. All basic credentials authentication services include mobile authentication with the OAuth 2.0 protocol and Proof Key for Code Exchange (PKCE). You no longer have to create a custom authentication service to support mobile applications.

For more information, see Configuring a basic authentication service.

Unauthenticated sessions transition seamlessly to authenticated

Valid from Pega Version 8.2

A new authentication service type allows a guest user to use an application without logging in, and to be prompted to authenticate later in the session. This enhancement supports scenarios such as online shopping portals where a user can browse for items and load a shopping cart as a guest but be prompted for credentials at checkout.

For more information, see Configuring an anonymous authentication service.

Create single sign-on authentication services from App Studio

Valid from Pega Version 8.2

You can create and enable single sign-on (SSO) authentication services from a new landing page in App Studio. From this new landing page you can also configure new SAML and OpenID Connect authentication services to provision users. For more information, see Creating a SAML SSO authentication service and Creating an OIDC SSO authentication service.

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