wolfnero.blogg.se -

The implementation of this workflow is opinionated.

User interacts with the web viewer, triggering additional flows of requests and responses to and from FileMaker.

Note: Steps 2 and 3 may repeat multiple times before user interaction

Web project sends a request to FileMaker.

Web project is deployed in a web viewer.

To allow us to utilize script and function results in our web integrations, we follow a workflow that manages the movement of data (and metadata) between our web components and our FileMaker solution. A web viewer workflow without limitations 🙂 Read on to see how a well-implemented web viewer workflow can overcome these limitations. And the result of the FileMaker.PerformScript function in JavaScript is “undefined” even if that script returns a result in its “Exit Script” step. That is, the result of the function called by the Perform JavaScript in Web Viewer step is not stored. While immensely powerful, both of these features share the same limitation: They cannot directly get results from the scripts or functions they run. More information on these features can be found in the FileMaker help. To use this function the new option “Allow JavaScript to perform FileMaker scripts” must be turned on in the web viewer setup.įileMaker.PerformScript('Handshake', 'Hello FileMaker') It allows us to run a FileMaker Script directly from a web viewer. Specifically, we can call a JavaScript function in a web viewer and include (text) parameters in that function call.įrom web viewers to scripts: FileMaker.PerformScript JavaScript functionįileMaker.PerformScript is a special JavaScript function accessible within web viewers. As the name suggests, the method for doing this is JavaScript. The Perform JavaScript in Web Viewer script step allows us to manipulate structure, style, and content in a FileMaker web viewer.

the FileMaker.PerformScript - a JavaScript functionįrom scripts to web viewers: Perform JavaScript in Web Viewer script step.

Perform JavaScript in Web Viewer - a FileMaker script step.We leveraged two key tools to fulfill our requirements:

We will now see how these these dynamic form (and interface) requirements were fulfilled in FileMaker with the help of web technologies. The interface for our Stack should be visual and dynamic Add a new Thing, and now you’ve Stacked It (Click image to open in new tab) Users can change the shape of a Thing by dragging its edges Resize a shape by grabbing and dragging (Click image to open in new tab) Users can dynamically add and edit structured data about Things Dynamically add a new field, including a label (Click image to open in new tab) Below we list these requirements and demonstrate their delivery. Stacked It is a simple app but it has some requirements that have been traditionally difficult to deliver in FileMaker. In Stacked It these Things can be physical, remembered or imaginary - anything! You add Things to a Stack, starting out as shapes, and then scroll through it at your leisure, making tweaks along the way.ĭownload the app demo file, Stacked_It.fmp12. Our dynamic web form is demonstrated in Stacked It, an app about Things. Traditional FileMaker layouts are semi-dynamic to a degree, but they lack the auto-sliding of web interfaces and have very limited animation options.Īs well as giving us access to new widgets and controls, we will see how web interfaces allow us to be specific about which controls show on layouts without worrying about running out of space, dealing with gaps between fields or a general excess of white space. When we say a form is “dynamic”, we mean that the form’s appearance can be altered at multiple points before and during the data entry process. This post shows how we can build dynamic data-entry forms for use in our apps. Using the FileMaker platform we can harness the power and wow-factor of modern web interfaces.