Published Release Notes

Record Editor and data import enhancements

The Record Editor and Import wizard for data types have been enhanced to make the import process faster and easier to use. You can now perform the following tasks.

• Configure the Record Editor to use full-text search, which makes searching faster.
• Configure the location of the data import error file. For example, you can set the location to a shared location so that users can access the file from any node in a multinode system.
• Pass the keys of the records that were added, updated, or matched directly to custom postprocessing without additional database I/O.
• Search and filter records and export only the results instead of all records.
• Stop an import that is in progress.

Create email correspondence by using templates

You can configure email correspondence rules by using email templates. Email templates provide custom email formats for users and give developers a greater degree of customization in designing email correspondence. Select an email template on the Corr tab of a correspondence rule by clicking Edit mode and selecting Templated email from the menu. You can also create a section as an email template by clicking Email template on the Settings tab of the section form. For more information see Creating email correspondence by using a template.

New Java API improves JSON serialization

By using a Java API, you can serialize a Page or Property clipboard object to a JSON string for faster JSON serialization. You can also create a map between API responses and an application's internal data model that improves integration performance and maintainability.

For more information, see Using the mapping API for high-performance JSON serialization and Using the mapping API for high-performance JSON deserialization.

Actions available for custom controls

All standard actions that are available for autogenerated controls are available on non-autogenerated custom controls as well. You can configure actions on custom controls by using the legacy actions options or the standard options that are available to custom and autogenerated controls. By using the standard options, developers can now configure multiple action sets for different types of events on a single custom control.

For more information, see Actions tab.

Edit sections across Pega Express and Designer Studio

Sections created in Pega^® Express can be edited in Designer Studio, saved, and then reopened in Pega Express. This allows developers to create more complex, feature-rich sections and make them accessible to Pega Express users. In the section rule, you can convert template-based sections to full sections that no longer use a template.

For more information, see Harness and Section forms - Adding a section.

Style UI elements based on their state

You can style a control or component based on its state to give users a visual indication of an element's current state, without overriding the CSS file. The styles that you specified for each state (hover, focus, or active) are applied at run time.

For more information, see Styling UI elements based on their state.

Style radio buttons as segmented buttons

You can configure radio buttons to be displayed as segmented buttons. Segmented buttons display multiple button options in a compact format. Segmented buttons do not support vertical orientation. On the Presentation tab of the properties panel, set Control format to Other and select Segmented.

For more information, see Radio Buttons control properties – Presentation tab.

Text file rules support JavaScript and CSS validation

The Rule-File-Text rule form supports validation errors and warnings for JavaScript and CSS files. This support makes JavaScript and CSS code easier to maintain and allows you to follow best practices while editing the rule. Any JavaScript or CSS validation warnings generate a guardrail warning of moderate severity.

For more information, see Text File rules - JavaScript and CSS validation.

Log file description in web.xml incorrect after upgrade to Apache Log4j 2

As a result of the upgrade from the Apache Log4j 1 logging service to the Apache Log4j 2 logging service, it is recommended that you update the log file description in the web.xml file from location of prlogging.xml file to location of prlog4j2.xml file. The description indicates which log file is in use. Updating the description avoids confusion about which log file is current. Change the description as shown in the following example.

<resource-ref id="ResourceRef_5">
<description>location of prlog4j2.xml file</description>
<res-ref-name>url/pegarules.logging.configuration</res-ref-name>
<res-type>java.net.URL</res-type>
<res-auth>Container</res-auth>
<res-sharing-scope>Shareable</res-sharing-scope>
</resource-ref>

Apply logic to data import fields

When importing data from an external system, you can translate data fields into values that can be read by Pega^® Platform. From the Import wizard, you can do the following actions:

• Apply a decision tree or decision table to the data that is imported for a field.
• Use imported data for a field to look up a value in another record. For example, you can look up the key of a record that uses an external identifier to populate a foreign key field.
• Create templates that contain business logic, which eliminates the need to handle data transformations manually during preprocessing.

For more information, see Transforming data during import.