Published Release Notes

Reporting

This release had a focus on extending key capabilities to improve the functionality and ease of use of reporting features based on early adopter feedback.  A series of cosmetic changes and fixes are also included.

• Multiple boxes may be checked on List view checkboxes
• Dashboard Charts slider has been improved.
• Summary View reports and charts have been enhanced.
• Column properties can be added to a report in the Report Editor.
• List view column widths can be set by Smart Info.
• Listviews will display correctly for updated systems.
• Improvements to the GuardRail Report.

New Business impact optimization dashboard

On the Analysis tab of the Application Profile landing page, you can now enable historical specification count and implementation progress by complexity and business impact. On the Business impact optimization dashboard, you can view counts of specifications by complexity and business impact. You can also view counts, by business objective, of specifications that have been implemented and for those not yet implemented. You can filter specifications by release and iteration.

For more information, see Viewing specifications by complexity, impact, and business objective, and Associating project specifications with business impact and complexity.

Easy access to proposition-related rules when creating change requests in revision management

When selecting propositions for change requests in Decision Strategy Manager, you can view the proposition filter, strategy, and when rules that are associated with the decision data the selected propositions belong to. In addition, you can include those rules in change requests. To view and add any associated rules to a change request, the rules must be part of the application overlay. With the ability to view and select all proposition-related data, you can consistently revise not only propositions themselves but also all associated rules.

For more information, see Proposition-centric revision management functionality.

Improved contracts for implementations

For more complete contracts, automations now support embedded pages, default values, and picklists. These enhancements provide a more robust model for inputs and outputs that is easier to update and maintain.

For more information, see Viewing automations.

Enhancements to the Send Email smart shape

The following enhancements have been made to the Send Email smart shape:

• You can now configure the Send Email smart shape in Pega Express.
• You can use templates, such as a rejection template, in your email.
• You can use property values, which allow you to insert the value of a field in your case type, such as First Name, within the email.
• You can insert a link to the case ID in your email.
• You can more quickly configure your recipient list by using two options, instead of one, to send messages to either a list of email addresses or to fields.
• You can choose to send either all case attachments in an email, or you can send attachments of a specified attachment category or an attachment type field. You can specify multiple attachment categories and attachment type fields.

For more information, see the following help topics:

• Sending email from a case (Pega 7.3)
• Sending email from a case (Pega 7.3 express)

Updates to the Data Page rule form

You can use the enhanced Data Page rule form to specify the name of a source system in the System name field in the Data sources section. This field represents the name of the system that is associated with a data source. For example, if your data source is a REST connector that connects to an external weather service such as Google Weather API, you can enter Google Weather in the System name field for the data source. The system name is used to display the source systems for a data type on the External Data Entities landing page.

For more information, see Viewing external data entities.

Store and source content in Box

You can now attach content from Box while working on a case in your application. You can attach files directly to your case or include them in a Pulse message. You can also store all the case and Pulse attachments in your application in Box. To enable content sourcing and storage in Box, configure the Content sourcing and Content storage sections on the Integration & security tab of your application rule.

For more information, see Storing and sourcing content in Box.

Requestor pools management in Designer Studio

On the new Requestor Pools landing page, you can view and manage requestor pools across the cluster, including on the current node and remote nodes. By using this landing page, you can tune the requestor pools to improve the performance of services. You can clear the requestor pool for a service package and view the requestor pool basic metrics and configured thresholds.

For more information, see Requestor pools management, Clearing a requestor pool, Viewing details for a requestor pool, Tuning a requestor pool configuration.

Empty properties are not included in snapshot

History records are smaller and more efficient, because empty properties are no longer included in the snapshot. However, as a result, the history snapshot for sections might present a distorted view of the section.

Automatically generate OpenAPI Specification documentation for application REST APIs

You can now access a clear, standard view of all the REST APIs in your application by using autogenerated OpenAPI Specification (OAS) documentation. In App Studio, you can view the OAS documentation generated for application-specific REST APIs by using the new Application tab in the API channel. Additionally, service package rules now include an OpenAPI tab where you can view the automatically generated OAS documentation for all the REST services included in the service package. With these enhancements, you can easily find, visualize, and test the REST APIs in your application.

For more information, see Generating OpenAPI Specification documentation for application-specific REST APIs.