ScriptMaster

From 360Works Product Documentation Wiki
Revision as of 18:21, 21 May 2019 by Nick (Talk | contribs)

Jump to: navigation, search

ScriptMaster is a free, general purpose plug-in. Extended documentation here.

Contents

Deployment and installation

Will ScriptMaster run on FileMaker Server?

Yes. ScriptMaster will run in all three possible plugin configurations: FileMaker Client, FileMaker Server, and FileMaker Web Publishing Engine. See the Plugin installation page for information on where to put the plugin for these configurations.

Changing Log Location

To specify the location to which ScriptMaster writes log files, create a file called "loglocation". The contents of the file should contain the path you want to use to store log files. Place the file in the appropriate location:

  • OS X: /Library/Application Support/360FmKit
  • All Windows: C:\360Works\loglocation

Signing Your Generated Plugins

FileMaker requires that all plugins come with a signature, which indicates that the software is valid, unchanged, and made by a certain developer. The default store version of ScriptMaster, which you can download at this page here, comes already signed by 360Works. So if you are strictly using ScriptMaster to register modules and execute the RegisterGroovy or the EvaluateGroovy functionalities of the plugin, you can use the store version without issues. However, if you are using ScriptMaster Advanced to generate your own plugins, you will need to manually sign those plugins.

It is fairly simple and straightforward to sign your own plugins. To begin, you'll need to use the unsigned version of ScriptMaster, which you can download at this link here.

On Mac

After generating your plugin using the unsigned version of ScriptMaster:


On Macs, you will need to have Xcode downloaded and installed. Troi plugins already has a simple writeup of this process at this link here, which is referenced by FileMaker themselves. You will need to sign up as a developer for Apple to issue you a developer certificate. You'll want to open your own generated plugin in Xcode, and head to the "General" tab in Build Settings. Scroll down to the "Signing" section, and select your Developer ID certificate.

Xcode Signing.png

On Windows

After generating your plugin using the unsigned version of ScriptMaster:


On Windows, you will need Microsoft Visual Studio downloaded and installed. Both Troi and FM Plugins have simple writeups of this process here and here respectively. You will need to acquire a code certificate from a Certificate Authority, such as Comodo, as the Apple certificate will not work on Windows. After receiving and preparing your certificate, you'll need to open your generated plugin in Visual Studio, and use the signtool.exe in the Visual Studio Command Prompt.

Enter "signtool sign /f "C:\Users\acme\your-code-sign2018.pfx" /p YOUR_PASSFRASE_HERE /tr http://timestamp.comodoca.com "C:\Users\acme\Desktop\PluginName.fmx64" or "signtool sign /f {Path To Certificate} /p {password} /tr http://timestamp.comodoca.com "$(TargetPath)", and then build your project.

WindowsCodeSign.png

Troubleshooting

When using Select File module I get spinning beach ball (Mac)

This sometimes happens when you use the Select File module with the Allow User Abort FM script step set to OFF. Setting this value to ON, allows the Select File function to work smoothly.

Using Get( InstalledFMPlugins ) with custom plugins generated by ScriptMaster

Due to a bug in FileMaker, the Get( InstalledFMPlugins ) function will return the version number of the ScriptMaster plugin used to generate the custom plugin instead of the custom plugin's version number. You should use the included "xVersion" function that comes with all custom built ScriptMaster plugins instead when trying to determine which version of your custom plugin is installed.

Personal tools
Namespaces

Variants
Actions
Plug-in Products
Other Products
Navigation
Toolbox