Hello,

Could you please provide more details and/or screenshots of what you would like to achieve?

Best regards,
Yuliya

Hi Yuliya,

what Sergio is asking is to only mark feed notification as read when they are clicked (similar behaviour to monday and other applications). 

Otherwise every time a user opens the tab, all notifications are marked as read, independent of if the user has read it or not.
 

I also noticed that unlike the instructions (https://academy.creatio.com/docs/8.x/creatio-apps/creatio-basics/commun…) the notifications counter is not showing and the new notifictions do not appear as grey. Can this have something to do with the browser that is used?

Rgds,

Luis

Luis Tinoco Azevedo,

Hi!

Unfortunately, so far, there is no possibility of marking notifications unread / marking them as read only after they are clicked. 
We have registered your suggestion on this topic, and our R&D team will consider implementing it in future releases.

As for the Academy article, there is an inaccuracy. The logic with the counter is currently applied only to the Classic UI shell. And the highlighting of the new notification has not been implemented so far.
We apologize for this inconsistency. We have already informed the Academy team about it, and they will correct the article. Also, a separate suggestion was registered for the R&D team on implementing the counter for Freedom UI and adding highlighting.

Thank you for being an active part of the Creatio community!

Best regards,

Natalia

Hello,

If you want to configure the deletion permissions please use Permission to delete messages and comments:



Permission to delete messages and comments gives permission to delete messages and comments left by other users in the [Feed] section, on the [Feed] tab of the Notification Panel, and on the [Feed] tab of the view and edit pages of the system sections.

Please note, that there is no possibility to deny permission to users to delete their own messages and comments even if they do not have access permissions to this system operation.

Hello Gareth,

Could you please elaborate on the task you are trying to achieve?

Additionally, could you please provide screenshots of the section you want to change?

Thank you,

Artem.

Artem,

The task I have been asked to do is to prevent users from adding comments to posts on the feed of the Agent Desktop.  Is it possible to remove or disable the comment button (see image)?  Thanks,

Gareth Osler,

One quick and easy way is to just hide the comments button with CSS. Add css to the agent desktop page - See https://customerfx.com/article/adding-custom-css-style-sheets-in-bpmonl…

Then add this CSS to hide the comments button:

#OperatorSingleWindowPageContainer [data-item-marker="SocialFeedContainer"] [data-item-marker="Comments"] {
    display: none;
}

Ryan

OperatorSingleWindowPage Agent desktop page already has CSS defined, namely OperatorSingleWindowCSS Agent desktop: CSS styles, which cannot be edited.

So I created another CSS file UsrOperatorSingleWindowCSS2 and put the CSS to hide comments in it.

The Agent desktop page isn't a normal section, it's not possible to open the section wizard, so I created a Replacing view model as follows:

Unsurprisingly the above did not work!  

Any suggestions would be appreciated.

Thanks,

Gareth Osler,

It does not appear as though you've created the replacing client view correctly. The code you shared shows "UsrClientUnit_fdb86f8", not "OperatorSingleWindowPage". This needs to change to match the view model being replaced. 

Ryan

Thanks for pointing out the mistake (you shouldn't have had to!).

For reference of anyone travelling down this road in the future the CSS/LESS to remove both comments and likes:

#OperatorSingleWindowPageContainer [data-item-marker="SocialFeedContainer"] [data-item-marker="Comments"] {
    display: none;
}
#OperatorSingleWindowPageContainer [data-item-marker="SocialFeedContainer"] [data-item-marker="UsersWhoLikeItButton"] {
    display: none;
}
#OperatorSingleWindowPageContainer [data-item-marker="SocialFeedContainer"] [data-item-marker="Like"] {
    display: none;
}