Published Release Notes

Customizations to the prlogging.xml file must be manually ported after upgrade

As a result of the upgrade from the Apache Log4j 1 logging service to the Apache Log4j 2 logging service, the name of the logging configuration file has changed from prlogging.xml to prlog4j2.xml and the format of the file has changed considerably. If you customized your prlogging.xml file, port the customizations to the new prlog4j2.xml file. If you do not port the changes, the Pega^® Platform uses the default prlog4j2.xml file and disregards your customized prlogging.xml file.

For more information about customizing your log files, see the Apache Log4j 2 documentation.

Socket server has changed for remote logging

As a result of the upgrade from the Apache Log4j 1 logging service to the Apache Log4j 2 logging service, the socket server that is used for remote logging has changed from the Log4j remote logging package with the LogFactor5 log analysis tool to TcpSocketServer. If you use remote logging, update your socket server to TcpSocketServer. For more information, see Installing and using remote logging.

Consistent authoring experience for sections

Section references inside a dynamic layout have the same configuration options as a top-level section within a section (section include). Section references reduce the need for included sections, reduce the size of the document object model (DOM), and provide a more consistent authoring experience. You can specify a container format, set view and update privileges, and defer content load for sections within or outside of a dynamic layout. For more information see Harness and Section forms - Adding a section.

Refer to mixin settings in override CSS

You can refer to mixin settings inside an override CSS, which makes it easier to maintain and restyle your application. Properties for typography, border, background, and combination mixins can be referenced in an override CSS. For more information see Mixins in an override CSS.

Tour IDs and Test IDs in UI controls

Many UI controls now support the Test ID and Tour ID fields in the General tab of the layout properties. The Test ID setting generates a data-test-id attribute to provide a fixed reference to a UI control for automated testing. You can use Tour IDs to create a guided tour of your user interface for users. For more information, see Test ID and Tour ID for unique identification of UI elements.

Test IDs and Tour IDs have been extended to the following UI controls.

Both Test IDs and Tour IDs are supported in the following types of controls:

• Autocomplete
• Button
• Check box
• Date time
• Drop-down
• Formatted text
• Icon
• Label
• Link
• Radio button
• Text area
• Text input

Test IDs are supported in the following controls:

• Grid
• Hidden text
• Tree
• Tree grid

Tour IDs are supported in:

• Dynamic layouts

Custom domain names in Pega Cloud

For your applications hosted on Pega® Cloud, you can use a custom domain name that conforms to your enterprise standards. By using a custom domain name, users of your Pega Cloud-hosted applications see domain names that are familiar to them.

For more information, see Requesting a custom domain name for applications hosted on Pega Cloud.

This functionality is available as of QII 2017.

Automatically process cases with SharePoint

You can now use Microsoft SharePoint Online to store and source case and Pulse attachments and to store and source attachments during automated case processing. Users only have to provide authentication and authorization details the first time they access SharePoint Online or when the trust has expired. The authentication profile must be OAuth 2.0 with a grant type of authorization code. The SharePoint Online component can be downloaded from Pega Exchange. For more information, see Downloading and configuring pluggable content management components.

Flexbox support for all default layouts

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.

Ability to set default values when importing data

You can now set default values for data that you import for a data type from a .csv file. By setting defaults, you can ensure that even when the .csv file data is incomplete, all of the data is imported. In addition, you can set default values for custom fields that do not have a matching source column in the .csv file. This feature is available for the Add and update and Add only import options. For mapped fields, the default value is used for new records if the source field is blank, and for existing records if both the source and target fields are blank. For custom fields, the default value is used for new records if a default value is provided, and for existing records only if the target field is blank.

For more information, see Importing data for a data type.

Support for Amazon Web Services Direct Connect

Pega® Cloud supports the Amazon Web Services (AWS) Direct Connect service between your Pega Cloud virtual private cloud (VPC) and your physical infrastructure within a geographical region without need for a virtual private network (VPN). Use this service to connect to:

• A data center provider that is located with AWS within the same geographical region.
• A multiprotocol label switching (MPLS) network or other type of wide area network (WAN).

For more information, see Configuring Amazon Web Services (AWS) Direct Connect in your Pega Cloud virtual private cloud.

This functionality is available as of QII 2016.