Published Release Notes

Service Portlet rules are deprecated

Service Portlet rules are deprecated. Existing rules will continue to work, but you cannot create new ones. Use Pega Web Mashup instead. In addition, some changes might impact functionality. If you are using Portlet rules and plan to upgrade, contact your customer service representative.

For more information about Pega Web Mashup, see About Pega Web Mashup.

Deprecated metadata types in the Connector and Metadata wizard

The WSDL, SAP WSDL, and DTD metadata types have been deprecated in the Connector and Metadata wizard. For WSDL, use SOAP integration, and for DTD, use XSD.

For more information about SOAP connectors, see About Connect SOAP rules. For more information about XSD, see About the Connector and Metadata wizard.

Create multistep forms for stages

In Case Designer, you can now create multistep forms for a stage. Create several focused and concise screens to capture the information from users instead of using a single long screen. For example, you can ask users for their personal details in one screen, and then ask them to describe their medical condition in a separate screen. When you create a multistep form, choose a template to determine how the users navigate between screens.

For more information, see Adding a multistep form to a stage (for Dev Studio), Adding a multistep form to a stage (for App Studio).

Support for the POST method in Integration Designer

From Integration Designer, you can now source data from any REST endpoint that requires a POST method to retrieve information. With the POST method, you can encrypt sensitive information in the body of the request.

For more information about using the POST method, see the POST method section on Service REST form - Completing the Methods tab.

Additional case settings in App Studio

You can now make it easier to distinguish your case type from other case types by customizing its icon and selecting a unique case ID prefix in the General case settings.

You can also access Locking and Notifications case settings in App Studio without switching to Dev Studio.

For more information, see:

• Changing the case ID format
• Changing the case icon
• Managing concurrent access to a case
• Enabling case notifications

Configure search for duplicate cases in the step property panel

You can now configure the search for duplicate cases in the step property panel. Save time by specifying search criteria that effectively identify potential duplicate cases.

At run time, make sure that each case represents a unique request by deciding whether to close the case as a duplicate, based on the criteria by which the system marked the case as a potential duplicate, for example, a matching email address.

For more information, see:

• For Dev Studio: Finding duplicate cases
• For App Studio: Finding duplicate cases

Visualize tasks more clearly with the task board view

In spaces and other contexts, you can now monitor and track the resolution of cases by using the task board view. This view groups tasks into columns by status to provide a visual overview for all members of a space. By default, the task board view is enabled in spaces, but you can enable it in any context to meet your needs.

For more information, see Monitoring and tracking cases (for App Studio) or Monitoring and tracking cases (for Dev Studio).

Deprecated support for passing symbolic index as strings to value lists and page lists

Starting with the next release after Pega Platform™ 8.2, passing symbolic indexes as strings in parameters, properties, and string literals to both value lists and page lists will no longer be supported. The following examples show the syntax that still works in Pega 8.2, that will not work in the next release:

myPageList("<LAST>")

and

param.str = "<LAST>"
myPageList(param.str)

The following example shows syntax that currently is not supported and gives a validation error. This syntax will also not work in future releases.

param.str = <LAST>
myPageList(param.str)

To avoid issues after upgrading to Pega 8.3, refactor all occurrences of this syntax in your code. For instructions on how to find occurrences of this syntax in your code, see Refactoring unsupported symbolic index syntax for value lists and page lists.

For more information about the correct use of symbolic indexes, see Symbolic indexes – APPEND, CURRENT, INSERT, LAST, and PREPEND.

Make important content visible by promoting spaces

Now you can make highly relevant content more visible and more easily accessible with promoted spaces. Highlight promoted spaces on a separate tab in spaces to ensure that the most relevant content is quickly available and clearly organized. Promoted spaces are available for every user; however, only users with Super Admin privileges can promote a space.

For more information, see Granting Super Admin privileges.

Default filter settings for Pulse feed sources

Set default filters for Pulse messages, so that users see only relevant posts. Users can temporarily change these settings at run time to view messages from different feed sources, and restore the default settings by refreshing the page.

For more information, see Adding a feed source for the activity feed.