Text Input control number type does not validate
Valid from Pega Version 7.1.5
When a Text Input control type is set to "Number" in the Presentation tab:
- Validation does not trigger and the field is blanked out when a user submits the form.
- If a value other than a number is entered, the browser sends an empty value, and the value is not validated.
- In the Clipboard, the field value displays as empty.
- If the field is required, the validation displays.
This issue occurs when using both the Chrome and Safari web browsers, and is a result of browser behavior for the HTML5 type=“number”. To fix this issue when using these browsers, do not use the "Number" type in Presentation tab of a Text Input control. Instead, the type should be set to "Text".
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.
Unclear error message when saving shared class instance in tenant layer
Valid from Pega Version 7.1.5
If you attempt to save a shared class instance from the tenant layer, Pega 7 displays this message:
This record has x errors. Save Failed: There was a problem saving an instance of class: Error Code: <none> SQL State: <none> Message: <none>
You cannot save a shared instance from the tenant layer if that instance cannot be overridden.
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 . To access detailed information about a single node, click Actions.
For 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.
Show multiple views of data in your application
Valid from Pega Version 7.2.2
You can now show multiple views of data in your application by adding the record editor (pxRecordsEditor) section to a layout, another section, or a cell in a layout. You can configure the section to customize the display and enable the search, import, and export capabilities of the record editor.
For more information, see Multiple views of data in the record editor section.
Support for additional rule types for PegaUnit test cases
Valid from Pega Version 7.2.2
To compare the expected results with the results that are returned by running a rule, you can now create PegaUnit test cases for the following rule types:
- Activities
- Data transforms
- Strategies
- Decision trees
- Decision tables
After you unit test these rules, you can convert them to test cases and configure assertions on the test cases. You can also set up the clipboard with data before tests are run, and clean up the clipboard after tests are run.
For more information, see PegaUnit testing.