Support for configuring and saving external data in App Studio
Valid from Pega Version 8.6
You can now configure a savable data plan to easily replace or update related data directly from App Studio, and persist those changes during the case lifecycle. This enhancement allows you to work directly in App Studio, without being limited to read-only access of data from case types.
Automation performance enhancements
Valid from Pega Version 8.6
To improve the performance of automation-based REST services and DX APIs, you can now configure JSON inputs and outputs in automation rules. The automation passes the JSON object directly to an automation-based REST service or DX API, eliminating the need to transform data on a page to JSON first. You can also take advantage of this enhancement if you are calling an automation from an activity. Additionally, you can simulate a JSON response in the automation rule and update the JSON sample if needed.
For more information, see <link TBD> and <link TBD>.
Cosmos React-UI supports custom authentication
Valid from Pega Version 8.6
Pega Platform™ now supports custom authentication in applications that use Cosmos React-UI. Depending on the needs of your users and the functionality of your application, you might need to write custom authentication schemes to meet specific requirements.
Clients that use custom authentication in their applications can now take advantage of the Cosmos React-UI.
For more information, see Securing Cosmos React-UI applications.
Support for creating automations
Valid from Pega Version 8.6
You can now create automations in Pega Platform. By creating an automation, you clearly define a contract to perform a specific task. For example, you can create an automation that retrieves a list of data objects that are available in the application.
For more information, see Creating an automation.
Support for filtering requests and responses in activity-based REST services
Valid from Pega Version 8.6
You can now use a JSON data transform to filter inputs and outputs in activity-based REST services. With this enhancement, you maintain high performance by filtering unnecessary properties from the REST service request and response.
For more information, see Creating a request for POST, PUT, and PATCH methods by using an activity implementation and Creating a response for Service REST methods by using an activity implementation.
Tracer file size limit to prevent disk usage issues
Valid from Pega Version 8.6
The maximum size of files with event details that Tracer generates is now 10 GB to avoid excessive disk usage and performance issues. Tracer applies the size limit at the node-level, so every node that runs in your system can use up to 10 GB of disk space to create an output file with event details. As a result, you can monitor the health of your system and deliver issue-free applications without experiencing disk space problems.
For more information, see:
- Avoid performance issues when monitoring applications with size limit for Tracer files (8.6)
- Tracer disk usage FAQ
Support for configuring data sources by using OpenAPI Specification
Valid from Pega Version 8.6
The Integration Designer in App Studio now supports OpenAPI Specification. You can provide an OpenAPI Specification endpoint or upload a YAML file to automatically generate data sources according to the specification. With this enhancement, you avoid having to manually create a representative sample JSON request and response, saving you time and increasing productivity.
For more information, see Integrating with a REST API by using OpenAPI Specification.
Integration and security tab now divided into two tabs
Valid from Pega Version 8.6
The Integration and Security tab is now two separate tabs on the form: Integration and Security. While the content of these two tabs are related, they function more effectively as separate tabs. The Security tab now includes the Authentication section, so you can add existing authentication services to your Application Definition to more effectively manage the security of your application.
For more information, see Security tab of the Application Definition.
Nested conditions visible in the condition builder
Valid from Pega Version 8.6
Condition builder now supports the option to view nested conditions in a read-only mode, so that you can conveniently analyze and understand logic in your application. For example, if you create a condition that uses another When condition rule as a value to compare at run time, you can preview the configuration of that When condition. You can use this feature with When conditions nested at multiple levels, so that you can analyze even complex logic in your application.
For more information, see Defining conditions in the condition builder.
More detailed configuration of persona access in App Studio
Valid from Pega Version 8.6
App Studio now supports more precise configuration of access for personas so that you can improve the security and usability of your application. You can now define what actions a given persona can perform on a case, a data object, or a configuration set. You also save time because you define settings for an entire group of users that a persona represents. For example, you can configure a customer service representative (CSR) persona to view only cases that process insurance claims from VIP customers, without the option to modify the cases. As a result, you ensure that users of your application can interact only with relevant data, in a way that best meets your business needs.
For more information, see:
- Manage access for personas more efficiently in App Studio (8.6)
- Configuring access options for a persona