Published Release Notes

Life cycle tab renamed to Workflow

The Life cycle tab for case types has been renamed to Workflow. On the Workflow tab, you can define a life cycle for case types by clicking Life cycle, and you can define user actions for case types and stages by clicking Optional actions.

For information about defining a life cycle for a case type, see:

• Pega Express 7.3.1 – Defining a life cycle for a case type
• Pega Platform 7.3.1 – Defining a life cycle for a case type

For information about user actions, see:

• Pega Express 7.3.1 – User actions
• Pega Platform 7.3.1 – User actions

Create simple URLs for work objects

You can now represent your work objects with simple URLs by using the new URL Mappings rule. Simple URLs are meaningful and easy to share with others, and improve collaboration between users of the same Pega^® Platform application. You can define different URL patterns to use in your application for your work objects (cases), reports, landing pages, or others. You can also generate canonical URLs for your case types to make all instances of these case types searchable by third-party search engines. To enable search engine indexing, a link tag is added to your case object harness.

For more information, see URL Mappings.

Enhanced activity feed for Pulse displays messages

The activity feed for Pulse has been enhanced to display replies to messages that you have posted, messages on cases that you are following, messages in which you are referenced, messages posted on your user profile, messages by users that you are following, and messages that you have bookmarked. You can filter the activity feed to display the messages that you want to view.

For information about Pulse enhancements, see:

• Pega Express 7.3.1 – Communicating with Pulse
• Pega Platform 7.3.1 – Pulse enhancements for social collaboration

Define property value criteria for stage entry

You can now define the criteria that property values must meet to enter a stage, by clicking Validations on the Data model tab of a case type. By validating the properties, you can ensure that a case contains relevant data before it enters a stage.

For more information, see Property condition requirements for stage entry.

Question template added to surveys

You can now import a question template to create multiple questions at once. By providing question data in a format that your application processes in bulk, you can speed up the development of your surveys.

For more information about the types of questions that you can import, see Question templates.

Improved processing of correspondence details

When you send correspondence, the system now does not update the pxSendDateTime property on the pxCorrSummary work page that belongs to pyWorkPage. In previous versions of Pega Platform™, after sending correspondence, the update of the pxSendDateTime property could cause errors when working with an application at run time. To prevent such issues, Pega Platform now includes a pyEnableCorrSummary when rule that, by default, is set to false. If your business scenario requires updating the pxCorrSummary work page, set the when rule value to true.

For more information, see:

• Notifying participants about events
• Approval by email
• Sending automatic emails from cases

Support for picklists with parameterized data pages in App Studio in Cosmos React UI

You can now use data pages with parameters to populate a property of the picklist type with filtered results in App Studio. For example, in a survey case type, you can use a parameterized data page to configure cascading drop-down controls in which the values in a secondary drop-down list are based on the value that the user selects in the primary drop-down list. With dynamically-sourced picklists, you get greater flexibility in configuring picklists, and users see more accurate values.

For more information, see link Dropdown control Properties — General tab.

Questionnaires available in App Studio

App Studio now supports authoring questionnaires, which in previous releases of Pega Platform™ were known as surveys. You can create questionnaires, add question pages, and populate the pages with questions of different types so that you can collect the exact data that your business processes require. For more efficient data management and reuse, data objects from a data model now store answers to questions, instead of autogenerated properties. For example, when a customer provides a date of birth in a questionnaire, and your application stores the date as a data object, you can conveniently reuse that data object in related cases. For greater flexibility, both standard Pega Platform and Cosmos React applications support questionnaires, however, some question types are unavailable in Cosmos React.

For more information, see:

• Create questionnaires in a low-code way in App Studio (8.6)
• Creating a questionnaire

Remote case types in App Studio

App Studio now supports remote case types for applications that you build on Cosmos React. With remote case types, you can create a case type inside one application, and then work on cases based on this case type in another, remote application. As a result, users can perform work from multiple applications on one screen without the need to switch between applications, which results in increased efficiency and faster case resolution.

For more information, see:

• Increase efficiency by sharing remote case types between applications (8.6)
• Remote case types  

Support for calling a data transform from a case life cycle in App Studio and initializing data at case creation

You can now call a data transform from a case life cycle in a low-code way in App Studio. For example, when a customer wants to order the same product again, your application can reuse the shipping information from their previous order. Additionally, by configuring data initialization for a case type, you can prepopulate fields at case creation. For example, an application for a delivery service can apply the customer's preferred delivery options when a new case starts. These enhancements save time for developers because the system can initialize data and prepopulate fields in a case by reusing existing logic, and for customers, who do not need to manually enter their details every time.

For more information, see Calling a data transform from a case and Initializing data at case creation.