Published Release Notes

Attribute-based access control model

Attribute-based access control (ABAC) is a security authorization model in which access rights are determined through the use of policies and attributes. A policy decision engine in ABAC evaluates digital policies against available data (attributes) to permit or deny access to the requested resource. For example, you can now determine access rights to cases by examining security attribute values assigned to the user and the case.

For more information, see Attribute-based access control.

Access work items directly after login

You can now directly access work items that you receive as email notifications or URLs. The Pega 7 Platform opens the work item after successful user authentication instead of redirecting you to the portal. For a valid user, the type of authentication or number of failed login attempts does not affect this direct access.

For systems that use basic or secure basic authentication, administrators can disable the redirect URL by setting the authentication/basicschemes/redirectToLoginScreen switch to false.

Open access to quiesced servers when using immediate drain

When using the immediate drain method to perform quiesce on a node, any operator can now access a quiesced server for root cause analysis or remediation, regardless of their user role or privileges. For quiesced server access when using the slow drain method, you must still include either the PegaRULES:HighAvailabilityAdministrator or PegaRULES:HighAvailabilityQuiesceInvestigator user role in a user's access group. Administrators using the slow drain method without either of these user roles are exiled from the quiesced node and are redirected to an active node.

For more information, see Immediate drain available for quiesce when using high availability.

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.

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.

Usability improvements in Pega Express

The following enhancements have been made in Pega Express to improve your development experience:

• Case Designer now has an option to create a case so that you can quickly test changes to the configuration of your case types.
• There are fewer steps in the process for configuring a dynamic view.
• Some controls on the screen have been repositioned for easier access and support for users who are not using a mouse.
• Some elements on the Life cycle tab of Case Designer support keyboard navigation when you use the Tab, Enter, Right Arrow, or Left Arrow keys.
• The status of a case can be set at the assignment level.

For more information about these changes, see:

• Creating a case
• Configuring a dynamic view
• Configuring a case at run time
• Adding an assignment to a process

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.

Email listeners no longer copy the email subject text to the email body

As of Pega^® 7.2.1, email listeners no longer copy the email subject text to the email body when the body is empty. If your customer application expects text in the body of the email, the application might fail. You can configure email listeners to copy the subject text to the body by using the following Dynamic System Setting:

Owning Ruleset: Pega-IntSvcs

Purpose: email/copyBodyNoContent

Value: true

For more information, see Creating Dynamic System Settings.

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.

Open cases in a mobile app with push notifications sent from Pega 7 Platform applications

Push notification smart shapes in a workflow of a Pega 7 Platform application can now send push notifications that open a case in a custom mobile app. Users working in the field can use this feature to instantly access priority assignments instead of having to search for changes manually.

For more information, see Configuring the Push Notification shape.