Skip to main content

Gatekeeper Flag FILES_ENABLE_CONTINUOUS_SCROLLING removed in Connections 8.0CR11

Some years ago Connections Files changed the catalog view from paginated view to continuous scrolling.

This had two caveats:

  • On large monitors (4k for example) only 10-20 files appear and the trigger to start loading more files to complete the list is not working
  • Feed icon (Feed for these Files) to copy the RSS feed URL is hard to get on large file catalogs (scrolling starts, and you can’t right-click to copy)

We asked for a way to disable this and got the Gatekeeper Flag FILES_ENABLE_CONTINUOUS_SCROLLING=False as solution.

Warning

Gatekeeper flags are normally unsupported, except when you got them from support to fix a specific problem.

During the installation of Connections 8.0CR11 we got an error setting this flag (flag missing). I checked https://connections_host/connections/config (you need the admin role in Common to access this site) and the flag has disappeared with CR11.

An opened case pointed to the right direction:

I will share however, the FILES_ENABLE_CONTINUOUS_SCROLLING was intentionally removed as a GK flag and was intended to become a generic property in the LotusConnections-config.xml. However, upon my internal testing, the generic property is not working as intended.

They didn’t mention the flag, but I wanted to double-check if it works.

So I started searching in the deployed Files.ear and found in files.web.war/v8/main.js the line 253:

let isScrollingEnabled = lconn.core.config.properties["files.view.continuous.scrolling.enabled"];

The new flag in LotusConnections-config.xml is files.view.continuous.scrolling.enabled and was added to my config already during the update, I just had to switch it to false. After a node synchronization and restart of all HCL Connections application servers, the continuous scrolling was disabled again.

I’m really happy that this Gatekeeper flag is now a config option, as this means that it gets tested during updates. The process could be made better, I would expect such breaking changes mentioned in the “What’s new section” of the documentation and the available config options for LotusConnections-config.xml.

Christoph Stoettner
Author
Christoph Stoettner
I work at Vegard IT GmbH as a senior consultant, focusing on collaboration software, Kubernetes, security, and automation. I primarily work with HCL Connections, WebSphere Application Server, Kubernetes, Ansible, Terraform, and Linux. My daily work occasionally leads to technical talks and blog articles, which I share here more or less regularly.

Related

Encrypt IHS proxypass traffic to Component Pack

I’m still working on encrypting all network traffic between Connections and Component Pack servers. This time I checked the Ingress-Nginx Controller - TLS/HTTPS documentation. The default configuration for connecting IHS with Component Pack uses the plain HTTP port 32080. All traffic like /social or the Tailored Experience wizard is routed from IHS to Kubernetes on port 32080. Our target is to encrypt the traffic on port 32443.