Published Release Notes

Improved data security for BIX extracts for Pega Cloud customers

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

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

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

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

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

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.

Authenticate users in processes with a JSON Web Token

You can generate and process a JSON Web Token (JWT) in Pega^® Platform to secure communications in Pega Platform applications. JWTs are intended to securely transmit small amounts of information between two parties. Because the JWT is signed, the integrity of the information is assured. The contents of the JWT can be used to authenticate a user or to exchange information.

For more information, see Token Profile data instance.

Automatically process cases with SharePoint

You can now use Microsoft SharePoint Online to store and source case and Pulse attachments and to store and source attachments during automated case processing. Users only have to provide authentication and authorization details the first time they access SharePoint Online or when the trust has expired. The authentication profile must be OAuth 2.0 with a grant type of authorization code. The SharePoint Online component can be downloaded from Pega Exchange. For more information, see Downloading and configuring pluggable content management components.

Flexbox support for all default layouts

To improve scalability, Pega Platform supports flexbox-based layouts by default in all its screen and column layouts and layout groups. You can convert existing layouts to flexbox-based layouts by selecting the Optimized code option on the Presentation tab of the layout.

For more information, see Screen Layout Properties.

Ability to set default values when importing data

You can now set default values for data that you import for a data type from a .csv file. By setting defaults, you can ensure that even when the .csv file data is incomplete, all of the data is imported. In addition, you can set default values for custom fields that do not have a matching source column in the .csv file. This feature is available for the Add and update and Add only import options. For mapped fields, the default value is used for new records if the source field is blank, and for existing records if both the source and target fields are blank. For custom fields, the default value is used for new records if a default value is provided, and for existing records only if the target field is blank.

For more information, see Importing data for a data type.