Skip to main content

This content has been archived and is no longer being updated. Links may not function; however, this content may be relevant to outdated versions of the product.

Support Article

Pega Pulse message visible to all users in same workgroup

SA-18333

Summary



User has the following requirement regarding Pega Pulse:

1. A particular operator posts a message on pulse in a case.
2. That message should not be visible to other operators of same workgroup when they open the same case

If user privately posts the message, users who open the same case will be able to see the message.

However, the requirement is for a user to post a message that will not be visible to others.


Error Messages



Not Applicable


Steps to Reproduce



Use Pega Pulse and post a message. 


Root Cause



Pega Pulse is a gadget that adds social activity streams to your application. When embedded in an application, it allows users in the same work group to create posts that share instant messages, files, and URLs.

Explanation with a few use cases the OOTB behaviour of Pega Pulse: 

User 1, User 2 belong to the same workgroup.
User 1 logs in and adds a post in Pega Pulse.
User 2 logs in. The post added by User 1 will be seen in Pega Pulse by User 2.
With both sessions active, if User 1 adds another post, User 2 will not be able to see the post unless a refresh happens.

As per OOTB behavior, if both users belong to the same workgroup, they will be able to see each others posts. 

Resolution



An enhancement request FDBK-13773 has been created for review and consideration by Pega Product Management. 

Published February 13, 2016 - Updated October 8, 2020

Was this useful?

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.

Did you find this content helpful?

Want to help us improve this content?

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

Pega Community has detected you are using a browser which may prevent you from experiencing the site as intended. To improve your experience, please update your browser.

Close Deprecation Notice
Contact us