Support for custom database tables in external Cassandra clusters
Valid from Pega Version 8.3
Pega Platform™ now supports a connection to external Cassandra clusters through a dedicated Database Table data set, which reduces the need for data ingestion and export. You can use custom tables that you store in your external Cassandra cluster in data flows for accessing and saving data. You can access your custom data model by mapping the model to a Pega Platform class.
For more information, see Connecting to an external Cassandra database through a Database Table data set.
Data synchronization does not resume after mobile app restart
Valid from Pega Version 8.3
If an offline-enabled mobile app that you build with Pega Infinity Mobile Client™ is stopped during an initial data synchronization session, the data synchronization does not resume when the mobile app is restarted. Users must not stop the mobile app before initial data synchronization finishes.
For more information about data synchronization, see Offline capability and Guidelines for creating an offline-enabled application.
Enhanced data flow performance monitoring
Valid from Pega Version 8.3
The performance alert log now provides more detailed information about the data flows in your application. You can view performance details for data flows that are currently running and data flow runs that have completed successfully. You can also view a performance summary for data flow runs that are running for too long or have failed.
For more information, see:
- PEGA0082 alert: Dataflow started
- PEGA0083 alert: Dataflow complete
- PEGA0062 alert: Data flow execution time above threshold
- PEGA0072 alert: Data flow run failed
Text analytics models editing and versioning
Valid from Pega Version 8.3
Pega Platform™ now supports editing and updating training data for text analytics models.
Pega Platform also supports the versioning of text analytics models. When you update the model, Prediction Studio creates an updated model version. You can then switch between the model versions.
Upgrade impact
In versions of Pega Platform earlier than 8.3, the training data for text models was stored in the database. In Pega Platform version 8.3 and later, the training data for text models is stored in Pega Repository. You cannot build new models without setting the repository. After the repository is set, all text models are automatically upgraded and will work normally.
What steps are required to update the application to be compatible with this change?
After a successful upgrade, set the repository in Prediction Studio before building or updating any Natural Language Processing (NLP) models. In Prediction Studio, click Settings > Text Model Data Repository.
For more information, see:
- Increase the accuracy of text analytics models by adding feedback data (8.3)
- Updating training data for text analytics models
Ability to support advanced device features with Pega Infinity Mobile Client
Valid from Pega Version 8.3
Pega Infinity Mobile Client™ now provides a development kit that you can use to make mobile apps support advanced device features that are typically available to native applications, for example, an embedded laser scanner or a projector module, and integrate functions of external software solutions, for example, a cloud-based file storage.
For more information about enhancing mobile apps with device feature support, see the documentation for the development module in the latest Pega Infinity Mobile Client distribution package on Digital Delivery.
Text analytics models migration
Valid from Pega Version 8.3
Pega Platform™ now supports the exporting and importing of text analytics models. For example, you can export a model to a production system so that it can gather feedback data. You can then update the model with the collected feedback data to increase the model's accuracy.
Upgrade impact
In versions of Pega Platform earlier than 8.3, the training data for text models was stored in the database. In Pega Platform version 8.3 and later, the training data for text models is stored in Pega Repository. You cannot build new models without setting the repository. After the repository is set, all text models are automatically upgraded and will work normally.
What steps are required to update the application to be compatible with this change?
After a successful upgrade, set the repository in Prediction Studio before building or updating any Natural Language Processing (NLP) models. In Prediction Studio, click Settings > Text Model Data Repository.
For more information, see:
- Increase the accuracy of text analytics models by adding feedback data (8.3)
- Exporting text analytics models
- Importing text analytics models
Support for regular performance alerts
Valid from Pega Version 8.3
You can now specify how often Pega Platform™ sends you performance alerts about SLA violations in data flow runs. By default, the interval is 5 seconds for single case data flows and 5 minutes for batch and real-time data flows.
The following dynamic system settings control the alert interval:
- Single case runs: dataflow/singlecase/alert/throttleTime
- Batch runs: dataflow/batch/alert/throttleTime
- Real-time runs: dataflow/realtime/alert/throttleTime
For more information, see PEGA0062 alert: Data flow execution time above threshold.
Automatic model training when mapping entities to case properties in Email Bot
Valid from Pega Version 8.3
You can now initiate automatic feedback to entity models in Pega Email Bot™, during manual mapping of email content to a case property.
To enable automatic feedback, you set the Work-Channel-Triage.pyIsRuntimeFeedback rule to true in Pega Platform™. By default this feature is disabled. Enabling this feature ensures that the email bot is more responsive by automatically copying detected entities, such as names, locations, dates, and ZIP codes, to case type properties of a case type.
For more information, see Email triage, Email channel NLP model and Enabling the NLP model training for the email channel.
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.
Data schema error on z/OS split schema upgrades from versions before Pega 7.1.8
Valid from Pega Version 4.1
When upgrading to a split schema on Pega 7.x with IBM DB2 for z/OS, you see an error during the data schema upgrade when the system tries to drop the PRPC_Updatescache procedure. Because triggers on rules tables use PRPC_Updatescache, you must use the ZOSDisableTriggerScripts to disable these triggers before you update the data schema.
- Follow the instructions in the Pega 7 Platform Upgrade Guide to upgrade the rules schema, but stop immediately before you upgrade the data schema with the upgrade.bat or upgrade.sh script. The Pega 7 Platform Upgrade Guide is on the page.
- Copy the contents of the <distribution>\ResourceKit\ZOSDisableTriggerScripts directory into the <distribution>\scripts\ directory.
- Run fixZosTriggers.bat or fixZosTriggers.sh with the following arguments:
--action preupgrade
--dataschema
<data schema name>--oldrulesschema
<old rules schema name. If you are upgrading from a single-schema system, this is the data schema name.>--newrulesschema
<new rules schema name>--automaticddl
<Optional. Set to true to automatically apply the disable trigger SQL scripts.>For example:
fixZosTriggers --action preupgrade --dataschema pegadata --oldrulesschema pegarules --newrulesschema newrules --automaticddl false
- If you did not set --automaticddl to true in the previous step, run the <distribution>\schema/disable.sql script to manually disable the trigger SQL scripts.
- Run the data schema upgrade as described in the Pega 7 Platform Upgrade Guide.