FM BetterForms
BF Editorfmbetterforms.com
1.0 dont use
1.0 dont use
  • Introduction
  • Features Summary
  • Getting Started
    • System Overview
    • Integration
      • 1. Configure FileMaker Server
      • 2. Add your Server to BetterForms
      • 3. Introduction to Hooks
      • 4. Create your first Site
      • 5. Create your first Page
      • 6. Configure your FileMaker File(s)
      • 7. Run your first Hook
      • Next Steps
    • Common Customizations
      • Introduction to Actions
      • Introduction to Buttons
      • Page Navigation
      • Displaying Data in a Table
    • Support
      • Hacking a Webpage
      • Learning JSON
  • Reference
    • Site Settings
      • Navigation
      • Slots / Code Injection
      • App Model
      • Site-wide Named Actions
    • Page Settings
      • Data Model
      • Card / Window Modals
      • Validation
        • Custom Validators
      • Misc Page Settings
    • Page Elements
      • Common
        • Button
        • Data Table
        • HTML
      • Grouping Elements
        • Tabs
        • panel
        • accordion
        • listrows
      • Uploading Files
        • dropzone
        • dropzone to S3
        • uploadCare
      • Misc Elements
        • Plain Text / Code Editor
        • signature
        • fullCalendar
        • rangeSlider
      • Payment Gateways
        • Authorize.net
        • PayPal
        • Stripe
      • Adding Custom Page Elements
    • Actions Processor
      • Named Actions
      • Actions
        • runUtilityHook
        • path
        • debounce
        • throttle
        • showAlert
        • showModal / hideModal
        • function
        • clipboard
        • cookie
        • setFocus
        • wait
        • emit
        • validate
        • channelJoinAnon
        • channelLeaveAnon
        • messageSend
        • messageSendAnonChannel
      • Authentication Actions
    • Script Hooks
      • Globals Variables
        • $$BF_Model
        • $$BF_App
        • $$BF_State
      • Keeping Keys Private
      • Reducing Payload Size
      • API Callback Endpoint
      • Common Hooks
      • Scoped Hooks
    • Users & Authentication
      • Managing User Accounts
      • Custom Login Pages
    • Advanced Configuration
      • Custom Domains
    • BF Utility Functions
    • BF Error Codes
    • Messaging
      • Adding users to channels
      • Removing users from channels
      • Sending messages
      • Get connected users
      • Get active channels
  • Usage Tips
    • Troubleshooting
      • Debugging
      • Frozen Actions Queue
    • JavaScript Tips
      • Calling Named Actions from HTML Vue Events
      • Calculations
    • System Overview
    • Forms Processor
      • Form Types
      • HTML & VueJS
      • Styling and Design
      • JS Caclulations and Functions
    • Customizing and Styling
      • Custom Components
      • Custom CSS
      • Custom Components
      • Page Pre-loaders
      • Favicon
    • Design Patterns and Best Practices
      • Working with environments
      • Handling Data
      • Saving Data
      • Optimization
      • Business Logic
      • UI / UX
  • Security
    • Authentication
    • Security White Paper
    • Firewalls
    • Technology Stack
  • Compatibility
Powered by GitBook
On this page
  • What exactly do you mean by "legacy FileMaker file"?
  • Install Custom Functions
  • Install Scripts
  • Reconnect the Helper File

Was this helpful?

  1. Getting Started
  2. Integration

6. Configure your FileMaker File(s)

Now that BetterForms is properly configured, let's finish integrating your legacy FileMaker file(s) so that we can test the entire workflow through BetterForms.

Previous5. Create your first PageNext7. Run your first Hook

Last updated 3 years ago

Was this helpful?

The BetterForms contains some preconfigured custom functions and scripts that will help you interact with BetterForms. On this page, we'll insert these into your legacy FileMaker file.

What exactly do you mean by "legacy FileMaker file"?

If you only have 1 FileMaker file in your solution, that is the legacy file we're referring to.

If you have multiple files, or wish to create a new "API" file for stronger separation of Business logic, the custom functions and scripts are only needed in a single file. Paste them into the file that will be handling your logic for all BetterForms requests.

Remember that each FileMaker file that BetterForms will interact with needs to have the same user credentials. Your BetterForms user account should be [Data Entry Only] with the XML and Data API extended privileges enabled.

Install Custom Functions

  1. Open the helper file on your server, navigate to the integration tab and select step 1. This will copy the custom functions to your clipboard.

  2. Paste these custom functions into your legacy FileMaker file.

Install Scripts

  1. Back in the helper file's integration tab, click step 2.

  2. Enter the same common hook set name that you configured for your Site in BetterForms.

  3. For your first scoped hook set, enter the name of the Scoped Hook Set that you chose for your first page.

  4. A set of scripts will now be on your clipboard. Open the Script Workspace of your legacy FileMaker file and paste in the generated scripts.

Reconnect the Helper File

Now that your legacy file has all of the scripts needed to function, we need to do one last step in the Helper file to connect them both.

  1. Open the Script Workspace in the Helper file and locate the Hooks - Developer - Transmitter- CONFIGURE HERE script.

  2. Edit the Perform Script step to run the Betterforms - App - Receiver and Dispatch script in your legacy file. You will need to add the legacy file as an additional FileMaker Data source to the helper file.

The helper file can route multiple BetterForms sites through the helper file. Branching by the site's domain is the most common, but you can configure multiple sites in any way that you see fit in this script.

Edit the else if branch to the domain you configured in your .

Helper file
site settings