+

Search Tips   |   Advanced Search

Customize shared resources for notifications

We can customize the common style and structure documents used by notifications in Connections.

Important: Before making any customizations, first back up the original notifications folder. In addition, ensure that any customized files are backed up before performing a product upgrade or applying a cumulative refresh or fix pack, as we might need to merge the changes again manually after making updates.

The notifications used in Connections share common style and structure documents, and are stored in the same location, allowing you to write the customizations once for all notifications, except for email digests. For information about customizing the daily and weekly email digests sent to users, see Customize email digests.

We can customize notifications in Connections by updating the shared resources stored at this location:

Resource Description
images Folder containing all the shared images referenced in templates.
nls Folder containing all localized strings shared between templates.
commonEEStructure.ftl Template used for generating the Embedded Application MIME part.
commonHeader.ftl Used in templates to import common .ftl files into scope. Uses acquisition look-up.
commonStructure.ftl Holds the main FreeMarker macros and functions that make up the individual notification components. For example, action, metadata, header, and footer.
commonStyle.ftl One CSS style file used in all individual notification templates.
commonUrlUtil.ftl Specific utility functions for URL link handling. Contains the linkify function.
commonUtil.ftl Provide a common set of utility functions.

Note on Freemarker acquisition: The template files that exist in the resources folder can also be stored in the notifications folders for specific applications. For example, to customize Activities templates, you place commonStyle.ftl at the following location:

Saving the style file in this location allows the Activities templates to pick up different styles that override the default shared ones. Acquisition look-up ensures that templates are imported to a directory that is local to the currently generated template. If the templates do not exist, the parent folders are scanned and the templates from the shared resources folder are loaded. Similarly, the images and nls resources can be stored in a directory that is local to an application folder. The notification framework ensures that local resources are checked and used first before checking the shared resources location.

To customize the content of a shared resource, complete one or more of the following steps.


Parent topic:
Customize notifications


Related:

Customize standard notifications

Customize email digests