MBeans deprecated in favor of Pega API
Valid from Pega Version 8.1
The use of MBeans for cluster management has been deprecated, although MBeans will continue to function for legacy deployments. The recommended best practice for automating system management is to use the Pega API. For more information, see Pega API.
Upgrading to the secure threading mechanism for email bots
Valid from Pega Version 8.1
In Pega Platform™ version 8.6, Pega Email Bot™ includes a more secure threading mechanism to help track emails from customers and other stakeholders in separate threads for an email triage case.
Upgrade impact
If you upgrade from Pega Platform version 8.5 or earlier, in which you configured an Email channel, perform the following steps to ensure that your system uses the new secure threading mechanism:
- Update the service email rule that the system uses to send an email reply as the initial acknowledgment.
- Update the email reply template in the data transform rule that the system uses when a customer service representative (CSR) sends the reply.
For more information about creating an initial acknowledgment email and email reply template, see Creating outbound email templates. For more information about the secure threading mechanism, see Use a secure threading mechanism in emails.
What steps are required to update the application to be compatible with this change?
For the initial acknowledgment email used by your email bot, update the service method for your email listener rule. On the Response tab for this service email rule, expand the Message contents section. In the Message data section, you specify the rule that defines the structure of the content of the email body. In Pega Platform version 8.6, you use for this purpose the pyEmailAcknowledgement correspondence rule that takes into account the selected built-in template. This template includes the security code tag that the system uses for the secure threading mechanism. If your application uses a different rule in the Message data section, update this definition to match one of the built-in correspondence template rules, for example, EmailAckTemplate_Clear.
The pySetEmailBotReplyTemplate data transform rule sets the name of the email correspondence rule that the system uses as the email reply template. If you do not want to use the default approach using the Classic, Cobalt, or Clear outbound email template themes, override this data transform rule to set the email correspondence rule name for the Param.ReplyTemplate target in the Source column field.
For more information about how to update the service email rule and the data transform rule to ensure that your system uses the secure threading mechanism, see Upgrading to the threading mechanism available in the 8.6 version.
Internet Explorer 11 support
Valid from Pega Version 7.1.5
7.1.5 now provides support for Internet Explorer 11 (IE11). For those customers interested in information about IE11 support in previous releases, refer to the Platform Support Guide.
Customize your report headers
Valid from Pega Version 7.1.5
You can customize the way that the header for all of an application's reports will be displayed by overriding the section pyReportEditorHeader. Save a copy of this section into the application's ruleset, then edit it to display the information, images, and layout that you desire. Once changes are saved, each of your application's reports will automatically use the updated header.
Guardrails compliance score
Valid from Pega Version 7.1.5
The Application Guardrails landing page has been enhanced to help you build more guardrail-compliant applications. Increase transparency and accountability on your projects by responding to the following compliance score metrics:
- A weighted compliance score (0-100) based on warnings, severity, and justification
- A percentage of compliant rules in your application
- Total number of rules in your application
- Total number of rules in your application with warnings (justified and unjustified)
Additional metrics include alert and interaction count trends over the last four weeks.
For more information, see Guardrails compliance score.
Automatically remove all inline styles
Valid from Pega Version 7.1.5
To ensure reusability and ease of maintenance, you can remove inline styles from all sections in all unlocked ruleset versions in your application from theSections Using Inline Styles section, click the Remove inline styles from all sections button.
landing page. In the
Automatically upgrade smart layouts to dynamic layouts
Valid from Pega Version 7.1.5
An automated command that upgrades from a smart layout to a dynamic layout is available in Designer Studio when creating new section layouts. Note that some smart layout configurations may not have a one-to-one correspondence with dynamic layouts, so these require some modification.
Advanced inline report filters
Valid from Pega Version 7.1.5
You can create a custom section and use it to display report filter controls at the top of the report, replacing the default display. The custom section can include basic controls (such as a drop-down menu or text entry field), and the controls can only provide values for the filter functions established in the Edit filters section of the Query tab for the Report Definition.
EAR support for JBoss EAP 6
Valid from Pega Version 7.1.5
PRPC deployment in JBoss EAP 6 as an EAR archive is now supported.
If you need to deploy the JBoss EAR file, go to My Support Portal and submit a Support Request. GCS can assist you with the procedure.
Format options in DateTime control
Valid from Pega Version 7.1.5
Several updates were made to the section and harness DateTime control.
First, this control now allows selection of both the MM/DD/YYYY and the DD/MM/YYYY format from the Date format dropdown menu.
Second, the number of characters used when inputting a date will be the same regardless of the date. For example, 1/1/2014 displays as 01/01/2014. In a data grid, this ensures that the date text in a column is aligned.
Third, you can now create a custom date format using the Java-supported custom date formats for both the Date or Date/Time types.
Following is an example of the new dropdown when selecting the type Date:
Following is an example of the new dropdown when selecting the type Date/Time:
Finally, as an example of custom date and time formatting, entering EEE, MMM D, YY H:MM A in the "Custom" field displays as Sat, May 1, '99 2:00 PM, as shown below: