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.
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.
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.
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.