FileMaker version 12 or higher.
When 360Plugins are intialized for the first time, they will automatically download all required support files
Drag the plugin from the MAC or WIN folder into your FileMaker extensions, and restart FileMaker.
If the plugin does not load correctly, please send an email to support@360works.com
Install plug-ins for use with WebDirect by dragging the appropriate plugin to FileMaker Server/Web Publishing/publishing-engine/cwpc/Plugins
You do not need to do this step unless you plan on using the plugin with Instant Web Publishing with FileMaker Server Advanced. You will need an Enterprise license to use this feature.
For installing into the Web Publishing Engine with FileMaker Server or FileMaker Server Advanced, drag the plugin from the MAC or WIN(.fmx) folder into the FileMaker Server/Web Publishing/publishing-engine/wpc/Plugins folder. If there is no Plugins folder inside the wpc folder, then create it manually. Restart FileMaker Web Publishing, and now the plugins should be ready to go.
The easiest way to test whether the plugin is working is to call the version function of the plugin, and display that on an IWP layout. If it shows "?", then the plugin is not working. If it shows a number, then the plugin has been installed successfully.
If you are using FileMaker Server 12.0v1, you can follow the same procedure as detailed above for custom web publishing. However, in FileMaker Server 12.0v2 and later, custom web publishing now runs as a 64-bit application and requires the 64-bit version of the plugin You will need an Enterprise license to use this feature.
For Mac, the single plug-in file in the MAC directory contains both 32-bit and 64-bit versions. For Windows, look for the plug-in that has the extension .fmx64 and use it in exclusively in custom web publishing.
To install 64-bit plug-ins, install either the .fmx64 or the .fmplugin to the following directory:
FileMaker Server / Web Publishing / publishing-engine / cwpc / Plugins
If it does not exist, create the Plugin folder manually. Restart FileMaker Web Publishing, and then you can then test a script that contains a plug-in and see if it returns the correct values.
You do not need to do this step unless you plan on using the plugin with scheduled script triggering. You will need an Enterprise license to use this feature.
360Works has created an AutoUpdate helper database which makes setting up AutoUpdate much easier. This file includes pre-configured plugin files which you can place on your server, and an AutoUpdate script for each of our plugins which you can paste into your own solution.
You can get the AutoUpdate360Works file here Follow the instructions included in the file to either host your own Auto Update server or pull the files from ours.
Plugins will run in demo mode until they are registered. While running in Demo mode, the product will run for 2 hours every time you launch FileMaker / FileMaker Server / FileMaker Web Publishing Engine. The 2 hour time limit will reset every time you relaunch FileMaker. There is no expiration date when Demo mode stops working. There are no feature differences between the Demo version and the licensed version.
Once you have purchased the plugin, you can register it with the license key. Once a valid license key is entered, the product will run for as long as FileMaker is running. After FileMaker starts up with the plugin installed, open FileMaker preferences, click on the Plug-ins tab, select the plugin from the list, and click the Configure button. Enter your license key and company name in this dialog. You will only need to do this once on a given machine. Alternately, you can use the registration function to register the plugin during a startup script.
Note: If you are running the plugin with FileMaker Server / FileMaker Web Publishing Engine, you must use the registration function to register the plugin, since there is no preferences dialog on FileMaker Server to enter the license key and company name. You will need to call the register function at the beginning of any script that is going to call plugin functions. This will ensure that you do not get demo mode errors.
We love to hear your suggestions for improving our products! If you are experiencing problems with this plugin, or have a feature request, or are happy with it, we'd appreciate hearing about it. Send us a message on our website, or email us!
When calling plugin functions as script steps, you will handle errors in the same manner you would any other FileMaker script step. Please see the FileMaker documentation for how to handle errors appropriately. Generally, if there is an error, our plugins will return an error code of 1552 when Get(LastError) is called. However, some plugin functions will return different error codes. If a function can return an error code other than a 1552, it will be documented with the description of the function below. In addition to the error code, you can also get the description of the error by calling Get(LastExternalErrorDetail). Please note that if you are using FileMaker 19.6 or later then this function has been renamed to Get(LastErrorDetail)
You can also call our functions in a calculation dialog. In this case, error handling is done differently. If you decide to call plugin functions in a calculation dialog and you want to capture errors, see this page page for instruction on how to do so
RemoteScripter allows you to remotely trigger FileMaker scripts on another computer. It can be triggered either by RemoteScripter running on a different computer, or by an HTTP URL. This plugin can safely be triggered from within the Web Publishing Engine, which makes it an ideal way to trigger non-web-safe scripts on a separate script processing computer. For example, let's say that your WebDirect or IWP application needs to be able to generate downloadable PDFs. You would define a script called "Generate PDF" which is designed to be run on a computer running regular FileMaker Pro at IP address 10.0.0.25. It might looking something like this:
Enter find mode
Set field Customer::customer ID to Get(ScriptParameter)
Perform find
Save as PDF
RemoteScripterSetResult("Success")
Now pick a random port number to run RemoteScripter on. We'll pick 4546, but it can be anything that does not conflict with another service running on the same port. You would have a startup script which calls:
RemoteScripterStart(4546, Get(FileName), "Generate PDF")
This tells RemoteScripter to trigger the Generate PDF script if it receives any requests on port 4546.
On the computer running WebDirect, you would have a button that the user clicks on to see the PDF. This button triggers a script which would look something like this:
if( RemoteScripterTrigger("10.0.0.25", 4645, Customer::customer ID) = "Success" )
Go to Layout (Download PDF)
else
Go to Layout (Show PDF generation error)
end if
You could also trigger the PDF generation script directly from a user's browser, without going through the web server. Just have a URL that looks like this:
<a href="10.0.0.25:4645?35">View customer record 35</a>
This will trigger RemoteScripter to run the script and return whatever is set with RemoteScripterSetResult().
You can use RemoteScripter to trigger scripts on your clients machines when they click links in a web viewer in your filemaker database. This allows you to design an interface in HTML, Java, Flash, or any language which can be displayed in your web viewer and then still trigger filemaker scripting. You can accomplish this by installing the Remote Scripter plugin on each of your client machines. You can then call the RemoteScripterStart function like in the example above (a startup script is a good place for this) and trigger the script using a link in your HTML to http://localhost:4645. The "localhost" url always points to the machine accessing it, so your users will trigger your script on their own machines when they click the link!
licenseKey - the license keycompanyName - the company or name the license is registered toemailAddress - The user's email address to allow for support contactproblemDescription - A description of the current issue
Set Variable[$errCap; Value: RemoteScripterSetError(True)]
errorCapture - set to true to suppress the default popups.HTTPcode - integer that specifies the HTTP code that is to be setheaders - String Array that specifies the headers and value pairs in a string array
The following starts RemoteScripter listening on port 9876. Incoming requests will trigger the Remote Scripter Callback Script script, passing in any URL parameters as key=value pairs, with the keys containing a $foo_ prefix.
RemoteScripterStart( 9876; Get(FileName); "Remote Scripter Callback Script" ; "variablePrefix=$foo_")
$key1="value1";$key2="value2". This makes it easy to pass the resulting string to the evaluate and let functions in FileMaker, which will populate local variables with the parameters from the URL.
For example, an HTML form with inputs for firstName, lastName, and notes will result in the following script parameter being passed in from RemoteScripter:
$notes="testing\ufffdone\ufffdtwo\ufffdthree";$firstName="Sam";$lastName="Barnum"
Evaluate ( "Let ( [" & Get(ScriptParameter) & "] ; true )" )
$firstName, $lastName, and $notes.
$", to facilitate the use of Let and Evaluate. For backwards compatibility with older versions of RemoteScripter (1.6 and earlier), pass an empty string for the variablePrefix. To prevent URL parameters from conflicting with variables, use a unique prefix for the variable name.portNumber - the port number you wish to use for listening for eventsfilename - The name of the filemaker database containing the script.scriptname - The name of the script which generates PDFsoptions - The optional variablePrefix. Adds the specified string to the beginning of all converted URL parameter keys.portNumber - the port to stop listening onremoteAddress - the hostname or IP address of the machine whose FileMaker instance is running the plugin.portNumber - this should be the same port number which was passed to RemoteScripterStart by the remote computer.paramText - Any arbitrary text to be included as a script parameter. It can be in the form of a single parameter (ie. "John"), or as multiple URL encoded parameters (ie. "firstname=John&lastname=Smith").timeout - Number value in milliseconds.