Rule creation and simulations of changes in a change request in the Decision Manager portal
Valid from Pega Version 7.2.2
Two major enhancements to revision management give Decision Manager portal users more control over change requests. Revision managers and strategy designers can now create rule instances as part of a regular change request. They also can run data flows to do simulations of changes that are introduced by the change request.
For more information, see Rule creation and simulations of changes in a change request in the Decision Manager portal.
Data transform support in offline-enabled applications
Valid from Pega Version 7.2.2
You can now use data transforms in offline-enabled applications to reduce the need to write your own custom JavaScript functions. Data transforms are automatically packaged for offline use when they are configured on flow connectors, as preprocessing or postprocessing data transforms on a flow action, or on refresh actions or data transform actions on controls in a section. You also can run a data transform in offline mode by using a Run Script action or a custom JavaScript function, provided you add the data transform definition to the rule of offline-supported data transforms.
For more information, see Data transform support in offline mode.
Language detection option in Text Analyzer
Valid from Pega Version 7.2.2
On the Text Analyzer form, you can identify the language of incoming records based on their language metadata tag by selecting the Language detected by publisher option. This option applies only to Text Analyzer rules that process Twitter records. By combining this option with the advanced language filtering criteria of Twitter data sets, you can filter out unnecessary data and analyze only the Twitter records that are relevant to your business objective.
For more information, see Configuring advanced filter conditions for Twitter data and Configuring language settings.
Failed Robotic Assignments work queue type changed to Standard
Valid from Pega Version 8.5
The default Failed Robotic Assignments work queue type is now Standard. In previous releases, the default type was Robotic. For usage information, see Configuring a work queue for robotic automation.
Upgrade impact
After upgrading to Pega Platform 8.5 and later, you cannot save case types in which you configure the Queue for robot smart shape to route new assignments to the Failed Robotic Assignments work queue. Existing assignments that you routed to the Failed Robotic Assignments work queue are not affected.
How do I update my application to be compatible with this change?
As a best practice, do not use the Failed Robotic Assignments work queue in your custom implementations. Instead, configure the Queue for robot smart shape to route new assignments to a Robotic work queue. When possible, update existing case types to use the robotic work queues that you created in your application.
Options for filtering data in Twitter data sets
Valid from Pega Version 7.2.2
Twitter data sets have more options for filtering tweets. On the Advanced options tab of the Edit Data Set form, you can configure your Twitter data set to not analyze tweets if they contain specific keywords or if the tweets are made by specific authors. You can also select the languages to analyze based on the language metadata tag of the incoming tweets (tweets in other languages are ignored). By configuring the filtering criteria, you can ignore data that is not relevant to your text analysis and retrieve only the records that you need.
For more information, see Configuring advanced filter conditions for Twitter data.
Savable data pages support loading pages individually from a page list
Valid from Pega Version 8.5
You can now load individual pages in a page list from single object data pages to your case and data types. This functionality allows you to save autopopulated properties with the Load each page individually option using a flow action, save data page smart shape, or the activity method.
For more information, see Saving data in a data page as part of a flow.
Consistent search experience in App Studio
Valid from Pega Version 8.5
Pega Platform™ now supports a unified search mechanism in App Studio. Instead of manually locating a single item, such as a case type, a channel, or a data object, you can simply use the Search option in the navigation pane. You can also use Search in case types and personas landing pages, to conveniently access the information that you need, for example channels and case types associated with a persona.
For more information, see Plan your Microjourneys more conveniently in an improved Case Designer (8.5), Creating a Microjourney for customer success.
Improved experience when building an IVA and Email Bot in App Studio
Valid from Pega Version 8.5
Build your Pega Intelligent Virtual Assistant™ (IVA) and Pega Email Bot™ while working only in App Studio. This approach makes the design process easier and more intuitive, and saves you time. You can now modify the advanced text analyzer configuration while working in App Studio. In addition, if you have access to Dev Studio, you can edit the text analyzer rule from App Studio for your chatbot or email bot by clicking a link to open the settings in Dev Studio.
For more information, see Adding a text analyzer for an email bot and Adding a text analyzer for an IVA.
New Mobile Apps form for defining and building mobile apps
Valid from Pega Version 7.2.2
You now create and build mobile apps in Pega Express from the Mobile Apps form. The new console is a control center for mobile apps where you can gather applications, services, components, and settings in one place to fully customize your apps. You can create and build one instance of a custom mobile app and define multiple native mobile apps that can use the Pega Mobile SDK. To push notifications to an Android or to an iOS device, you must define an SDK mobile app in Pega Express with a certificate set that has push notifications enabled.
For more information, see Configuring a custom mobile app and Configuring push notifications for an SDK app.
Push real-time notifications to your clients
Valid from Pega Version 7.2.2
You can now set up a real-time notification system based on the publish/subscribe (pub/sub) messaging pattern where a node in the cluster can push notifications to your browser clients. Nodes publish notifications to a channel that can broadcast to all the subscribed browser clients.
You can create a notification channel from the Notification channels landing page and subscribe to the channel by selecting the On Load action, which is available under action sets.
For more information, see Real-time applications and push notifications in the Pega 7 Platform.