Limited access for end user portals
Valid from Pega Version 7.1.1
The following portals are only accessible from supported versions of Internet Explorer in “quirks” mode:
- WorkUser
- WorkManager
Nesting dynamic containers not supported
Valid from Pega Version 7.1.1
Do not include a section containing a dynamic container inside of another dynamic container. This configuration may cause performance issues resulting in unexpected behavior at runtime, and is not supported.
All tabs are accessible on delegated rule forms
Valid from Pega Version 7.1.1
Delegates can now access all tabs in a delegated rule form.
You can continue to customize the development experience for delegated users, such as line managers, who may not require the full set of rule form options. For example, you can prevent users from adding new nodes on the Decision Tree form or using the expression builder on the Map Value form. All users, including delegated users, can remove these restrictions if they hold a rule-editing privilege.
For more details on this process and a list of commonly delegated rules, see How to delegate a rule.
Using Kerberos authentication with your database
Valid from Pega Version 7.1.1
Pega 7 supports Kerberos functionality. Kerberos is a computer network authentication protocol which allows nodes communicating over a non-secure network to prove their identity to one another in a secure manner.
To use Kerberos for authentication, you must use the command line to install or upgrade Pega 7.
To use Kerberos authentication:
1. Change the setupDatabase.properties file.
a. In the “Uncomment this property section” of the file, uncomment the jdbc.custom.connection.properties property. Based on your security infrastructure, different properties may be required as parameters to this property; provide the needed properties as semicolon-delimited name/value pairs:
jdbc.custom.connection.properties=prop1=val1;prop2=val2;prop3=val3;
Example: For an installation on a MSSQL database server from a Windows client machine (where both machines belong to the same Windows domain), using the Microsoft JDBC driver, the property may be set as follows:
jdbc.custom.connection.properties=integratedSecurity=true;
b. Comment out all the username and password properties where they occur in the jdbc.custom.connection.properties file, so that they appear as follows:
# pega.jdbc.username db username
# pega.jdbc.password db password
[lines removed here]
# pega.jdbc.username=ADMIN
# pega.jdbc.password=ADMIN
2. Set up your database to enable Kerberos functionality. This may include additional vendor-specific JDBC driver configuration, or other setup procedures. Check the documentation from your database vendor to determine what Kerberos setup is needed for your database.
3. Run the command line installation or upgrade by following the instructions found in the Pega 7 Deployment guides.
Run cleanup.bat/sh script only before upgrading
Valid from Pega Version 7.1.1
Prior to upgrading the rulebase, you can optionally run the cleanup.bat/sh script to remove older rules from the database.
Run this script before you upgrade your rulebase, or the script may delete needed rulesets. For more information about running the cleanup.bat/sh script, refer to the Upgrade Guide specific to your release version.
When using Oracle 12.1.0.1, left outer joins in reports may return incorrect results
Valid from Pega Version 7.1.1
When using Pega 7 with Oracle 12.1.0.1 , reports that use left outer joins may return incorrect results.
This is an Oracle known issue. To resolve this behavior, upgrade to Oracle 12.1.0.2, apply the Oracle patch 16726638 by requesting it directly from Oracle, or, for Microsoft Windows installations, apply Windows Bundle patch 12.1.0.1.15 or later.
For more information in this behavior, see: https://support.oracle.com/epmos/faces/DocumentDisplay?_afrLoop=392085808201943&id=1957943.1
Updated Word merge support with Microsoft Silverlight plug-in
Valid from Pega Version 7.1.3
Starting in this release, Pega 7 features that integrate with the Word merge capability are now cross-browser. ActiveX controls (which are only compatible with Internet Explorer) have been replaced with Microsoft Silverlight. This plug-in must be downloaded separately from Microsoft because it is not shipped with Pega 7.
Common features that are affected by this change include the Specification form and Case Type landing page.
Prior to using these features, see the release note Word merge support with Microsoft Silverlight plug-in for more information about setting up their client systems.
Support for Data streaming service for Pega Cloud Marketing 7.4 applications
Valid from Pega Version 2.1
Pega Cloud Marketing 7.4 applications support the Kafka-based Stream service featured in Pega Platform 7.4.
Naming pattern changed for file data sets
Valid from Pega Version 8.6.3
File data sets are used to import from and export data to a file repository. In case of data export, prior to version 8.6.3, the first file exported had the same file name that was provided by the user in the data set, and any subsequent file exported to the repository had a unique identifier appended to it. Starting in Pega Platform version 8.6.3, each file has a unique identifier, automatically generated based on the data flow node, thread ID, and timestamp.
Upgrade impact
If your process to consume output files expects files with a specific name, it may not be able to process the resulting files correctly.
What steps are required to update the application to be compatible with this change?
If you have configured the process before updating to Pega Platform version 8.6.3, but the exported files are no longer recognized by downstream processing logic after the upgrade, ensure that the downstream tool is configured to recognize the files by a pattern rather than the full name. For example, when referring to files exported to the repository, use the * character to indicate a pattern instead of using the full file name. For example, use Export*.csv to refer to the files.