Set a time zone for the DateTime control
Valid from Pega Version 8.3
The DateTime control now supports the selection of a specific time zone. Apart from the default local time zone, you can choose a Java-supported time zone or enter a property. For example, you can make it easier for a manager working in New York to schedule a task for a worker in London by configuring a calendar picker on user forms to show a date and time for Europe/London.
Beginning with this release, the calendar picker defaults to the current time in the time zone that is defined in the operator record. Previously, it defaulted to the local time zone of the system.
For more information, see Specifying a time zone for a DateTime control.
Upgrade impact
After a successful upgrade, the DateTime gadget displays the time in the current operator's locale, which is defined on the operator rule form or in the browser.
What steps are required to update the application to be compatible with this change?
If you need to display the system time from which the user has logged in, and if this is not the same as the time in the user's locale (based on the browser setting), set the Locale field in the operator ID to be blank so that the browser-based setting and the displayed time are the same as the system time.
Support for controlling simulations in Integration Designer
Valid from Pega Version 8.3
Integration Designer now supports toggling an existing simulation for a data source on and off, and supports creating a simulation when a data source does not have a simulation configured. By simulating a data source, you can continue developing an application when your integration is not available, and test an application independently from the integration.
For more information, see Managing data and integrations with the Integration Designer.
Improved access to Cosmos UI settings
Valid from Pega Version 8.5
The Settings tab in the App Studio case designer now includes tools for configuring Cosmos UI. With this enhancement, you can adjust design system settings without the need to specialize individual When rules in Dev Studio, which simplifies UI creation and saves development time.
For more information, see Managing Cosmos UI settings in case designer.
Ability to restrict access to the Import wizard
Valid from Pega Version 8.5
You can now restrict access to the Import wizard so that users implement an automated pipeline to deploy changes between environments such as staging and production. Deployment Manager is one method by which to create pipelines. By using pipelines to propagate changes, users can apply a standardized and automated deployment process for migrating their applications.
For more information, see:
- Ensuring that users migrate applications with a pipeline by restricting the Import wizard
- Understanding model-driven DevOps with Deployment Manager
Improved control of case locking and retry mechanisms
Valid from Pega Version 8.3
The Delay factor, Initial delay in minutes, and Max retry attempts fields have been added to queue processors, and the Timeout to acquire lock field has been added to the Queue-For-Processing
method. Using these fields, you can quickly configure background processes that require you to lock cases or retry case processing.
For more information, see Creating a Queue Processor rule.
Upgrade impact
After a successful upgrade, the new fields contain their default values.
What steps are required to update the application to be compatible with this change?
To customize the functionality of this feature (and the new fields), open the Queue-For-Processing
definition and modify the values for the new properties or fields.
Update access groups from the command line
Valid from Pega Version 7.2.2
Remotely update access groups by using the prpcServiceUtils tool. This feature is useful in automated deployment scenarios when you want to provide access to a new application version.
For more information, see Updating access groups from the command line.
Role-based page access in App Studio
Valid from Pega Version 8.3
App Studio now supports the management of access to pages in your application based on user roles. You can use this functionality to define which pages are visible for every role, for example, make an analytics page available only to an administrator.
For more information, see Configuring role-based page access.
Custom DX API attributes for auto-generated controls
Valid from Pega Version 8.5
Auto-generated controls now include the option to add custom attributes for use with the Pega Digital Experience (DX) API. The attributes are part of the DX API response to the front end and you can use them to modify the run-time behavior of the UI elements in your application. For example, you can add an attribute to a field that displays a tooltip text for that field at run time. This enhancement introduces significant flexibility to application development and gives you greater control over UI components.
For more information, see Adding custom attributes for version 1 DX API to auto-generated controls.
Access PegaUnit compliance metrics from a centralized location
Valid from Pega Version 8.5
PegaUnit compliance metrics and execution rate have been added to the PegaUnit metrics tile of the Application Quality dashboard. This dashboard provides a centralized location for all PegaUnit data for a specific application.
The dashboard also supports granular PegaUnit test information for each case type and data type, similar to the process currently available on the branch quality dashboard.
For more information, see Analyzing application quality metrics.
New menu design options with the auto-generated menu control
Valid from Pega Version 7.1.7
Usability and responsive capabilities have been enhanced with a new auto-generated menu control offering multiple design options and configurations. New display options include text, descriptions, badges, and responsive vertical in-line menus. Loading options include:
- At screen load
- Defer load
- On first use
- On every use
Show menu controls for existing applications can be upgraded using the Upgrade Show Menu button in the HTML5 Readiness feature.
Menu created using the auto-generated menu control