Automate business process tracking by importing Excel files
Valid from Pega Version 8.5
To track business processes status and data, you can now import Excel files when you create a case or data object in App Studio. This functionality provides the following enhancements:
- You can now upload a CSV file when you create a case or data object in App Studio. By importing a CSV file, you can use the data in your spreadsheet to define your data model.
- You can generate a data import template that you can use to import a file in its original format during production.
- You can upload .xlsx files to avoid resaving your Excel file as a CSV file.
For more information, see Creating a data model from a spreadsheet.
Data APIs support data exploration in React UI tables
Valid from Pega Version 8.5
Data APIs have been enhanced to support filtering, sorting, paging, and aggregation in React UI tables. You can use that functionality to access your data quickly and intuitively. For example, by using paging, you can query a data page to retrieve the second page of an employee contact list and specify the number of results that are displayed on the page.
For more information, see Data API performance and limitations.
Support for application-specific REST API calls
Valid from Pega Version 8.5
You can now call an authenticated REST API in the context of any application that is listed on an operator record by using the application alias URL. With the application alias URL, you can also develop REST services without changing the access group in the service package. REST services run in the context of the access group that points to the provided application, instead of the access group that is specified in the service package.
For more information, see Invoking a REST service rule.
Failed Robotic Assignments work queue type changed to Standard
Valid from Pega Version 8.5
The default Failed Robotic Assignments work queue type is now Standard. In previous releases, the default type was Robotic. For usage information, see Configuring a work queue for robotic automation.
Upgrade impact
After upgrading to Pega Platform 8.5 and later, you cannot save case types in which you configure the Queue for robot smart shape to route new assignments to the Failed Robotic Assignments work queue. Existing assignments that you routed to the Failed Robotic Assignments work queue are not affected.
How do I update my application to be compatible with this change?
As a best practice, do not use the Failed Robotic Assignments work queue in your custom implementations. Instead, configure the Queue for robot smart shape to route new assignments to a Robotic work queue. When possible, update existing case types to use the robotic work queues that you created in your application.
Savable data pages support loading pages individually from a page list
Valid from Pega Version 8.5
You can now load individual pages in a page list from single object data pages to your case and data types. This functionality allows you to save autopopulated properties with the Load each page individually option using a flow action, save data page smart shape, or the activity method.
For more information, see Saving data in a data page as part of a flow.