Here you’ll find some information regarding compatibility of Troi Plug-ins with FileMaker 18.
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 22, 2019 and last updated on October 13, 2019. The web page with information regarding compatibility of our plug-ins with FileMaker 17 is still available here.)
Running plug-ins with FileMaker 18
FileMaker 18 will 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 18 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 18.
The same plug-in architecture
The plug-in architecture has not changed in FileMaker 18. So there is no need to change your function calls when converting to FileMaker 18.
Overview of Troi Plug-ins for FileMaker 18
Here is an overview of all our plug-ins that have been tested to work with FileMaker 18 (and also FileMaker Pro 17, 16, 15, and 14).
FileMaker 18, 17, 16, 15, 14
|Activator Plug-in||Apr. 23, 2019||5.0||5.0||code signed on macOS and Windows|
|Dialog Plug-in||Oct. 13, 2019||8.0||8.0||code signed on macOS and Windows|
|Encryptor Plug-in||Feb. 12, 2019||5.0||5.0||code signed on macOS and Windows|
|File Plug-in||May 22, 2019||11.0||11.0||code signed on macOS and Windows|
|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||March 20, 2019||6.0||6.0||code signed on macOS and Windows|
* This is the first version that was tested with FileMaker 18