Here you’ll find some information regarding compatibility of Troi Plug-ins with FileMaker 19.
We will update this page when we release new versions of our plug-ins. Please check back for updates.
(This page was first published on May 20, 2020 and last updated on December 18, 2020. The web page with information regarding compatibility of our plug-ins with FileMaker 18 is still available here.)
Running plug-ins with FileMaker 19
FileMaker 19 (as does FileMaker 18) will still check if plug-ins are code-signed. A valid code signature assures the user that a plug-in is valid, unchanged and made by a certain developer. When you install a plug-in that is not code-signed, FileMaker 19 will give you a warning.
All current Troi plug-ins are code-signed. For more information on how our code signatures look, see the correct code signatures of Troi Plug-ins information. Please see below for an overview of all Troi plug-ins and their compatibility with FileMaker 19.
The same plug-in architecture
The plug-in architecture has not changed in FileMaker 19. So there is no need to change your function calls when converting to FileMaker 19.
Overview of Troi Plug-ins for FileMaker 19
Here is an overview of all our plug-ins that have been tested to work with FileMaker 19 (and also FileMaker Pro 18, 17, 16 and 15).
FileMaker 19, 18, 17, 16, 15
|Activator Plug-in||May 26, 2020||6.0.1||6.0.1||updated for FileMaker 19|
|Dialog Plug-in||Nov. 10, 2020||9.0||9.0||updated for FileMaker 19|
|Encryptor Plug-in||June 10, 2020||6.0||6.0||updated for FileMaker 19|
|File Plug-in||May 20, 2020||12.0||12.0||updated for FileMaker 19|
|Serial Plug-in||Sep. 4, 2019||6.0||6.0||code signed on macOS and Windows|
|Text Plug-in||May 19, 2019||4.5.1||4.5.1||code signed on macOS and Windows|
|URL Plug-in||December 18, 2020||7.0||7.0||updated for FileMaker 19|
* This is the first version that was tested with FileMaker 19