Overview of Language Localization in Anthology Reach

Anthology Reach is built upon the foundational components from Microsoft Dynamics 365, TPC (The Portal Connector) Portal, and Power Platform.

The architectural components of Anthology Reach include:

  • Out of the box (OOTB) solutions and objects provided and maintained by Microsoft.

  • Anthology-developed solutions and objects, which are part of its proprietary intellectual property.

  • Third-party solutions such as TeleSign SMS, MSCRM DCP, etc.

Languages Supported by Anthology Reach

  • Base Language

    Anthology Reach is developed in English as the base/primary language. All core functionality and interfaces are by default available in English.

  • Additional Language Support

    Anthology Reach provides language localized Reach solution with the option to support additional languages.

    The following additional language support is available:

    • Spanish - Spain (3082, es-ES)

Assumptions and Important Considerations

  • Microsoft OOTB Solutions and Components

    Microsoft provides translation language packs for its products and handles the translation of out-of-the-box (OOTB) Dynamics components.

  • Languages Supported

    The languages supported for OOTB Dynamics solutions are limited to those that Microsoft supports.

  • Anthology's Responsibilities

    Anthology is responsible for the deployment and maintenance of localized content in the customer's environment.

    This includes deploying the relevant Microsoft product language packs and language localized Anthology Reach product solutions and content. For a list of UI components that are localized and shipped OOTB, see Localized Components in Anthology Reach Solution.

  • Customization and Localization

    Implementation teams and customers can further customize or localize additional content. They are responsible for deploying and maintaining any customized content.

Localized Components in Anthology Reach Solution

The following table provides a list of UI components in Anthology Reach that are localized.

UI Component Comments and Examples
Model-driven app E.g. Anthology Reach App, Marketing, etc.
Site Map (Area, Group, Sub Area) The sitemaps associated to Model-driven apps
Entity Names and Descriptions Names of the System Entities or tables and their descriptions
Field Display Names and Descriptions Attributes names and descriptions
Option Set Labels Picklist, Multi-Select fields
Entity Relationships Entity relationship names
Form and View Forms and Views names along with Tabs and Section names.
Ribbon Buttons Buttons on Forms and Views headers
Web Components Entity Picker, Maps (Trip and Account Map), Connections View etc.
BPF (Step Names) Lifecycle BPFs, Trip BPFs, etc
Validation Messages Validation messages as part of Plugins and Javascript.
Web Controls E.g. Custom PCF (Entity Pickers on form, Dependent Option Set picker, Interaction Overview)
Web Resources E.g. Assign Success Plan Model Window, Application Completion Progress etc.
Business Rules System business rules and validation messages related to it

Areas, Components, and Solutions not Localized in Anthology Reach Solution

The following table provides a list of components in Anthology Reach that are not localized.

Areas or UI Components Not Translated Comments
Workflows Out-of-the-Box (OOTB) Workflows and Actions are only available in English.
System Integration Framework and Integration Mappings Out-of-the-Box (OOTB) Integration Mappings are provided only in English.
Security Roles Security roles are linked to the base language, which should not be changed. Management of these roles should be done in English.
Power Automate Flows Out-of-the-Box (OOTB) Power Automate flows are only available in English.
Default Data Default data within reference entities is only available in English.
Connections Functionality The default data for connections and the New Connection UI are available only in English.
Anthology Raise and its related solutions Anthology Raise solutions are currently not translated.
MSCRM – Template Designer MSCRM-ADDON template designer works better in English language.

Limitations

  • Multiple language data is currently not supported.

    • Microsoft Dynamics 365 currently do not provide a clear approach to handle multiple language data for reference entities.

Recommendation

  • It is recommended to use English as the base language for Anthology Reach.

    • End users can switch to a different UI language. For more information, see Changing the Language of User Interface.

    • System administrator should use English as the base language because the following components will continue to be displayed in English after the UI language is changed.

      System Components / Areas Not Available in Non-English Languages Comments
      Advanced Settings (Classic UI) Customization options in the Advanced settings in the classic UI are only available in English.
      Power Apps – System Configuration Pages System configuration pages within Power Apps are displayed in English only. Administrators working in other languages will need to use the English interface for these tasks.
      Solutions Solutions cannot be edited in languages other than English.
      Workflows Out-of-the-Box (OOTB) Workflows and Actions are available only in English. Administrators should use the English interface for managing and configuring workflows and actions.
      Integration Mappings Out-of-the-Box (OOTB) Integration Mappings are available in English. Ensure that all integration configurations are performed using the English interface.
      Student Integrations Out-of-the-Box (OOTB) Student Integrations are only accessible in English. Admins must use the English interface to manage these integrations.
      Security Roles Security roles are tied to the base language, which should not be changed. Ensure that security roles are managed in the English interface to maintain consistency and functionality.
      Power Automate Flows Out-of-the-Box (OOTB Power Automate flows are available only in English.

  • Importance of selecting a vendor for localization

    • Language Localization for Custom Components

      • Language localization for OOTB Reach components is managed with the assistance of our preferred vendor, Welocalize.

      • For custom components and strings added as part of your specific implementation, we recommend using Welocalize for localization services.

    • Why Use Welocalize?

      • Utilizing the same vendor for both OOTB and custom components ensures consistency in language localization.

      • Consistent use of language enhances the usability of the system for end users, providing a more cohesive and seamless experience.