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
Surveys do not display questions with custom templates
Valid from Pega Version 7.3
Because many rules have been refactored or renamed in the Pega-Survey ruleset, questions that use custom templates are not displayed in surveys. To resolve this issue, create a new version of the applicable sections from the Embed-PegaQ-Results-Question class in your application, and then update the sections to include your custom content and logic.
WebSphere log error with Java 8 for Enterprise JavaBeans
Valid from Pega Version 7.1.8
For environments that are deployed by using Java 8 on IBM WebSphere Application Server version 8.5.5.9 through the last 8.5.5.x fix pack, the log might report that a class was not found when the application server attempts to start Enterprise JavaBeans. If Java EE functionality is not needed, no further action is required. However, to use Enterprise JavaBeans, see WebSphere log error with Java 8 for Enterprise JavaBeans.
Package caching is not supported in offline-enabled applications built with the UI Kit 7 (09-01-01) portal
Valid from Pega Version 7.3
When you create an offline-enabled application in Pega® Platform, by default, it uses a portal with the UI Kit 7 (09-01-01) ruleset. In such a case, the package caching functionality cannot be used. You must either disable caching on the Advanced tab of the Access Group rule form, in the Offline Configuration section, or use an adaptive design instead of rendering different elements for different devices with the UI Kit 7 (09-01-01) ruleset.
For more information, see Access Group form - Completing the Advanced tab.
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.
Text file rules support JavaScript and CSS validation
Valid from Pega Version 7.3
The Rule-File-Text rule form supports validation errors and warnings for JavaScript and CSS files. This support makes JavaScript and CSS code easier to maintain and allows you to follow best practices while editing the rule. Any JavaScript or CSS validation warnings generate a guardrail warning of moderate severity.
For more information, see Text File rules - JavaScript and CSS validation.