Published Release Notes

Use spaces to collaborate with users

You can now collaborate with other users in your application on a specific area of interest by using spaces. By restricting the discussion of certain topics to the users of a space, you can avoid broadcasting irrelevant messages to all users in your application.

For more information, see:

• App Studio – Collaborating with users by using spaces
• Dev Studio – Collaborating with users by using spaces

Collaborate on shared content by using documents

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:

• App Studio – Collaborating on shared content by using documents
• Dev Studio – Collaborating on shared content by using documents

Ability to search case attachments in Pega Cloud Services

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.

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

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.

Add subspaces within spaces

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.

PATCH support for REST integrations

REST connectors and REST services now include support for integrating with REST APIs that require using the PATCH method. REST integrations that support the PATCH method allow you to make partial updates to individual resources while retaining data that does not require an update. With PATCH support, you no longer need to write complex custom code to integrate with services that require using the PATCH method.

For more information about REST integrations, see Connect REST form - Completing the Methods tab.

Configure REST connectors for standard-compliant endpoints

REST connectors now support all standards-compliant endpoint URLs, regardless of how those URLs use query parameters.

This URL support allows you to do the following actions:

• Include repeated query string parameters in a URL.
• Omit a query string parameter if the value of the parameter is empty when you send a request.
• Apply appropriate encoding for different URL components.

For more information about REST connectors, see Connect REST form.

Support for sourcing case and Pulse attachments from repositories

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. 

Elasticsearch reports support string comparison operators

To improve performance, reports that use string comparison operators in filters can now run queries against Elasticsearch instead of querying the database. The following operators are now supported for Elasticsearch queries.

• Starts with, Ends with, Does not start with, and Does not end with
• Contains and Does not contain
• Greater than, Less than, Greater than or equal, and Less than or equal

In cases where a query cannot be run against Elasticsearch, the query is run against the database, for example, if the query includes a join. To determine if a query was run against Elasticsearch, use the Tracer and enable the Query resolution event type. For more information, see Tracer event types to trace.

Add varied content to a case with Recent content gadget

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).