1. Problem Statement / Current Behavior
Currently, the ICXT component for HCL Connections provides a default English template for exporting Wikis and Blogs to PDF. To localize these PDF outputs (e.g., changing labels to German, French, etc.), Administrators must currently rely on a workaround involving the main.js script.
While a template.properties file exists for configuration, it currently exposes a very limited subset of keys, mostly restricted to the Activities application.
Critical static text elements—such as "Table of Contents," "Tags," and "Date Format"—are not available in the properties file. To change these, an Administrator must modify the logic in main.js. This approach is suboptimal because:
High Complexity: It forces System Administrators to modify JavaScript code rather than using standard configuration files.
Operational Risk: Editing the script manually is error-prone; a single syntax error (e.g., a missing bracket) can break the entire PDF export functionality.
Inconsistency: It fragments localization efforts—some strings are managed in template.properties, while others are hardcoded in JavaScript, making management inefficient.
Time-Consuming: Requires developer skills rather than simple configuration.
2. Proposed Solution
Expand the existing template.properties file to include keys for all static text elements rendered in the PDF output. This allows Administrators to strictly use the properties file for localization without touching logic scripts.
Request: Add the following (and similar) keys to the standard property set:
Properties
# Proposed New Keys for General PDF Structure
pdf.content.general.tableOfContents=Table of Contents
pdf.content.general.tags=Tags
pdf.content.general.page=Page
pdf.content.general.createdOn=Created on
pdf.content.general.updatedOn=Last updated
3. User Story
"As an HCL Connections Administrator, I want to localize PDF export labels (like 'Table of Contents') simply by editing a key-value pair in a properties file, so that I can support multi-language users without maintaining custom JavaScript code".
4. Business Value & Impact
Ease of Administration: Shifts localization from a "Development Task" (editing JS) to a "Configuration Task" (editing a properties file).
Reduced Risk: Eliminates the chance of breaking the export logic when simply trying to change a text label.
Standardization: Centralizes all text strings into one standard property file, aligning with industry best practices for Internationalization (i18n).
For reference: ICXT - PDF Export templating documentation
