Add additional columns to customized work history tables
Valid from Pega Version 7.1.6
The standard work history table, pc_history_work, contains two new columns that return the latitude and longitude coordinate location of the action that prompted the history. Mobile devices can display this location as a street address. If you have a customized work history table, add these two columns to it:
<decimal name="pxLatitude" size="19" scale="9"/><decimal name="pxLongitude" size="19" scale="9"/>
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
Microsof Internet Explorer 9 (IE9) may display a script error when clicking a Help button
Valid from Pega Version 7.1.6
A script error may be displayed when clicking a Help button when script error notification is turned on in the browser. As a work around, uncheck the Display a notification about every script error option in the Advanced tab of the Options dialog box in Microsoft Internet Explorer 9.
Support for encrypted traffic in a cluster
Valid from Pega Version 7.3
The Pega 7 Platform includes the Ignite platform, which supports encryption for intra-cluster communications. You can now configure encryption for intra-cluster traffic for compliance with regulatory or organizational security requirements.
For more information, see Enabling encrypted traffic between nodes.
Deploy revisions directly in target environments
Valid from Pega Version 7.3
As a revision manager, you can now directly deploy or migrate completed revisions to multiple Pega 7 Platform environments that were configured as targets by the system architect. The revision management process is faster because you do not need to package a revision as a JAR file, and then manually import that file to the Pega 7 Platform. Additionally, this solution gives business users more control over application rulesets and enables them to act more independently.
For more information, see Direct deployment of revisions.
Batch database processing improvements
Valid from Pega Version 7.3
Batch database processing has been enhanced to ensure that a constraint violation does not occur when you save transactions to a table with a foreign key dependency. Because batch processing changes the order of save operations, it is disabled for transactions with foreign key dependencies. Disabling batch processing ensures that a record with a foreign key dependency on another record will not be written before the record on which it is dependent.
For more information about how batch database processing works and how to enable and disable it, see Batch processing during database write operations.
Operator presence record tracks disconnected status of operators
Valid from Pega Version 7.3
The state attribute in the operator presence record now tracks the operator connection status of DISCONNECTED, in addition to tracking the operator connection status of ACTIVE, AWAY, or OFFLINE. Operators are disconnected if their browser crashes, if they close a browser session without logging out of the system, or if the network connection is down. The DISCONNECTED status helps prevent work from being routed to operators who are not online or not available.
When the operator restores the browser session or the network connection is restored, the Pega® Platform updates the operator connection status to ACTIVE.
For more information, see Tracking the online presence of operators.