Add the security checklist to applications created before 7.3.1
Valid from Pega Version 7.3.1
The security checklist is now automatically added to applications. You can manually add the security checklist to applications that were created in earlier versions.
You can improve the security of your application by completing the tasks on the checklist.
The following task reflects the procedure on how to manually add the security checklists to Designer Studio prior to 7.3.1:
- In the header of Designer Studio, click the name of the application, and then click Definition.
- Click the Documentation tab.
- In the Application guides section, click Add guide.
- In the Application guide& field, enter pxApplicationSecurityChecklist.
- Click the Configure icon in the Available in column and select the portals (App Studio and Dev Studio) that you want to add the security checklist to.
- Click Save.
Change logic does not work in Report Editor
Valid from Pega Version 7.1.2
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
Valid from Pega Version 7.1.2
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:
- Navigate to the <tomcat-home>\webapps\prweb\WEB-INF\classes directory.
- Open the prlogging.xml file.
- Locate the "appender" definitions section that contains the "@{web.tmpdir}" string
- 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
Valid from Pega Version 7.1.2
Use the following JVM setting to improve WebSphere performance on Mac platforms:
-Djava.net.preferIPv4Stack=true
Split schema systems require additional privileges
Valid from Pega Version 7.1.2
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.
Compare rule versions in a rule form
Valid from Pega Version 7.2.2
You can now compare different versions of rules from the
menu when you work within a rule form instead of using the Rule Compare utility. You can inspect changes that were made between versions directly on the rule form, make updates, and save any changes to the rule form.For more information, see Rule version comparison within a rule form.
Performance improvement to BLOB support in Postgres databases
Valid from Pega Version 7.2.2
New tables that contain BLOB columns now use external storage instead of expanded storage for Postgres databases. This improvement applies to tables that are created during installation, upgrade, or during DDL and schema generation. Using external storage improves database performance.
For more information, see BLOB storage in Postgres databases.
View all nodes in a cluster from the Cluster Management landing page
Valid from Pega Version 7.2.2
Use the Cluster Management page to view information for all of the available nodes in a cluster. To view the nodes, click Actions.
. To access detailed information about a single node, clickFor more information, see System Operations.
Automatically manage nodes in a System Management Application cluster
Valid from Pega Version 7.2.2
Instead of manually adding and deleting nodes in a cluster by using the System Management Application (SMA), you can now automatically manage nodes. You can enable Auto Node Discovery and configure it to get information about all the nodes in a cluster, add new nodes, and update the node list.
For more information, see Managing nodes automatically in a System Management Application cluster.
Logic-based assignment routing
Valid from Pega Version 7.2.2
You can now define business logic that controls when and by whom an assignment is processed in a case. By routing assignments to a specific user or group of users, you can help ensure that cases are resolved faster.
For more information, see Logic-based assignment routing.