Surveys are not compatible with prior versions of the UI Kit
Valid from Pega Version 7.3
Now that survey functionality is available in the Pega-Survey ruleset, some rules are no longer compatible with prior versions of the UI Kit. To ensure that your surveys are rendered correctly, update your Application form to include version 09.01 of the UI Kit.
If you cannot change the version of the UI Kit, you can override the Work-.pyCaseActionArea section in your application and update it to use the same configuration as the section in version 09.01 of the UI Kit.
Surveys do not display navigation links
Valid from Pega Version 7.3
The navigation links, or bread crumbs, in a survey are not displayed when you configure a survey to run as a screen flow. To resolve this issue, override the Work-.pyCaseActionArea section in your application, and then update that section to include the Work-.ProcessSteps_ScreenFlow section.
Deprecated survey APIs
Valid from Pega Version 7.3
APIs that were available in the PegaSurvey ruleset have been superseded by Pega® Platform APIs. Although older APIs continue to function in this release, it is recommended that you update your flows and flow actions to use the new APIs because they provide the latest survey capabilities, and deprecated features are not supported.
The following table maps deprecated APIs to their replacement APIs.
| Deprecated API | New API | Description |
|---|---|---|
| Work-.QuestionShape | Work-.pzQuestionShape | A flow that displays one simple question. |
| Work-.QuestionShapeScr | Work-.pzQuestionShapeScr | A screen flow that displays one simple question. |
| Work-.SurveyDriver | Work-.pxSurveyDriver | A flow that displays questions in a survey, which can be simple or complex. You can control whether the questions are displayed on one or multiple screens. |
| Work-.SurveySection | Work-.pxSurveySection | A section that displays questions in a survey. You can reference this section from a user action, such as a flow action or connector flow action, in a flow. |
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.
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.
Class structure expanded for surveys and questions
Valid from Pega Version 7.3.1
You can now create surveys and questions at any class level. Because there is no longer a restriction on which class of flows can use the Survey and Question smart shapes, you can create more contextual surveys that reference embedded properties, or instances of classes, that you define outside the Work- class structure.
For more information about using the Survey or Question smart shapes in a flow, see Integration methods for surveys.
Locatable pages are deprecated
Valid from Pega Version 7.3.1
Locatable pages are deprecated. Use a data page instead. Data pages provide improved performance. When you save a rule that has a Locate Page Activity or when you create an activity of type Locate page, a guardrail warning is displayed indicating that this feature has been deprecated.
For information about data pages, see Data pages.
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