Published Release Notes

Enhancements to email approvals in a case

The following enhancements have been made to email approvals in a case:

• In Designer Studio, you can quickly access the correspondence rule to customize the email template by clicking the Configure email template link on an approval step.
• In Designer Studio, you can add or remove the fields that are displayed in the approval email by customizing the associated Review view.
• In Case Designer, you can now quickly enable email approval when you click an approval step and route it to another user without having to switch to Process Modeler if you are working Designer Studio or switching to Designer Studio if you are working in express mode.
• Recipients of email approvals can quickly open cases by clicking the links to the related cases that are provided in the emails.

For more information, see Email approval enhancements in a case type.

Approval emails now contain links to cases

Emails that you receive to reject or accept a task in a case now contain a link to the case. You can click this link to quickly open a case for which you receive approval emails.

DocuSign integration

You can now integrate DocuSign with your Pega 7 Platform application to collect digital signatures during case processing. You can make a signature request to DocuSign by adding the Send via DocuSign smart shape to your flow. You can customize your request by overriding the data transforms that are used to make a successful signature request to DocuSign.

For more information, see Integrating DocuSign with the Pega Platform.

Email approval and instantiation not supported on multitenant systems

The Enable email approval check box appears on the General tab of an approval step in Case Designer in multitenant systems. It also appears on the Approval shape in Designer Studio. In addition, in Designer Studio, the Settings tab in Case Designer displays the option to configure email instantiation. However, because configuring email listeners is not supported on multitenant systems, you cannot enable email approval or email instantiation.

Text area field supports rich text

You can now configure a text area field on a form to collect plain or rich text from users at run time. By customizing the way that users provide information, you can create cases that display data in different formats and styles.

For more information about the supported options for text area fields, see:

• Configuring a text area field
• Storage and display of fields

New URL field type on forms

You can now add a URL field to a form to display a link at run time. By using this field type, you can integrate a case with external resources, such as documents and web pages.

For more information about the URL field type, see:

• Adding a single-value field to a form
• Adding a single-value field to your data model
• Storage and display of fields

New notifications for case types

You can now enable email and push notifications for a case type to communicate an event, such as an expired service-level agreement, to users in your application. By calling attention to assignments in a case that require action, you can help users to resolve cases faster.

Assignments in upgraded flows automatically inherit the notification policy that is defined by the case type unless you provide a custom notification activity or explicitly disable notifications in the Assignment shape.

For more information, see: Case notifications.

New achievement badges

New achievement badges have been added to help you learn about and explore Pega Express.

The new badges are:

• Configure a new application view
• Configure a layout
• Add a chart to a report
• Set a profile picture
• Post to Pulse
• Manage team details
• Enable push notifications

For more information about badges, see Achievement badges.

Escalation actions removed from case-wide goals and deadlines

The option to define an escalation action for a case-wide goal and deadline has been removed from Case Designer because the standard actions, Notify assignee and Notify manager, apply to assignments, not cases. You can still define escalation actions for goals and deadlines that apply to an assignment.

For more information, see Defining an escalation action for an assignment.

Deprecation of override rulesets in run-time ruleset lists

Pega 7.2.1 is the last release where override rulesets can be incorporated in the run-time ruleset list. The ability to create override rulesets was originally deprecated in Pega 7.1. However, any override rulesets that were created in releases prior to Pega 7.1 in the application ruleset lists were still incorporated into the run-time ruleset lists at the appropriate location. In releases after Pega 7.2.1, override rulesets will be ignored and will not be incorporated in the run-time ruleset list. Therefore, it is recommended that you use production rulesets in access groups instead of override rulesets.