Third party add-ins on Server Mode

About this article

By allowing 3rd party add-ins in Server Mode, we enable users to utilize partner add-ins (e.g., Corporate Charts & Tables) in virtual environments.

• Overview
• Third Party Add-in Conversion Logic

Prerequisites

Overview

When the server mode module is enabled and third party add-in packages have been uploaded to the tenant, Templafy Desktop will convert the third party add-in packages when an update is requested. This allows utilizing one single add-in package no matter which environment (normal or virtual) is required. Additionally, some lines or blocks within the package can be skipped to avoid their translation if necessary.

Once the translation happens for the first time, the server mode converted version will be saved on the blob storage to avoid unnecessary conversion if the package remained identical and already contains the most recent configurations since the last Templafy Desktop update. 

Third party add-in conversion logic

The following conversion logic will be applied to the package: 

• LocalAppData folder to ProgramData
• Regristry entries HKCU will be converted to HKLM
• Office add-ins key is duplicated in HKEY_LOCAL_MACHINE\\Software\\WOW6432Node and HKEY_LOCAL_MACHINE\\Software to support 64- and 32-bit versions of office
• Both absolute paths C:\\Users\\CurrentUser\\AppData\\Local and abbreviations such as %localappdata% will be supported
• Folders like OfficeUserTemplates, WordStartup, ExcelStartup, AppData will be omitted

How to skip lines or blocks from being translated/converted

In case some parts of the package should not be translated during the conversion for server mode, one can use ;[TEMPLAFY SKIP START] and ;[TEMPLAFY SKIP END].

Related articles