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. With this release, end-users will be able to utilize sponsored solutions in virtual environments like Citrix.
How does it work?
When the server mode module is enabled and third party add-in packages were uploaded to the tenant, Templafy Desktop will convert the third party add-in packages for Server mode when an update is requested. This allows utilizing one single 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 happened the first time, the translated 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.
What is the conversion logic of third party add-ins for Server mode?
The following conversion logic will be applied to the package:
- Regristry entries
HKCUwill be converted to
- Office add-ins key is duplicated in
HKEY_LOCAL_MACHINE\\Softwareto support 64- and 32-bit versions of office
- Both absolute paths
C:\\Users\\CurrentUser\\AppData\\Localand abbreviations such as
%localappdata%will be supported
- Folders like
AppDatawill 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].
When is the package translated?
The third party add-ins will be translated on-demand when Templafy Desktop requests the package (/forceupdate in a virtual environment or in golden image).