7 Ways 360Works Scribe Streamlines FileMaker Document Automation

• Set Variable [$template; Value: Template::Container] or file path
• Set Variable [$outputPath; Value: …]
• Set Variable [$jsonLineItems; Value: YourJSONBuildCalculation]
• Perform Script: Scribe Merge (or use Scribe.DoMerge function) with parameters mapping tokens to values

Concrete example using Scribe.DoMerge (pseudo-call):

Scribe.DoMerge (    Template: $template;    OutputPath: $outputPath;    FieldsJSON: {     "ClientName": "Acme Inc",     "InvoiceNumber": "INV-1001",     "LineItems": $jsonLineItems   } ) 

Adjust according to the exact syntax of your installed Scribe version. Use FileMaker’s Insert from URL or plugin script steps if required.

5. Handling repeating sections (line items)

If your template uses a repeating block ({{#LineItems}}…{{/LineItems}}), you must pass Scribe a structure it recognizes:

• JSON array of objects (preferred).
• Pipe/line-delimited lists or FileMaker repeating fields (older approach).

Ensure keys in each object match the inner tokens in your template. Example token block in Word:

Scribe will duplicate the row for each object in the array and replace tokens accordingly.

6. Formatting and conditional content

• Use Word’s native styles for consistent formatting. Scribe merges raw text into Word; preserve styles in the template for fonts, bold/italic, and spacing.
• For conditional content (only show a paragraph when a field has a value), use simple conditional tokens or prepare the content in FileMaker (empty strings to hide sections). Some Scribe versions support conditional sections like {{#IfField}}…{{/IfField}} — check your plugin docs.

7. Exporting, printing, and delivering documents

Scribe can save output as .docx, .pdf, or other formats depending on setup.

Common post-merge actions:

• Save to container field for storage in FileMaker.
• Export to a network folder for integration with other systems.
• Email the generated document using FileMaker’s Send Mail or SMTP plugin.
• Print directly via FileMaker or Scribe/OS printing facilities.

Example: Save merged PDF to container

• Merge to a temporary file path as PDF.
• Insert File into Container from path.
• Optionally delete the temp file.

8. Error handling and testing

• Test templates with edge-case data (long names, empty fields, many line items).
• Add script error checks after Scribe calls; capture return codes and messages.
• Log generated filenames and timestamps to a debug table during development.

9. Tips and best practices

• Keep template design simple: avoid complex Word fields that might interfere with token replacement.
• Version templates and store a change log in FileMaker.
• Use consistent token naming and document it for team members.
• For large batch generation, run merges on FileMaker Server or a scheduled script to avoid client interruptions.
• Back up templates and test after plugin or Word updates.

10. Example: Minimal invoice template & FileMaker flow

Word template tokens:

• {{ClientName}}
• {{InvoiceNumber}}
• {{Date}}
• Repeat block: {{#LineItems}}{{Description}} | {{Quantity}} | {{Price}}{{/LineItems}}

FileMaker flow:

1. Build $jsonLineItems.
2. Set $fieldsJSON with client and invoice values.
3. Call Scribe.DoMerge with template and $fieldsJSON.
4. Save returned file to container and present for preview.

If you want, I can:

• Provide a downloadable sample .docx template with tokens.
• Write exact FileMaker script steps tailored to your FileMaker and Scribe versions.
• Convert the pseudo Scribe.DoMerge example into the precise plugin calls your Scribe version requires.