Customize strings sourced in JavaScript

Overview

Replace a word or string in the product user interface sourced in JavaScript as opposed to a strings resource bundle.

Many strings in the Connections user interface are represented by key and value pairs defined in JavaScript files stored in the application JAR files. We can customize these strings by...

• Locating the JavaScript source file
• Copying it into the corresponding subdirectory of the customization directory
• Overwriting the key and value pair in the copied file with the custom text

We cannot use the customization debugging capability to test edited strings.

To change functionality of the JavaScript code, see Overriding JavaScript in Connections.

To use the external resource bundle loader for adding and updating strings in the user interface, see Add custom strings for widgets and other specified scenarios.

Update text in the JavaScript files in the deployment

1. Locate the JavaScript source file for the application to customize.

2. Determine the base directory where the customizations should go.

3. Copy and paste the file to customize into the appropriate subdirectory of the customization root directory.

   For example, for Activities, save the customized JavaScript file in...

   customizationDir/javascript/lconn/act/nls/strings.js

   For locale-specific strings, create a folder in...

   customizationDir/javascript/lconn/act/nls

   ...name it with the corresponding language code, and save the JavaScript file in the new folder.

   For example, to save German strings for Activities, save the customized JavaScript file in...

   customizationDir/javascript/lconn/act/nls/de/strings.js

4. Open the copied JavaScript file for editing. Find the key and value pair to overwrite, and replace the value with the custom text.

5. Repeat the previous step until you have replaced all of the strings to change.

6. Remove any key and value pairs that you did not edit. Those will be read from the version of the JavaScript file in the application's product directory.

7. Save and close the JavaScript file.

8. Use the WAS console, restart the application associated with the file you have changed.

9. Test the changes by clearing the browser cache, and then refreshing the browser.

10. See Apply the changes permanently.

To help find customizable strings sourced in JavaScript files, and to determine where to save the customized JavaScript files, see JavaScript resource strings.

Parent topic:
Customize product strings

Related:
Determine where to save the customizations
Required post-customization step
Overriding JavaScript in Connections
Add custom strings for widgets and other specified scenarios
Language codes
Property file strings