Conditionally start a process
Valid from Pega Version 8.1
You can now define a condition that causes a case to start a process in a stage. When the condition evaluates to false, the case skips the process. You can resolve cases more quickly by moving a case to the next process in the sequence when the current process is not relevant.
For more information, see:
- App Studio – Conditionally starting a process by using a condition
- Dev Studio – Conditionally starting a process by using a when condition
Collaborate on shared content by using documents
Valid from Pega Version 8.1
You can now share additional information about cases with all users in your application by using documents. Documents enable you to view shared content on a landing page and collaborate on the content with other users in Pulse so that you can resolve cases more quickly.
For more information, see:
- App Studio – Collaborating on shared content by using documents
- Dev Studio – Collaborating on shared content by using documents
Enhancements to the Send Email smart shape
Valid from Pega Version 7.3
The following enhancements have been made to the Send Email smart shape:
- You can now configure the Send Email smart shape in Pega Express.
- You can use templates, such as a rejection template, in your email.
- You can use property values, which allow you to insert the value of a field in your case type, such as First Name, within the email.
- You can insert a link to the case ID in your email.
- You can more quickly configure your recipient list by using two options, instead of one, to send messages to either a list of email addresses or to fields.
- You can choose to send either all case attachments in an email, or you can send attachments of a specified attachment category or an attachment type field. You can specify multiple attachment categories and attachment type fields.
For more information, see the following help topics:
Conditionally display an optional task
Valid from Pega Version 8.1
You can now define a condition that decides whether an optional task for a case type or a stage is displayed at run time. Optional tasks require additional processing, and by excluding the tasks that are not relevant, you can resolve cases more quickly.
For more information, see:
- App Studio – Conditionally displaying an optional task
- Dev Studio – Conditionally displaying an optional task
View mini user profiles in Pulse
Valid from Pega Version 8.1
You can now view mini profiles of users who post messages and users who are referenced in Pulse, by clicking the name of the user. A mini profile contains the user's job title, reporting manager, organization, and links to call and send email to the user. By seeing a brief overview of a user profile, you can access important information about users and contact them more quickly.
For more information about Pulse, see:
- App Studio – Communicating with users by using Pulse
- Dev Studio – Communicating with users by using Pulse
Support for calling a data transform from a case life cycle in App Studio and initializing data at case creation
Valid from Pega Version 8.6
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.
Conditionally display a supporting process
Valid from Pega Version 8.1
You can now define a condition that causes a case to display a supporting process for the case type or for a stage in the case type. When the condition evaluates to false, the case does not list the process. Supporting processes require additional processing, and by skipping the processes that are not relevant, you can help users resolve cases more quickly.
For more information, see:
- App Studio – Conditionally displaying a supporting process
- Dev Studio – Conditionally displaying a supporting process
Send email notifications for goals and deadlines
Valid from Pega Version 8.1
You can now configure an assignment or approval in a case type to send email notifications to the users associated with the case when the goals and deadlines are not met. You can create the subject and content for the notification message. The system sends email notifications when the suggested and required completion times for an assignment or approval elapse. By notifying relevant users about goals and deadlines, you can ensure that service-level agreements are strictly enforced during case processing.
For more information, see:
- App Studio – Setting goals and deadlines for task completion
- Dev Studio – Setting goals and deadlines for task completion
Create multistep forms for stages
Valid from Pega Version 8.2
In Case Designer, you can now create multistep forms for a stage. Create several focused and concise screens to capture the information from users instead of using a single long screen. For example, you can ask users for their personal details in one screen, and then ask them to describe their medical condition in a separate screen. When you create a multistep form, choose a template to determine how the users navigate between screens.
For more information, see Adding a multistep form to a stage (for Dev Studio), Adding a multistep form to a stage (for App Studio).
Add subspaces within spaces
Valid from Pega Version 8.2
You can now create subspaces within spaces. By adding a subspace, you can collaborate on a subtopic that is related to the topic of the parent space. For example, you can create an Annual Day subspace within the Events space.
For more information, see Creating a subspace.