Enabling security policies now requires current password
Valid from Pega Version 7.1.3
As part of Pega’s initiative to protect against malicious attacks, the change password dialog has been enhanced. When Security Policies have been enabled for your system, new users or those with expired passwords will now be prompted for both their existing password as well as their desired new password.
For more details, review the Designer Studio > System > Settings > Security Policies landing page.
Tomcat log files moved to work directory
Valid from Pega Version 7.1.2
For Tomcat application server users, the default path for PRPC logs has been changed to the "work" directory for Catalina. For example:
<tomcat>\work\Catalina\localhost\prweb
This directory can be cleaned up during administration. To avoid loss of files, you can redirect logging to a different directory after installation:
- Navigate to the <tomcat-home>\webapps\prweb\WEB-INF\classes directory.
- Open the prlogging.xml file.
- Locate the "appender" definitions section that contains the "@{web.tmpdir}" string
- Update the FileNamePattern values to point to the new directory.
For more details, refer to the “Change the default path to PRPC logs” section in the Tomcat installation guide for your database.
Supported JDBC drivers
Valid from Pega Version 7.1.1
Pega 7.1.1 supports Java 6 and Java 7 SDKs only. Ensure that the JDBC driver you are using supports those versions of Java. See your database installation or upgrade documentation for additional information.
| Database | Java 6 | Java 7 |
|---|---|---|
| Oracle | ojdbc6.jar | ojdbc7.jar |
| MSQL | sqljdbc4.jar | sqljdbc4.jar |
| DB2 LUW | db2jcc4.jar | db2jcc4.jar |
| DB2 z/OS* | db2jcc4.jar or jdb2jcc.jar** | db2jcc4.jar |
| PostgreSQL | postgresql-9.1-903.jdbc4.jar*** | postgresql-9.1-903.jdbc4.jar |
* JDBC drivers are only available from the DB2 for z/OS product. Additionally, you need db2jcc_license_cisuz.jar in the same directory as db2jcc4.jar.
** The db2jcc.jar has been deprecated and may not be supported in future releases.
*** This .jar file is required for PostgreSQL version 9.1.x.
Deprecated end user portals
Valid from Pega Version 7.1.1
The following portals are no longer be supported:
- SysAdmDD
- WorkUserDD
- WorkManagerDD
As a best practice, customize standard, supported portals rather than update your existing portals to include new features.
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 thelanding page. In the Sections Using Inline Styles section, click the Remove inline styles from all sections button.
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.