Define participants for case types
Valid from Pega Version 8.1
You can now configure participants more easily for case types. By defining case participants, you can indicate their relationship with a case and share important case updates with them. You can update case participants at run time, route assignments and approvals to them, and send notifications to them when goals and deadlines are not met.
For more information, see Participant configuration for case types.
Post private messages in Pulse
Valid from Pega Version 8.1
You can now post messages in Pulse to initiate conversations with selected users within a context. By posting private messages, you can discuss specific topics with relevant users without broadcasting them to all users.
For more information, see:
- App Studio – Posting a message in Pulse
- Dev Studio – Posting a message in Pulse
Reference spaces and documents in Pulse
Valid from Pega Version 8.1
You can now reference spaces and documents when you post Pulse messages. By including a link in your Pulse message that opens a relevant space or application document, you can add context to a conversation.
For more information, see:
- App Studio – Adding a reference in Pulse
- Dev Studio – Adding a reference in Pulse
Add comments to feed source messages
Valid from Pega Version 8.1
Users can now post comments on messages from feed sources in their activity feed. By adding comments to these types of messages, users can discuss topics from internal or external data sources, for example, Twitter updates on their organization. You can configure a feed source to allow comments on messages from the source.
For more information, see Adding a feed source for the activity feed.
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
External login with OpenID Connect or SAML protocol for custom mobile apps
Valid from Pega Version 8.1
Custom mobile apps can now use single sign-on (SSO) with OpenID Connect or SAML to authenticate by using identity providers such as Google, Auth0, Okta, or Azure Active Directory (Azure AD). External login provides a convenient and secure way to access your application. Users' credentials are never shared with the custom mobile app.
For more information, see Configuring a custom mobile app to use external login with OpenID Connect or SAML protocol.
Use spaces to collaborate with users
Valid from Pega Version 8.1
You can now collaborate with other users in your application on a specific area of interest by using spaces. By restricting the discussion of certain topics to the users of a space, you can avoid broadcasting irrelevant messages to all users in your application.
For more information, see:
- App Studio – Collaborating with users by using spaces
- Dev Studio – Collaborating with users by using spaces
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
Protect a custom mobile app with a device lock
Valid from Pega Version 8.1
Custom mobile applications that use an external identity provider (IdP) that is compatible with OpenID Connect or SAML for login are now protected with the device's personal identification number (PIN) or biometric lock. The app user does not have to set up an additional application-specific password and can unlock the app quickly and easily. You can configure the behavior of the locking method and implement custom locking methods by using a custom native module implementation.
For more information, see Protecting your custom mobile app with a device lock.
Ability to search case attachments in Pega Cloud Services
Valid from Pega Version 8.1
File repositories in Pega Cloud Services are now indexed. Indexing allows your application users to search case attachments from end user portals based on content and metadata.