How notification templates are affected by customizations

In this article, we'll provide you with an overview of the changes that can be introduced to LMS365 notifications templates, by customers (which is called customizations) or on the LMS365 side, and how these changes will affect the notification templates.

In this article

• Changes that can be introduced to the LMS365 notification templates
• How customizations will affect notifications

Changes that can be introduced to the LMS365 notification templates

Required role: Catalog admin.

Editing of a notification template field by customers is called customization and such templates are marked as Custom in the All Templates column on the Notifications page.

Find more about how to customize notification templates in LMS365 in this article.

In LMS365, we provide our customers with all texts across the LMS365 product translated into 25 supported languages (27 languages for the LMS365 mobile app). This process is called localization.

We're constantly improving LMS365 capabilities and introducing new features and options that interact with the existing functionality and content, including texts in notifications, tooltips, messages, etc. These changes are implemented during the production release updates.

This means changes made to the LMS365 notification templates can be classified as either:

• Customizations – when the fields are edited by the customer.
• Localization – an automatic translation of the default fields values in the templates.
• Updates – changes of the fields values from the side of LMS365 released in a release.

How customizations will affect notifications

When customizations are introduced to a notification template, in some cases, it'll prevent the notification template from being updated with new product updates and translations.

In the following table, you can see how fields of notification templates are affected by customizations when new product updates and translations are introduced to the product.