Microsoft Silverlight no longer supported in Mozilla Firefox 52
Valid from Pega Version 7.3
Beginning with Mozilla Firefox 52, Firefox no longer supports NPAPI-based browser plug-ins, including Microsoft Silverlight. Pega Platform features that use Silverlight, such as merging case data into a Microsoft Word template, no longer work.
For more information, see End of Support for Microsoft Silverlight in Mozilla Firefox 52.
Nodes in a cluster do not see each other for Docker, multiple VMs, or multiple NICs setup
Valid from Pega Version 7.3
If a cluster is set up in Docker, or uses separate virtual machines (VMs) or multiple network interfaces, you must set the public address in the prconfig.xml file for each Pega® Platform node to avoid problems with node clustering. Add the <env name=”identification/cluster/public/address” value=”IP address”/> setting to specify the public address that is used by each node.
Support for round icons in Android 7.1 mobile apps
Valid from Pega Version 7.3
To improve the look and feel of Android mobile apps, round icons are now supported in apps that are created for Android 7.1. You can add the icons to the assets.zip file during the customization stage when you build the app in the Pega® Platform.
For more information, see Branding mobile apps.
Select multiple nodes for the Adaptive Decision Manager service
Valid from Pega Version 7.3
You can select multiple Pega Platform nodes and assign them to the Adaptive Decision Manager (ADM) service as worker nodes. Adaptive learning is no longer restricted to a single server, which provides resilience and scalability. You can add or remove nodes from the ADM service while the system processes customer responses.
For more information, see Changes to Adaptive Decision Manager.
Cross-origin resource sharing (CORS) policies for APIs and REST services
Valid from Pega Version 7.3
You can now use cross-origin resource sharing (CORS) policies to control how external systems and websites (origins) are permitted to access resources such as APIs and services within your applications. For example, Pega® Platform uses CORS policies to restrict which Pega Robotic client applications can connect to your Pega applications, and to limit which mobile apps can call Pega mobile services. Using CORS policies results in reduced cost and implementation times, while providing increased security when other systems or websites interact with your application.
For more information, see Creating a cross-origin resource sharing (CORS) policy and Mapping an endpoint to a cross-origin resource sharing (CORS) policy.
Flexbox support for all default layouts
Valid from Pega Version 7.3
To improve scalability, Pega Platform supports flexbox-based layouts by default in all its screen and column layouts and layout groups. You can convert existing layouts to flexbox-based layouts by selecting the Optimized code option on the Presentation tab of the layout.
For more information, see Screen Layout Properties.
Create pre-import and post-import steps
Valid from Pega Version 7.3
To take specific actions based on archive metadata, add pre-import and post-import action steps to collections. For example, you can configure a pre-import activity to automatically verify that an archive meets certain criteria before you import the archive. If the archive does not meet the criteria, Pega® Platform does not import the archive.
For more information, see Pre-import and post-import collections.
Capture real-time feedback with Agile Workbench
Valid from Pega Version 7.3
Project stakeholders can use the new Agile Workbench tool to capture real-time feedback directly in an application, which can increase the efficiency of application development. You capture feedback by creating a user story, bug, or feedback item, and these work items can include video recordings of screens, annotated screen captures, file attachments, or URLs. In Designer Studio, you can configure Agile Workbench to integrate with Pega® Agile Studio so that bugs and user stories are synchronized between the two systems.
For more information, see:
- Pega Express 7.3 – Agile Workbench
- Pega Platform 7.3 – Agile Workbench
Multistatus case dependencies replace custom implementations
Valid from Pega Version 7.3
You can now quickly define a case dependency that supports variations of a resolved status, such as Resolved-Completed and Resolved-Rejected. Because the definition of a resolved case now includes all status values that start with the word “Resolved,” you can replace custom logic in your application with a Wait shape that you configure in a flow.
For more information about defining a case dependency, see:
- Pega Platform - Pausing a process in a case
- Pega Express - Pausing a process in a case
Improved interactions for email and Pulse
Valid from Pega Version 7.3
You can now continue a discussion that was initiated by email when you post a message to Pulse or reply to an email message. By providing a consistent thread of discussion in a case, you can keep stakeholders informed while allowing them to use the communication channel of their preference.
For more information about the communication interchange that occurs when you initiate a discussion, see:
- Pega Express 7.3 - Email instantiation
- Pega Platform 7.3 - Email instantiation