Skip to main content

Improve collaboration by filtering Pulse feeds and adding attachments in Cosmos React (8.6)

Suggest edit Updated on May 11, 2021

Provide the users of your Cosmos React applications with access to relevant information by adding feed sources and the ability to attach files. Users can now view and filter feed sources directly in the Pulse feed, provide additional context for their Pulse conversations through attachments, and delete their own messages. Application developers can also select from Pega-provided feed sources to display in the Pulse gadget.

As a result of these enhancements, collaboration between different users of an application is more efficient. For example, a case worker can quickly find a request for additional information about a case by viewing only posts from cases that the worker is following. Then, they provide necessary details by replying to the request and attaching a relevant document.

Users can enable all feed sources, or only selected sources. For example, a manager views all posts that mention the manager or are replies to their own messages. As a result, the manager can quickly check for action items from the team, as in the following figure:

"The filters overlay contains several Pulse feed sources that users can view or hide"
Filtering Pulse feed sources

Pulse messages can contain one or more attachments. For example, a project manager attaches documents that the team needs to prepare for a meeting, as in the following figure:

"User writes a Pulse message and attaches multiple attachments"
Adding multiple attachments to a Pulse message

For more information, see Configuring Pulse feed sources for Cosmos React and Posting a message in Pulse.

Did you find this content helpful? YesNo

100% found this useful

Have a question? Get answers now.

Visit the Collaboration Center to ask questions, engage in discussions, share ideas, and help others.

Ready to crush complexity?

Experience the benefits of Pega Community when you log in.

We'd prefer it if you saw us at our best.

Pega.com is not optimized for Internet Explorer. For the optimal experience, please use:

Close Deprecation Notice
Contact us