Published Release Notes

Changes to User Interface menu in Designer Studio

The User Interface menu in Designer Studio has changed. For example, menu options related to localization are now grouped under Application readiness.

For more information, see Designer Studio - Landing Pages.

Legacy landing pages removed

The following legacy landing pages and their links in the Designer Studio menu have been removed:

• Designer Studio > Data Model > Clipboard Pages > Data Pages
• Designer Studio > Data Model > Clipboard Pages > Undefined Pages
• Designer Studio > Data Model > Classes & Properties > Class Relationships

The streamlined Designer Studio menu facilitates locating and navigating to landing pages.

For information about the replacements for these landing pages, see Deprecated features.

Integrated Application Security Checklist helps you deploy a secure application

Pega^® Platform now provides an Application Security Checklist that you can refer to when you prepare your application for deployment. By completing the recommended tasks in this checklist, you can track your progress, access instructional information for tasks, and verify that your configurations are secure.

For more information, see Preparing your application for secure deployment, Compliance Score tab, Designer Studio — Home page.

Monitor application health on the Application Quality landing page

On the Application Quality landing page, you can view various quality-related data in one place so that you can monitor the quality of your application and correct any issues. The Application Quality landing page contains a summary of guardrails compliance, PegaUnit test coverage, and results of PegaUnit tests.

For more information, see Application Quality landing page.

PegaWAI ruleset deprecated in 8.5

Accessibility functions that were contained in the PegaWAI ruleset are now integrated into the main Pega Platform™. Consequently, the user interface in your applications now features accessibility functions out of the box, so you no longer need to use the PegaWAI ruleset to ensure accessible behavior in your application.

For more information, see Building an accessible UI.

Add the security checklist to applications created before 7.3.1

The security checklist is now automatically added to applications. You can manually add the security checklist to applications that were created in earlier versions.

You can improve the security of your application by completing the tasks on the checklist.

The following task reflects the procedure on how to manually add the security checklists to Designer Studio prior to 7.3.1:

1. In the header of Designer Studio, click the name of the application, and then click Definition.
2. Click the Documentation tab.
3. In the Application guides section, click Add guide.
4. In the Application guide& field, enter pxApplicationSecurityChecklist.
5. Click the Configure icon in the Available in column and select the portals (App Studio and Dev Studio) that you want to add the security checklist to.
6. Click Save.

Preview and select icons with the icon class picker

To see the standard, predefined icons that are available for a Button, Link, or Icon control, use the Open the icon class picker icon on the General tab of the Properties panel. From an overlay of icons, you can then select the one that is most appropriate for your control. By using a predefined icon, you bring greater consistency to your user interface and help users more easily understand the purpose of each control.

For more information, see Previewing and selecting predefined icons with the icon class picker.

Requestor pools management in Designer Studio

On the new Requestor Pools landing page, you can view and manage requestor pools across the cluster, including on the current node and remote nodes. By using this landing page, you can tune the requestor pools to improve the performance of services. You can clear the requestor pool for a service package and view the requestor pool basic metrics and configured thresholds.

For more information, see Requestor pools management, Clearing a requestor pool, Viewing details for a requestor pool, Tuning a requestor pool configuration.

Update activity for button and link formats

To update existing Button controls or Link controls to current, simplified formats (Strong, Standard, and Simple), use the pzUpdateButtonLinkFormats activity. Using the report definition and other parameters that you specify, the system retrieves the sections to be converted, loops through each section rule to find Button controls and Link controls, and updates their formats.

For more information, see Updated button and link formats and Update-Button-Link-Formats.

Support for application-specific REST API calls

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.