We have discovered and further verified with FileMaker Inc. that when Get(ScriptParameter) is used on a graphical object (Button) that the scripting stack wipes out the Get(ScriptParameter).

Scenario:

1. Script is fired to perform a find and a series of parameters are embedded in the button firing the script.

2. During the script run the user has the option to direct the active script process in another direction, cancel, create, move records to another department or user.

3. The user clicks a button on the interface while the current script is active or has ended. In FileMaker 10 the design would allow for Get(ScriptParameter) to capture the previous script or active scripts parameters. From there you would be able to invoke conditional changes and run a secondary script.

4. Due to this bug in FileMaker 11 the process above that would work in FileMaker 10 will fail by not capturing the previous script Parameter.

Is this relevant? For some readers no, and yes for others. Out of the box FileMaker templates are not affected by this, however more complex workflow automations that use Get(ScriptParameter) in a Button when triggering a script will fail. Note the Get(ScriptParameter) embedded in a PerformScript step within a script is not affected.

FileMaker as of today has not announced an update that will fix this bug. That being said we expect in the coming months FileMaker will provide and update for this bug and others that have been reported to FileMaker Inc.

I thank Robert MacKay of FileMaker Tigers for taking the time to confirm my findings on this, further the team at FileMaker for taking a solid look at this reported bug.