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:
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.
Need to run script before updating Multitenant systems
Valid from Pega Version 7.1.5
When updating or upgrading a Multitenant system from Pega 7.1.5 or 7.1.6 to Pega 7.1.7, if that system uses either an Oracle or a PostgreSQL database, you may encounter the error:
“Table must be empty to add column.”
The Multitenant architecture requires an additional column on a number of the PRPC database tables (“pzTenantID”). In Pega 7.1.7, two additional PRPC tables were tenant-qualified: pc_schedule_task and pr_index_schedule_task. The Multitenant column is added to these tables by the update/upgrade process. However, Oracle and PostgreSQL do not allow the addition of a non-null column to an existing table unless the table is empty, so updating or upgrading systems on those databases displays the error detailed above.
To avoid this error, before beginning the update or upgrade, it is necessary to run a script:
- Oracle —
OracleMTupgrade.sql
- PostgreSQL —
PostgresMTupgrade.sql
For updates, these scripts are located in the /scripts/ddl
directory.
For upgrades, these scripts are located in the /Resourcekit/AdditionalUpgradeScripts
directory.
Use Page-Change-Class method to change a Page class
Valid from Pega Version 8.3
With the release of Pega Platform™ 8.3, using the Property-Set method to change the Page class shows a guardrail warning. Use the Page-Change-Class method to change the Page class instead.
For more information about the Page-Change-Class method, see Changing the class of a page and Page-Change-Class method.
Support for the decisioning-enabled NLP text analyzer in IVAs and Email Bots
Valid from Pega Version 8.3
You can now use the new intelligent natural language processing (iNLP) text analyzer in Pega Intelligent Virtual Assistants™ (IVAs) and Pega Email Bots™. This advanced text analyzer is decisioning-enabled and empowers IVA or Email Bot for all conversational channels to provide smarter responses. The decisioning capability in the system integrates text analytics with strategies, prepositions, and interaction history, to provide the context for making better next-best-action decisions.
For more information, see Use the decisioning-enabled NLP text analyzer in IVAs and Email Bots, Defining advanced Facebook text analyzer configuration and Facebook channel behavior.
Upgrade impact
Existing channels remain with the current configuration, and their current functionality does not change. Channels created after the upgrade automatically use the new text analyzer.
What steps are required to update the application to be compatible with this change?
The new text analyzer is enabled or disabled using a new interactive API (iAPI) selection, which is selected by default for new channels. You can disable the iAPI for new channels if you want to maintain current functionality. You can also enable it for existing channels if you want to move existing channels to the new functionality.
CyberArk password vault support added for Pega database
Valid from Pega Version 8.3
With the CyberArk password vault, you can store your systems' passwords in a secure, central location and retrieve them from that location instead of directly entering credentials into the systems. This support is available only for IBM WebSphere environments.
For more information, see Pega Platform deployment guides.
Support added for multiple mashups
Valid from Pega Version 8.3
You can now include multiple mashups on a single webpage or browser, even if the mashups have different application and authentication requirements. Use mashups to embed a Pega Platform™ application as a gadget on your website. For example, you can embed Web Chatbot and Self-Service Advisor on the same website.
For more information about mashups, see Configuring the Mashup channel.