Skip to Main Content
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.

Status Needs Review
Categories 13. Other
Created by Guest
Created on Feb 11, 2026

Touchpoint - Configurable Redirection URL Upon Wizard Completion

Description / Idea:
Currently, upon completion of the Touchpoint onboarding wizard, users are redirected to the standard HCL Connections Homepage application (/homepage) by default.
There is currently no supported configuration option to change this target URL to a different landing page, such as the HCL Connections Engagement Center (/xcc/main).

We request a standard configuration parameter (in touchpoint-config.xml) to define a custom post-wizard redirection URL.

Pain Point / Business Justification:
Many customers use the Engagement Center (HCEC) as their primary corporate entry point. To achieve this, they configure redirects at the IBM HTTP Server (IHS) level to send root traffic to /xcc/main (as documented in the official HCL guide: "Configuring the Engagement Center as the landing page").

However, there is no equivalent setting for Touchpoint. When a new user completes the onboarding wizard, Touchpoint redirects them to /homepage.
Result: The user lands on a page that is inconsistent with the rest of the company's navigation flow. This creates confusion for new employees immediately after their first interaction with the system.

Current Workaround & Risks:
The only documented workaround (referenced in article KB0082345) involves modifying the application code within the Touchpoint.ear file/directory directly.
This approach is not enterprise-ready because:

  1. Modifications to the applications code, for example Touchpoint.ear, are not officially supported.

  2. Modifications to the EAR file are overwritten by any HCL Connections Update or Touchpoint update, requiring manual re-implementation after every maintenance window.

Proposed Solution:
We suggest implementing a new parameter in the Touchpoint configuration file (touchpoint-config.xml) with /homepage as the default value:

<postTouchpointRedirection>/homepage</postTouchpointRedirection>

In the frontend logic (e.g., touchpoint.js or touchpoint.eventhandlers.js), a new attribute should be implemented that retrieves the value defined in the <postTouchpointRedirection> parameter. This new attribute should then be referenced in line 104 of touchpoint.eventhandlers.js.

Current Logic (touchpoint.eventhandlers.js, line 104, default):
$('body').append('<div style="display: none;"><a id="touchpoint-submit-final" href="%s">%s</a></div'.s([config.homepageCtxRoot, nls.button.submit]));

Proposed Logic (touchpoint.eventhandlers.js, line 104, modified):
$('body').append('<div style="display: none;"><a id="touchpoint-submit-final" href="%s">%s</a></div'.s([config.postTouchpointRedirection, nls.button.submit]));

  • Attach files