Associate project management work items with application features
Valid from Pega Version 7.3
You can associate project management work items that you create in Agile Workbench with features in your application stack. Work items include bugs, user stories, and feedback. Associating a work item with a feature improves traceability in your application.
For more information, see Associating a project management work item with a feature.
Cross-origin resource sharing (CORS) policies for APIs and REST services
Valid from Pega Version 7.3
You can now use cross-origin resource sharing (CORS) policies to control how external systems and websites (origins) are permitted to access resources such as APIs and services within your applications. For example, Pega® Platform uses CORS policies to restrict which Pega Robotic client applications can connect to your Pega applications, and to limit which mobile apps can call Pega mobile services. Using CORS policies results in reduced cost and implementation times, while providing increased security when other systems or websites interact with your application.
For more information, see Creating a cross-origin resource sharing (CORS) policy and Mapping an endpoint to a cross-origin resource sharing (CORS) policy.
New delivery method for Pega Survey
Valid from Pega Version 7.3
The functionality of Pega Survey is now provided by a standard ruleset in the Pega® Platform. This new delivery method keeps your survey capabilities in sync with the latest features and speeds up development because you no longer need to install or maintain a separate archive.
You must purchase a separate license to use survey capabilities in your application.
For more information about surveys, see the Pega Survey product page.
Adding a conversation to a case type
Valid from Pega Version 7.3
You can add a conversation that uses a messaging or voice application (for example, Facebook Messenger) as a channel for adding information to a case. You configure the messaging workflow as part of the case life cycle. At run time, a user working in the selected application sees (or hears) a series of questions that ask the user to enter information.
For more information about adding a conversation in Designer Studio, see Adding a conversation to a case type.
For more information about adding a conversation in Pega® Express, see Adding a conversation to a case type.
Email instantiation added to case types
Valid from Pega Version 7.3
You can now configure a case type to support email instantiation. By associating your case type with an email account, you can provide a way for users to create cases without logging in to your application. In addition, stakeholders can track updates to a case in one place, because the email and related discussion thread are stored in Pulse.
For more information about email instantiation, see Configuring the Email channel.
Improved interactions for email and Pulse
Valid from Pega Version 7.3
You can now continue a discussion that was initiated by email when you post a message to Pulse or reply to an email message. By providing a consistent thread of discussion in a case, you can keep stakeholders informed while allowing them to use the communication channel of their preference.
For more information about the communication interchange that occurs when you initiate a discussion, see:
- Pega Express 7.3 - Email instantiation
- Pega Platform 7.3 - Email instantiation
Create specialized Decision Data rules for text analytics resources
Valid from Pega Version 7.3
You can store various types of resources for text analytics in Decision Data rules that are based on templates. Each resource type (for example, sentiment analysis models, taxonomies, entity extraction rules, and so on) has its own definition class that defines the appearance of the corresponding Decision Data rule form. With this enhancement, system architects can create and maintain various text analytics-related artifacts without having to edit the default Decision Data form fields first.
For more information, see Definition class of text analytics Decision Data rules.
Pega Agile Studio integration
Valid from Pega Version 7.3
You can configure the new Agile Workbench tool to integrate with Pega® Agile Studio so that bugs and user stories are synchronized between the two systems. In addition, you can improve traceability in your development environment by using the Current work feature to associate a user story or bug with development changes.
For more information, see Integrating Agile Workbench with Pega Agile Studio and Tracing development changes to work items.
Style UI elements based on their state
Valid from Pega Version 7.3
You can style a control or component based on its state to give users a visual indication of an element's current state, without overriding the CSS file. The styles that you specified for each state (hover, focus, or active) are applied at run time.
For more information, see Styling UI elements based on their state.
Style radio buttons as segmented buttons
Valid from Pega Version 7.3
You can configure radio buttons to be displayed as segmented buttons. Segmented buttons display multiple button options in a compact format. Segmented buttons do not support vertical orientation. On the Presentation tab of the properties panel, set Control format to Other and select Segmented.
For more information, see Radio Buttons control properties – Presentation tab.