Published Release Notes

Click, record, and play UI scenario tests

You can now record, edit, and run scenario-based UI tests in end-user portals. By using scenario-based tests, developers focus on testing an application's ability to deliver real business value instead of writing code. Developers can test autogenerated and custom controls, actions, and navigation in a specific case or in an entire portal. Test recording is available on the run-time toolbar, and tests are available on a unified landing page that provides easy access to them. For more information, see Find and fix issues by using the Accessibility Inspector.

Support for inline helper text for editable form fields

You can now configure inline helper text for editable form fields. The helper text is always visible on the form, and you can style the text to override the helper-text CSS class in the Override CSS file in the skin.

Providing helper text in editable form fields helps users complete forms more quickly and efficiently.

For more information, see Adding a Text Input control.

Optimized dynamic layout for sections with no container format or header

You can set dynamic layouts to use the new optimized layout mode. When optimized, the dynamic layouts that do not include a container format or a header no longer generate extra container and body DIVs. The depth of the Document Object Model (DOM) is reduced, which makes the layouts easier to maintain. Selecting this option also enables automatic updates for new markup with each release, so that you stay current with improvements to dynamic layout markup.

You can use an Upgrade tool to convert sections that use the legacy dynamic layouts to use the new optimized dynamic layout.

For more information, see Upgrading legacy dynamic layouts to use the optimized dynamic layout.

Add and manage landing pages in App Studio application menus

When working in App Studio, you can now create landing pages that are not directly associated with a case flow to make your application more informative. The landing pages are a good place to display the resources that are related to a case, images as well as text. Configure them to provide an overview of the work, workers, teams, reports, or any information that is available.

For more information, see Creating a landing page. 

Mobile apps now use custom-generated skeletons for page transitions

Mobile harnesses are now configured with custom-generated skeletons. Used during page transitions, skeletons render a temporary placeholder UI that closely matches the actual UI while data is being loaded from the data store. The use of skeletons enhances the user experience by providing a smooth transition while data is being loaded.

Skeleton transitions work with both dynamic and Ajax containers on the mobile client but work only with the Ajax container on tablets and desktops.

For more information, see Transition effects on actions.
 

Changes to the Attach Content control in Pega Client for Windows

Users who access offline-enabled Pega Platform™ applications from Pega Client for Windows can now use the Attach Content control within a case view to attach files with a native file picker control or take screenshots with a device camera. Images are immediately attached to the case, and image file names are based on a time stamp. If a device has no camera, the client skips the source selection step and the native file picker control opens.

For more information, see Harness and Sections forms – Adding an Attach Content control.

Manage test ID access with an access group role

Test IDs for user interface components are available only to users who have the PegaRULES:TestID role added to their access group. This requirement allows administrators to limit access to test IDs to users who create or run tests. At run time, applications do not include the test ID data for users without the PegaRULES:TestID role, which reduces the amount of code that is downloaded to the client.

For more information see Managing Test ID access with an access group role

Text file rules support the Google Closure Compiler

Text file rules support Google Closure Compiler as the default option for minification of JavaScript code. Minification reduces the size of JavaScript in text file rules for faster download. Access the Closure Compiler by selecting it in the Minification menu in a text file rule. For more information, see Text File rules - Completing the Main tab.

Date range option added to DateTime control

The autogenerated DateTime control, used in forms, now features a custom date range option in the calendar picker. To specify a time period, click the From date and To date fields on an interactive calendar overlay. This input method is both convenient and mobile-friendly.

Enhancements to the AJAX container

It is now possible to set a document limit for an AJAX container, between 2 and 16 to control the number of documents opened by users. To reduce development time, you can also choose a new option to have no default view. The multidocument mode features tabbed navigation so that users can switch between open documents. A tabless container, on the other hand, includes an out-of-the-box navigation action for Home, which helps application users move within the portal.

For more information, see Configuring the AJAX container.