Configuring Pulse in Constellation

User Experience
1

Pulse is awesome and i use it a lot personally in the Pega apps i am the user of. For both my current clients, i would like to be able to configure two things Constellation Pulse which i dont know how to do:

  1. I want to be able to disable the upload of attachments in pulse messages. Is there a system setting / configuration / condition that i need to change to disable this?
  2. I want to control the available operators that users can mention in the pulse? It looks like D_pyC11nOperatorsList is the datapage, but this is a datapage used in many other purposes (like user reference fields) and i see this datapage does not get the context of the case as param. I would love to restrict the available users to be mentioned by organization and in some cases only participating users to the case (case participants/stakeholders) to avoid sending pulse messages to users from which the case should be shielded and to avoid visibility of user names to users that should not see this personal information.
  3. Same (as 2) goes for case references.
  4. If i can not control the mentions or case references, i would like to be able to disable both mentioning and case relations all together.
2

@schos1Below is my analysis for your questions,

As such i did not notice any extension point (when/DT,etc) for hide the upload attachment feature. Although there is one to disable the delete post option. May be we might get natively in future

You can control the visibility of mention of User / Case using below extension points

Extend the pyExtendDefaultSettings DT in Pega-Ext-Mentions-Users / Pega-Ext-Mentions-Cases class (whichever you want to disable) and set the .pyHideMentions value to true to not to show the option when you type @ in the post text area.

For cases mode, if you want to filter the cases retrieved based on your search then start from the below activity,

@baseclass : pyRetrieveCaseListForReferences : Pega-Social:08-01-01

Which calls the RD pyGetCasesForReferencesFromIndex. You can modify the filters here to ensure you get results accordingly. May be you can also utilize the new extension point introduced in v25 for pxRetriveReportData as well (Mentioned at the last of this post)

To filter the Users both from global/case context, other than the DPage (D_pyC11nOperatorsList) you mentioned, i did not find anything more. If we modify this in any manner it might hamper other functionalities. Also, there seems to be no scope for additional parameters that can be configured to differentiate our custom configuration. So, for this feature as well, there should be a native extension point from pega in future which we can utilize.

Additional details : As part of this analysis, i noticed that we have a new extension point introduced in v25 in pxRetrieveReportData activity to filter the results based on some custom logic,

Rule-Obj-Report-Definition : pyRetrieveReportDataExtension : Pega-Reporting:08-25-01

Hope this helps

Regards

JC

3

@schos1

Hi Sander as suggested by Jayachnadra below you can override the pyExtendDefaultSettings data transform Pega-Ext-Mentions-Users and Pega-Ext-Mentions-Cases class.

To provide the necessary context for filtering the user list, we must pass the context to the data page. We will certainly consider this feedback for future improvements.