Import and export artifacts to and from a repository
Valid from Pega Version 7.3.1
You can import and export development artifacts to and from a repository. Use the Import wizard, the Export wizard, or the service-enabled system management command-line tool to move artifacts. For more information, see Tools for migrating rules and data.
Like and bookmark Pulse messages
Valid from Pega Version 7.3.1
You can now like messages that are posted to Pulse and view the number of likes for each message. You can also bookmark the messages that you want to view in your activity feed.
For information about Pulse enhancements, see:
- Pega Express 7.3.1 – Communicating with Pulse
- Pega Platform 7.3.1 – Pulse enhancements for social collaboration
Real-time updates in Pulse
Valid from Pega Version 7.3.1
You can now view real-time updates of messages in Pulse. If a user posts a comment on a Pulse conversation while you are viewing the conversation, you receive a notification in real time, which you can click to refresh the conversation and see the comment.
For information about Pulse enhancements, see:
- Pega Express 7.3.1 – Communicating with Pulse
- Pega Platform 7.3.1 – Pulse enhancements for social collaboration
Customize themes for your application
Valid from Pega Version 7.3.1
You can now customize themes for your application by selecting the background, border, button and text colors; border width; and text font and size. You can further customize themes by using Cascading Style Sheets (CSS).
For more information, see Customization of themes.
Legacy landing pages removed
Valid from Pega Version 7.3.1
The following legacy landing pages and their links in the Designer Studio menu have been removed:
The streamlined Designer Studio menu facilitates locating and navigating to landing pages.
For information about the replacements for these landing pages, see Deprecated features.
Service REST monitoring
Valid from Pega Version 7.3.1
You can now monitor response and request data for REST services and view the results in Pega® Platform. The ability to monitor REST services is useful for debugging your application during development, for example, when a request fails. It is not recommended that you monitor REST services in production environments because monitoring might affect performance and depending on the number of incoming service requests, there is a chance that over a period of time, the invocation history might get large enough so that you run out of database space. You can configure monitoring globally for all of your REST services by using the service/EnableglobalMonitoring Dynamic System Setting with owning ruleset Pega-IntegrationEngine, or by using the service package and service rule forms.
For more information, see Service REST monitoring.
Support for intelligent routing in the Email channel
Valid from Pega Version 7.3.1
When you create an Email channel interface to use as a Pega® Intelligent Virtual Assistant, you can now set up automatic routing of the received email content. You define routing rules so that the Email channel is more responsive and makes an informed decision about how to process the email content. The Pega Intelligent Virtual Assistant can automatically assign it to an operator, add it to a work queue, or create a top-level case. In addition, you can configure multiple email accounts to act as the same Pega Intelligent Virtual Assistant.
For more information, see Configuring routing conditions for automatic email handling.
Import to and export from network storage
Valid from Pega Version 7.3.1
You can import development artifacts from and export development artifacts to network storage. Use the Import wizard, the Export wizard, or the service-enabled system management command-line tool for these activities.
For more information, see Tools for migrating rules and data.
Support for advanced text analysis when routing incoming emails
Valid from Pega Version 7.3.1
You can use text entity, category and sentiment analysis during the automatic routing of incoming emails. You provide text analysis of the text-based email content by defining routing rules, so that an automatic decision is made about how to process the received emails by the Pega® Intelligent Virtual Assistant. You can route the email content to an operator, assign it to a work queue, or open a top-level case with the information.
For more information, see Configuring routing conditions for automatic email handling.
Conditional paths added to case life cycle
Valid from Pega Version 7.3.1
You can now add a conditional path to a process in the life cycle of a case. By defining the decisions that cause a process to follow different paths, you can create cases that support more than one outcome.
For more information about conditional paths, see Conditional paths in a case life cycle.