The most current version of the engine code is used by default
Valid from Pega Version 7.1.7
Beginning in Pega 7.1.7, the "com.pega.pegarules.bootstrap.codeset.version.Pega-EngineCode" setting is removed from the prbootstrap.properties file. By default, Pega 7.1.7 uses the most current version of the code present in the system.
Update Existing Applications wizard will run for every upgrade
Valid from Pega Version 7.1.7
The upgrade process from a PRPC 5.x or 6.x system to Pega 7.1.7 now automatically runs the Update Existing Applications wizard. This may extend the time that the upgrade process takes to complete, depending on the version you are upgrading from and the number of rules in your application.
Upgrading to Pega 7.1.7 with an Oracle database requires new role permissions
Valid from Pega Version 7.1.7
When upgrading or updating from a prior version to Pega 7.1.7, if your system uses an Oracle database, an additional role is required to support the Reversability functionality. In addition to the Oracle privileges specified in the Install Guides, the role SELECT_CATALOG_ROLE is required. Verify that this role is present before beginning the upgrade or update.
IBM WebSphere Application Server V8: Edit the URL for Enabling System Management Application
Valid from Pega Version 7.1.7
WebSphere 8 does not correctly resolve the URL to enable System Management Application. As a workaround, when you configure the application server, you can do either of these actions:
Enter the full URL in the format:
http://hostname:port/prsysmgmt/getnodes.action- Set the com.ibm.ws.webcontainer.redirectcontextroot property to true.
Flow import functionality is limited to Microsoft Internet Explorer Version 9 and Version 10 in Pegasystems Public Format
Valid from Pega Version 7.1.7
Importing a flow in the Rule-from-File wizard is limited to Microsoft Internet Explorer 9 and Internet Explorer 10 in the Pegasystems Public Format .
Improved cross-browser support
Valid from Pega Version 7.1.7
All rule forms are now harness-based and open in the work area of Designer Studio. This means that you can develop in the browser of your choice, free from pop-up distractions and incompatibility messages. Many rule forms have been upgraded to use the latest layouts, styles, and design best practices, giving you a consistent development experience.
Viewing a Word Template in Pega 7.1.7 compared with Pega 7.1.6
Previous restrictions still apply to any deprecated or custom rule forms in your application that remain form-based. Refer to the Deprecated features list for guidance on how to upgrade these forms and recommended alternatives.
Changes to archive.info in Pega 7.1.7
Valid from Pega Version 7.1.7
In Pega 7.1.7, the contents of the archive.info file have changed.
- In versions Pega 7.1.6 and earlier, the archive.info file displays the build number of the Pega installation.
- As of Pega 7.1.7, the build number no longer appears in the archive.info file.
In Pega 7.1.7, the archive.info file only displays a status message indicating whether or not the system is running, and the build number no longer appears. Instead, if the system is operational, the message “status=Running” displays in the archive.info file.
If there are any automated tests, scripts, or applications that rely on the archive.info file displaying the build number, those may fail and produce an error. It is recommended that any automation that relies on the build number displaying in the archive.info file be changed to look for the “status=Running” message.
Quickly see what's new in Pega 7.1.7
Valid from Pega Version 7.1.7
A new home page panel gives you centralized access to Help and the PDN, eliminating the need to leave Designer Studio. Use the buttons in this panel to learn about new features quickly and stay connected to product announcements.
What’s new panel as it appears on the Designer Studio home page
After you are finished reviewing new features and enhancements, you can dismiss the What’s new panel. This hides the panel from your operator in future sessions without impacting the home page for other application users.
Clear and actionable guardrails help you mitigate risk sooner
Valid from Pega Version 7.1.7
The Application Guardrails landing page has been restructured to give you an executive-level view into your application health. Use the available metrics and tools on each tab to understand the scope of warnings in your application, the operators responsible for introducing this risk, and ways to improve your compliance score before your development goes into production.
Include this landing page in your governance process to:
- Understand your application compliance score and how it has changed over time:
A score of 90 or greater indicates your application is in good standing.
A score of 80-89 indicates your application needs review for improvement.
A score below 80 requires immediate action.
- Investigate the factors contributing to your score, such as warning age or severity, and the rules and operators associated with each warning.
- Review a comprehensive list of warnings and the recommended path to resolve them.
- Communicate all of these details to project stakeholders through email or exported documents.
Available metrics on the Compliance Details tab of the Application Guardrails landing page
The Charts tab in this landing page has been superseded by the Compliance Details tab, which provides more options and an enhanced presentation.
For more information about the available features on all tabs in this landing page, see Application Guardrails landing page.
Rollback functionality is limited to latest revision
Valid from Pega Version 7.1.7
The rollback functionality in DSM Revision Manager allows customers to roll back the import of the latest revision to their DSM application. Only one rollback is allowed; after a rollback, the rollback option is disabled until the next revision is imported. If importing two (or more) revisions at once then attempting a rollback, the system only rolls back one revision.
Example: a user has a base DSM application. They import Revision 1, and then import Revision 2. Next, they try to roll back both revisions. The system reverts to the Revision 1 version of the application, and the customer cannot revert all the way back to the base application.