HCL Connections Newsletter v2 and Join Community requests

Created:
Last Update:

Author: Christoph Stoettner
Read in about 3 min · 496 words

White Printer Paper on Blue Textile

Photo by Olya Kobruseva | Pexels

Since IBM Connections 6.0CR4 we can use a new newsletter format which needs still (now with HCL Connections 7) be activated separately in LotusConnections-config/notification-config.xml.

Today some users asked how they can add other users to their private communities (visible in Community catalog) without manually adding them. As we investigated the question I had a look at the old notification format.

So there a community owner got following e-mail when a user requested to join:

Mail notification for community owner

So he could directly add the requesting user to the community.

Now we switched to the new v2 format and the mail looks like this:

Mail notification for community owner in version 2

So the “Add Member” link disappeared. So what happens when we use “Open”? Yes it opens the community and I can’t see any link or option where I can answer these requests within the community. This was the reason for the users question, because they added the requesters manually with “Add member”.

Which other options does the user have to add the requesting members?

Notification Bell

Notification about user requesting community membership

There they get the information about the request, but clicking on the notification opens the Community and as we already know: you can’t see the request there.

Action Required

The only way to say and click the “Add member” link is “Action Required” in the old Homepage (sorry, but I haven’t deployed Orient Me until now, so I don’t know if you see it there).

Action required

Workaround

So how can we get the link “Add Member” into the notification email again?

LotusConnections-config/notifications_v2/communities/requestToJoinMail.ftl

27
28
29
30
31
32
33
34
35
<#-- Default 'Open' Action -->
<#assign defaultAction = comUrlUtil.linkifyContainer(community.url, comUtil.resource('OPEN_LINK_TEXT'), {}, comStyleUtil.actionArgs) />

<#-- Actions -->
<#assign actions = [ defaultAction ] />

<#-- Deprecated Actions -->
<#-- comUrlUtil.linkifyContainer(community.url, comUtil.resource("email.open.community")) -->
<#-- comUrlUtil.linkifySpecial(comUrlUtil.LINK_ID.COMMUNITIES.MEMBERS, community.members.url, comUtil.resource("email.add.this.person")) -->

Deprecated Action “email.add.this.person” let’s check this

27
28
29
30
31
32
33
34
35
36
37
 <#-- Default 'Open' Action -->
 <#assign defaultAction = comUrlUtil.linkifyContainer(community.url, comUtil.resource('OPEN_LINK_TEXT'), {}, comStyleUtil.actionArgs) />

 <#-- Actions -->
 <#assign actions = [
         comUrlUtil.linkifySpecial(comUrlUtil.LINK_ID.COMMUNITIES.MEMBERS, community.members.url, comUtil.resource("email.add.this.person"), comStyleUtil.actionArgs)
         defaultAction ] />

 <#-- Deprecated Actions -->
 <#-- comUrlUtil.linkifyContainer(community.url, comUtil.resource("email.open.community")) -->
 <#-- comUrlUtil.linkifySpecial(comUrlUtil.LINK_ID.COMMUNITIES.MEMBERS, community.members.url, comUtil.resource("email.add.this.person")) -->

Copy the line to the actions, remove the comment signs and add , comStyleUtil.actionArgs) into the function, this adds the same styles as for “Open”

When we synchronize the nodes and restart the news application we get following notification:

Customized newsletter with direct action

So we got back some usability, but in my opinion I miss a view in each Community to see the “Join Requests” like the view “Invitations” in the members’ widget.

There is already an enhancement request / idea in the Product Ideas Portal for HCL Connections .

Customized newsletter with direct action

Summary

I made all tests with HCL Connections 7 installed with Connections-Automation Ansible repository . I doublechecked and the error/missing link appeared already with Connections 6.5 (no older version to check).

Author
Add a comment
Error
There was an error sending your comment, please try again.
Thank you!
Your comment has been submitted and will be published once it has been approved.

Your email address will not be published. Required fields are marked with *

Suggested Reading
Card image cap

The newsletter in version 2 format has one big disadvantage, we or our users lost the easy links to the topic, author profile or application.

Created:
Last Update:
Read in about 2 min
Aaron Burden: Fountain pen and a notebook
I had an issue with daily newsletters in Connections 3.x, where newsletters were sent every 25 and not 24 hours. This is fixed in Connections 4, now newsletters are arriving every 24 hours.
Created:
Last Update:
Read in about 1 min
Card image cap

Last week I played around with the HCL Connections documentation to backup Elasticsearch in the article Backup Elasticsearch Indices in Component Pack .

In the end I found that I couldn’t get the snapshot restored and that I have to run a command outside of my Kubernetes cluster to get a snapshot on a daily basis. That’s not what I want.

Created: Read in about 4 min