Published Release Notes

Change logic does not work in Report Editor

The Report Editor​ change logic button does not work. As a workaround, use the rule form to change the logic.

Tomcat log files moved to work directory

For Tomcat application server users, the default path for PRPC logs has been changed to the "work" directory for Catalina. For example:

<tomcat>\work\Catalina\localhost\prweb

This directory can be cleaned up during administration. To avoid loss of files, you can redirect logging to a different directory after installation:

1. Navigate to the <tomcat-home>\webapps\prweb\WEB-INF\classes directory.
2. Open the prlogging.xml file.
3. Locate the "appender" definitions section that contains the "@{web.tmpdir}" string
4. Update the FileNamePattern values to point to the new directory.

For more details, refer to the “Change the default path to PRPC logs” section in the Tomcat installation guide for your database.

Slow WebSphere performance on Mac platforms

Use the following JVM setting to improve WebSphere performance on Mac platforms:

-Djava.net.preferIPv4Stack=true

Split schema systems require additional privileges

On Oracle split schema systems, add the following database privileges:

• Grant DROP ANY INDEX to the Admin User.
• Grant UNLIMITED TABLESPACE to the Rules User.

Use the Oracle Enterprise Manager to add these privileges or refer to the 7.1.3 Upgrade and Installation guides for Oracle.

Internet Explorer 11 support

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.

Customize your report headers

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.

Guardrails compliance score

The Application Guardrails landing page has been enhanced to help you build more guardrail-compliant applications. Increase transparency and accountability on your projects by responding to the following compliance score metrics:

• A weighted compliance score (0-100) based on warnings, severity, and justification
• A percentage of compliant rules in your application
• Total number of rules in your application
• Total number of rules in your application with warnings (justified and unjustified)

Additional metrics include alert and interaction count trends over the last four weeks.

For more information, see Guardrails compliance score.

Automatically remove all inline styles

To ensure reusability and ease of maintenance, you can remove inline styles from all sections in all unlocked ruleset versions in your application from the HTML Application Readiness landing page. In the Sections Using Inline Styles section, click the Remove inline styles from all sections button.

Automatically upgrade smart layouts to dynamic layouts

An automated command that upgrades from a smart layout to a dynamic layout is available in Designer Studio when creating new section layouts. Note that some smart layout configurations may not have a one-to-one correspondence with dynamic layouts, so these require some modification.

Advanced inline report filters

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.