Improve application test coverage by running multiple sessions
Valid from Pega Version 8.1
You can improve the test coverage of your application by using a new test coverage method - Application Coverage. Multiple users can perform coverage sessions which are aggregated into a single report. By using report metrics that show the number of rules that are covered and are not covered by tests, developers can identify which areas of the application need more test coverage.
For more information, see the Test Coverage landing page.
Security fields in JFrog Artifactory repository rule form removed
Valid from Pega Version 8.1
The fields in the Security section of the JFrog Artifactory repository rule form, including the Secure protocol field, the Truststore field, and the Keystore field, were not functional in Pega Platform™ 7.3, 7.3.1, and 7.4. This section has been removed from the JFrog Artifactory repository rule form in Pega Platform 8.1.
Data pages can source information from a robotic desktop automation
Valid from Pega Version 8.1
You can now configure data pages to source information from robotic desktop automations (RDA). Using an RDA to source a data page allows you to connect your Pega Platform™ application to any application that is accessible from an end-user's desktop. By using automations to retrieve data and load it into a data page, you can use data virtualization to separate your Pega Platform data model from the physical interface of a legacy system against which the automation is running.
For more information, see Obtaining information from robotic automations.
Unit testing support for more rule types
Valid from Pega Version 8.3
You can now create unit tests for the following additional rule types. You can also create assertions to validate activity status. The expanded rule types for unit testing enable developers to more thoroughly perform regression testing of their application, thereby improving application quality.
- Collection
- Declare expression
- Map value
- Report definition
For more information about unit testing rules, see Pega unit test cases.
Upgrade impact
With the four new rule types, unit test execution and unit test compliance metrics will change. Reports on automated unit testing of the customer application decrease due to the increased pool of supported rules.
What steps are required to update the application to be compatible with this change?
After a successful upgrade, create Pega unit test cases for the newly supported rules to see updated and accurate unit test metrics.
Data and integration troubleshooting enhancements
Valid from Pega Version 8.3
Identify how data is loaded in user interface (UI) elements, discover the data sources used, and navigate to the relevant rules by using the new Live Data tool. Use the Live Data tool to quickly troubleshoot data and integrations by providing data page information or autopopulate properties from the UI without searching through the clipboard.
For more information, see Troubleshooting data in UI elements.
Retrieve a flat list of fields from Pega Digital Experience APIs
Valid from Pega Version 8.3
You can now use the flatListOfFields parameter to retrieve a list of the fields in a case or flow action. With this parameter, you avoid parsing all the layout information for the Pega Digital Experience API, making it easier for you to see only what you need to build your user interface.
The following Pega Digital Experience APIs support the flatListOfFields parameter:
- GET /casetypes/{ID}
- GET /assignments/{ID}/actions/{actionID}
- GET /cases/{ID}/actions/{actionID}
For more information, see Retrieve a flat list of fields from Pega APIs.
Customized application overview documents in App Studio
Valid from Pega Version 8.3
Keep stakeholders notified of the status of an application by customizing and generating an application overview document in App Studio. The overview may include information such as case types, roles, features in your application, and more. Select the chapters that you want to include in the overview, and then highlight the most relevant information by ordering the chapters. In addition to the application overview document, you can generate a detailed data model, either in Microsoft Word or Excel format.
For more information, see Creating project documents for stakeholders in App Studio, Exporting a data model into a document.
Attachment migration from Pega database storage to a repository
Valid from Pega Version 8.3
You can now migrate case attachments from Pega database storage to a repository by using a wizard from Pega Platform™. This ability is useful, for example, when you migrate from an on-premises deployment to a Pega Cloud Services environment and you want to reduce the size of your Pega database and manage all your case attachments in a single location.
For more information, see Migrating case attachments to a repository.
New send email automations and enhancements
Valid from Pega Version 8.3
You can now configure cases, flows, and activities to compose and send guardrail-compliant emails that conform to the MIME standard by using email automations. Use the new Call-Automation method to call an automation from an activity without writing Java.
You can also now categorize error messages in automations to quickly understand the type of error that occurred. In addition, page list data types are now supported for inputs and outputs in automations.
For more information, see Calling an automation from an activity and Viewing automations.
Specify a queue of user operations in Pega Digital Experience APIs
Valid from Pega Version 8.3
You can now specify a queue of page instructions for user operations on embedded pages, page lists, and page groups in Pega Digital Experience APIs. The page instructions allow your client application to more accurately model users’ actions.
Pega Digital Experience APIs support the following operations:
- For embedded pages:
DELETE
,REPLACE
, andUPDATE
. - For page lists:
DELETE
,REPLACE
,UPDATE
,APPEND
,INSERT
, andMOVE
. - For page groups:
DELETE
,REPLACE
,UPDATE
, andADD
.
For more information, see Page-related operation queuing with page instructions in Pega APIs.