Tweak HCL Connections Newsletter v2

Created:
Last Update:
Author: Christoph Stoettner
Read in about 2 min · 251 words
HCL Connections newsletter

Postboxes for newsletter

Photo by Yannik Mika | Unsplash

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.

Newsletter version 1

When we look at the same information in Newsletter version 2, we can’t open the profile or the main blog/application, just the post is linked on the “Open” link.

Newsletter version 2 with default settings

The links are stored in the homepage database and are stripped away during the generation of the newsletter/notification message.

/opt/IBM/WebSphere/AppServer/profiles/Dmgr01/config/cells/CellName/LotusConnections-config/notifications_v2/resources/commonUtil.ftl 

391
392
393
394
395
396
397
398
399
400
401
402

<#-- Convert html fragment structures to text
 #              Strip all tags but preserve html entities
 #              Structural tags converted to white space to maintain word separation
 #              Link URL's are discarded
 # -->
<#function convertHtmlStructuresToText html>
        <#if html??>
                <#return __convertHtmlStructuresToText(html?string) />
        <#else>
                <#return html />
        </#if>
</#function>

This function is called to prepare the headings in the notifications. So we can remove the call, or just return the html after the call:

391
392
393
394
395
396
397
398
399
400
401
402

<#-- Convert html fragment structures to text
 #              Strip all tags but preserve html entities
 #              Structural tags converted to white space to maintain word separation
 #              Link URL's are discarded
 # -->
<#function convertHtmlStructuresToText html>
        <#if html??>
                <#return html /> # <.>
        <#else>
                <#return html />
        </#if>
</#function>

Replace the original line here with the highlighted code.

Now synchronize the nodes and test it again:

Newsletter version 2 with customized header

Author

Christoph Stoettner

I work at Vegard IT GmbH as a senior consultant with a focus on collaboration software, Kubernetes, security and automation. I mainly deal with HCL Connections, WebSphere Application Server, Kubernetes, Ansible, Terraform and Linux.

Sometimes my daily work results in technical talks and blog articles, which you can follow here more or less regularly. You can find the presentations in the main menu under public speaking .

I created a list of tools I use regularly, most of which have been released under an open source license.

In my spare time I read a lot, test all kinds of technical software and gadgets and try to follow about 200 RSS feeds.
Here you can find a collection of them.

This is my private blog, all opinions are my own.

           

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

HCL Connections Newsletter v2 and Join Community requests

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.

Created:
Last Update: Read in about 3 min
Aaron Burden: Fountain pen and a notebook

Daily Newsletter in IBM Connections 4

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

How to get regular snapshots with Elasticsearch

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