Upgrade changes system name
Valid from Pega Version 7.1.1
As of Pega 7.1.7, the following renaming behavior no longer occurs.
The upgrade process renames your system to “PRPC” and modifies any custom requestor rules in your application to use this name. After the upgrade completes, you must apply these changes to revert your system:
- Identify all custom requestor rules (browser, batch, app, portal) with access groups that point to prior versions of PRPC.
- Open the relevant access groups (for example, PRPC:Unauthenticated and PRPC:Agents) and update the name and version fields to point to the current PegaRULES application.
- Reset your system name to its original value. You can set the Dynamic System Setting prconfig/identification/systemName/default or use the landing page.
- Restart the system.
Required DB2 settings
Valid from Pega Version 7.1.1
For customers using the DB2 Version 4 drivers (“db2jcc4.jar”), it is necessary to set the custom connection property useJDBC4ColumnNameAndLabelSemantics to “false”.
For customers using DB2 with WebSphere, the useJDBC4ColumnNameAndLabelSemantics property in the DB2 data source needs to be changed from a Boolean to an Integer and set to "2".
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.
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.
Small distribution kit
Valid from Pega Version 7.1.5
A new “small” release distribution format for Maintenance Levels (ML) is now available, designed to significantly increase adoption via:
- Minimal package size and faster download time
- Minimal install time via tactical changes to the upgrade implementation and process
This kit contains streamlined installers (both UI and command-line installers) and specialized error handling for ML updates (for example, a “small” kit will only work if an existing version of the same release is already installed).
The kit assembly has also been automated, which includes the construction of a PRPC_Rules.jar archive containing cumulative rules since the GA release.
A “small” kit will work for any prior ML release within a major release (for example, the “small” ML5 distribution kit will update any customer on 7.1 ML1 through 7.1 ML4).
Improved data page performance
Valid from Pega Version 7.1.5
Improvements have been made with queueing and processing of asynchronously-loaded data pages to reduce the number of calls to the database and avoid generating performance problems because of unneeded asynchronous requests.
Restricted SMA access
Valid from Pega Version 7.1.5
System Management Application (SMA) remote connections are not supported on JBoss EAP 6.x. This means SMA users may only monitor locally connected systems. Ensure that the "Local JVM Connection..." option is selected when configuring PRPC nodes:
Use "alternate database" as report source
Valid from Pega Version 7.1.6
You can opt to use the the "alternate database" identified in the Reports Database field of the Data-Admin-DB-Table instance that supports the Applies To class of a report as the source for the report. This reduces the load on the database that serves your application when you run the report.
PRServlet not required in PRPC URLs
Valid from Pega Version 7.1.6
PRServlet is no longer required in a URL when accessing PRPC. A URL typically written like this:
http://example.com/prweb/PRServlet?[QueryString]
Can instead be written like this:
http://example.com/prweb/?[QueryString]