HCL Connections
Some time ago I got the tip from HCL Support, that the Create Community button will recognize the role community-creator only when the gatekeeper option CATALOG_CARD_UPDATED is set to false.
This is working, but I had to complain, that this option activates some code, which loads fonts from a CDN instead of the local Connections deployment.
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.
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.
Since the update to the new HCL Connections Community Card-Based Overview (Connections 6.0 CR4) I search for a way to hide the button “Create Community” from users without the role “Community-Creator”. This was always possible in the earlier versions of Connections, but the button was shown always since the update.
During the year I mostly forgot about it, but yesterday I opened a case with HCL Connections Support and got immediatly following answer:
Some weeks ago I wrote about an workaround to prevent TDI from deleting the touchpoint status in HCL Connections .
During some research on TDI I found Mapping fields manually in the HCL Connections documentations. This document describes how to add additional fields to the TDI synchronisation. On point 11 I found something new for me. You can add additional fields and then add the content with an Javascript function for example.
Today I activated Elasticsearch Metrics and Typeahead Search on my demo HCL Connections cluster .
To my surprise the indices weren’t created and I got errors on the wsadmin.sh commands.
SearchService.createESQuickResultsIndex()
I checked the Elasticsearch pods which showed a running state, but the logs showed following messages: