Support for following users in the Pega Express and Case Manager portals
Valid from Pega Version 7.3
You can now follow users in both the Pega Express and Case Manager portals. Posts that are made by users whom you are following are displayed in your Pulse activity feed in your dashboard. In addition, an icon indicates whether followed users are online.
For more information, see the following help topics:
Enhancements to the Send Email smart shape
Valid from Pega Version 7.3
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:
Disable inactive operators
Valid from Pega Version 7.3
As a system administrator, you can control access to an application by disabling Operator IDs. To disable an Operator ID, you can use one of the following options in Designer Studio:
- Call the Service REST: user.
- Change settings on the Operator Access tab on the System Settings landing page or on the Security tab on the Operator ID form.
- Define the number of inactive days in the security policies before an Operator ID is automatically disabled.
For more information, see System Settings - Operator Access tab, Enabling Security Policies, Security tab on the Operator ID form.
Refer to mixin settings in override CSS
Valid from Pega Version 7.3
You can refer to mixin settings inside an override CSS, which makes it easier to maintain and restyle your application. Properties for typography, border, background, and combination mixins can be referenced in an override CSS. For more information see Mixins in an override CSS.
Improved data security for BIX extracts for Pega Cloud customers
Valid from Pega Version 7.3
Data security is improved for BIX extracts in the Pega Cloud. BIX extracts are now processed through the use of a HIPAA-compliant system. As a result of this improvement, the method for obtaining BIX extracts has changed. For more information, see Process for obtaining BIX extracts has changed for Pega Cloud customers.
New process for Pega Cloud customers to obtain BIX extract files
Valid from Pega Version 7.3
The process for obtaining Business Intelligence Exchange (BIX) extract and manifest files for Pega® Cloud customers has changed as a result of data security enhancements for HIPAA compliance. By default, after upgrading to Pega 7.3, you must obtain the BIX extract and manifest files from the Pega SFTP server. From within Designer Studio, you can configure the BIX extract and manifest files to be sent to a remote SFTP server by a file listener. For Pega Cloud customers who have purchased a Pega Cloud SFTP Server subscription, you can configure BIX to send the BIX extract and manifest files to the SFTP server's folders for remote SFTP client download.
For more information about obtaining files from the Pega SFTP server, see Obtaining BIX extract files from the Pega SFTP server.
For more information about having files sent to your SFTP server, see Defining SFTP-related data instances.
Tour IDs and Test IDs in UI controls
Valid from Pega Version 7.3
Many UI controls now support the Test ID and Tour ID fields in the General tab of the layout properties. The Test ID setting generates a data-test-id
attribute to provide a fixed reference to a UI control for automated testing. You can use Tour IDs to create a guided tour of your user interface for users. For more information, see Test ID and Tour ID for unique identification of UI elements.
Test IDs and Tour IDs have been extended to the following UI controls.
Both Test IDs and Tour IDs are supported in the following types of controls:
- Autocomplete
- Button
- Check box
- Date time
- Drop-down
- Formatted text
- Icon
- Label
- Link
- Radio button
- Text area
- Text input
Test IDs are supported in the following controls:
- Grid
- Hidden text
- Tree
- Tree grid
Tour IDs are supported in:
- Dynamic layouts
Improved requestor management
Valid from Pega Version 7.3
From the Requestor Management landing page, you can now manage active requestors and debug their activity on all nodes in the cluster, including the current node and remote nodes. You can view performance and requestor details; start the Tracer or Clipboard tool; profile, interrupt, or terminate the selected requestor; and estimate the data size of all requestors on the selected node.
For more information, see Managing requestors.
Security landing pages and features require privileges
Valid from Pega Version 7.3
Security-related landing pages and features are no longer visible and accessible to every user. To view and configure the following security features, you must have the appropriate privileges:
- Attribute-based access control (ABAC) policies require the pzCanManageSecurityPolicies privilege.
- The Authentication Services landing page requires the pzCanCreateAuthService privilege.
PegaUnit testing now supports flows, case types, and additional assertions
Valid from Pega Version 7.3
You can now create PegaUnit test cases for flows and case types to verify that the rule returns the expected output when you run the test case.
Additionally, you can use the following new assertions
- Assigned to – Verifies that the case is routed to the appropriate operator or work queue.
- Case status – Verifies the status of a case.
- Attachment exists – Verifies that an attachment exists.
- Case instance count – Verifies the number of case types, such as child cases, that are created when the test case runs.
For more information, see PegaUnit test cases for flows and case types.