HCL Connections Ideas Portal
Welcome to the HCL Connections Product Ideas Lab! The place where you can submit product ideas and enhancement request. We encourage you to participate by voting on, commenting on, and creating new ideas. All new ideas will be evaluated by the HCL Product Management & Engineering teams, and the next steps will be communicated. While not all submitted ideas will be executed upon, community feedback will play a key role in influencing which ideas are and when they will be implemented.
For more information and upcoming events, please visit our HCL Connections page.
I would be able to "mention" a certain person when working on a file f.ins.
Just a thought --
I agree with others that the risk of creating SPAM needs to be controlled.
Perhaps @Mentioning a community should be considered a "draft" post to a "news" or "announcement" for the target community..
The admins of the target community could then choose to accept reject the posting AND if accepting the posting could then choose to allow to individual community members OR only post to the "announcements"/"news" list(s)
I agree with the comment of 14 June 2019. This is a dangerous feature that must be handled with great care.
BIG SPAM-WARNING!
In Slack and other team chats, this is often over-used resulting in something similar to a bazaar, with everybody shouting over each other to get attention. Just as bad as email spam.
Maybe enable it only for Community Owners? And definitely make it possible to disable altogether.
If this is ever implemented PLEASE make it possible for the community owner to configure if s/he wants to allow this within the community AND make it possible for every user to configure if s/he wants to receive such a group notification within each of his/her communities!! Otherwise we will risk that people don’t use Connections any more since the spam they get via „Mail Community“ is now even increased by these group notifications!
As i "Profiles" it should be a solution to create "Groups" of members in a community. As "Mail to" just send mails to members and owners or only owners, there is a need to be able to send message to less than what is possible today. I miss the possibility to create different groups. Sorting members in a community into groups, make it possible to @Mention to the spesific group.
I would be able to "mention" a certain person when working on a file f.ins. Now I have to copy the link and then thereafter send a mail with the link with info.
Although I see the benefit of this as a simple and quick way to communicate, in our environment, where a community can have 25K members it would be necessary to give owners the option of allowing members to @Mention or to allow only owners to @Mention similar to how connections handles community email rights today... In fact you could leverage the existing selection for email rights and expand it to include @Mention.
Agreed.
When using a group @mention, maybe there could be a confirmation window to avoid accidental spamming.
I think that such feature would be very useful and often much better than “email this community” which produces messages which are not findable in Connections (as they obviously live only in e-mails)
I suggest to create new wildcards such as @owners @everybody and @network (for community members who are also in my professional network). Such granularity should hopefully prevent unnecessary mentions. Perhaps only community owners should be able to mention everybody. Or there might be a configurable option per community as we have got already for mail this community.
I think you need to be careful here. If that @Mentioning of a community would result in the same behavior as @mentioning an individual person (e.g. send a mail and list in the @mentioning tab) I would not be for it. The problem is that with that you would undermine the power of the individual @mention as someone could quite easily and unnecessarily @mention hundreds if not thousands of people by simply using one of the large communities in a org (I know of a public community with 15.000 users for instance that I would not like people to do that with). If you want to address those users you can always post a community status update.
However... I would like the idea of being able to @mention a community that will not so much create an individual @mention to each community member but trigger a status update in the community being @mentioned, referring back to the item where that @mention to a community was made from. That way you still address a group of users through it's community but aren't spamming everyone or undermining the power of the individual @mention