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.
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.
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.
DB2-LUW database logfile size increase
Valid from Pega Version 7.1.5
To avoid running out of logfile space due to large transaction sets during the rule base load of a Pega 7.1.x install, upgrade, or maintenance level update, systems supported by a DB2-LUW database platform should increase the LOGFILSIZ parameter to at least 4096 pages from the default size of 1000 pages.
After the size has been increased, restart the database to ensure that the new setting is loaded into the database correctly.
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.
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.
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.
No direct upgrade to multitenant setup
Valid from Pega Version 7.1.1
It is not possible to upgrade directly to a multi-tenant setup. A Pega 7 application may be exported and then imported into a multi-tenant system, with the administrator making the decision as to whether this then becomes a tenant system or a shared system.
Applications developed in versions prior to Pega 7 must be upgraded to a Pega 7 standard system, and then exported and imported into a multi-tenant system. See the Multitenancy Administration Guide for full details.
Redesigned Attachment Categories tab
Valid from Pega Version 7.1.5
The Attachment Categories tab on the case type record has been redesigned as follows:
- In the Category field, you can associate case types with a case by selecting one in the application ruleset stack, or create a new one by typing a name in the field.
When you add a category to the list and save the record, the system automatically generates a page list property that that can be used to easily reference attachments by category.
In the example shown below, the page list property AuditComplianceAttachments can be used to access a list of attachments in the Audit Compliance category.
For ease of use during your design session, you can access this functionality using the "Attachments" option on the Case Designer Details tab.
The new function alias pxIsAttachmentOfCategoryInCase checks if an attachment of a particular category is attached to a case.
- Auto-Attach capabilities are deprecated but still supported. The tab displays a read-only list of attachments that were configured with this feature in previous releases.
- To remove this capability, delete the item.
- For new development, use the Attach Content smart shape in your process diagram.
Geolocation tracking for the latest mobile client
Valid from Pega Version 8
The latest version of Pega Mobile Client™ now supports geolocation tracking for offline-enabled mobile apps. You can enable constant tracking when users work on specific cases from their worklists. This enhancement helps audit the trail of the case and increase the efficiency of your mobile users. For example, dispatchers at headquarters can track the routes of field workers and more effectively assign them tasks based on their current location.
For more information, see Tracking mobile users based on geolocation data.