Introducing the Communication Log

Most teams track conversations in email threads, chat, and spreadsheets. When you need the full picture on a client, order, job, or ticket, context is scattered. A Communication Log centralizes those touchpoints right on the record, so anyone can see what was said, by whom, and when without leaving FileMaker.

You get: faster handoffs, fewer “did anyone call them?” moments, and an audit trail you can trust.

What you can do with it (examples)

• Pin call notes, emails, and internal comments to any record

• See a chronological timeline of interactions in one place

• Load a log per customer, order, project, etc.

Requirements & compatibility

• Works with modern FileMaker versions that support Add‑ons (FileMaker 19+).

• Designed to drop onto any layout and point to your base table’s primary key

• Ships with two helper scripts: dialog_Create Message and dialog_Load WebViewer

Quick start (5 minutes)

1. Create the add‑on bundle

   • Download and open FileUploader-Addon.

   • Click Create Add‑on.

   • When the script finishes, close FileMaker.

2. Install the add‑on into your app

   • Reopen FileMaker and open the target file.

   • In Layout mode, open the left pane → Add‑ons → Install Add‑on.

   • Select CommunicationLog and click Choose.

3. Drop it into a layout

   • In the Add‑ons panel, drag the CommunicationLog onto the layout you want.

   • Restyle to match your theme (styles, fonts, colors).

4. (Optional) Support multiple contexts

   • Open the script dialog_Create Message.

   • Replace the hard‑coded IDs on lines 10 and 20 with your layout’s primary key field (e.g., Customers::CustomerID).

   • This lets you reuse the add‑on on different layouts (Customers, Orders, Projects) and keep each log scoped correctly.

5. Load behavior (recommended)

   • Trigger dialog_Load WebViewer on OnRecordLoad or OnLayoutEnter.

   • Pass the record’s primary key as a JSON parameter.

   • Use the example attached to the add‑on’s “Load Dialog” button as the source of truth for the correct JSON keys.

6. Example (generic):
   // Script trigger parameter
   JSONSetElement ( “{}”
   ; [ “ID_LOG” ; YourTable::PrimaryKey ; 1]
   )

How it fits into real workflows

• Sales/Account Management: Log calls and emails against a customer; see the full history before a renewal call.

• Service/Support: Tie notes to a ticket; cut back on “who said what” confusion.

• Operations/Projects: Keep vendor or internal coordination readable at a glance.

Styling tips

• Create custom object styles for headings, timestamps, and message text to match your app.

• Consider a light/dark background card for readability.

• If the add‑on exposes buttons (add, filter, etc.), map them to your theme’s button style.

Security & deployment

• Apply proper privilege sets so only the right users can add or edit messages.

• Test on a copy of your file before deploying to users.

Troubleshooting

• Add‑on doesn’t appear? Make sure you ran Create Add‑on and then restarted FileMaker before installing.

• Web Viewer is blank? Confirm the dialog_Load WebViewer script is firing and that you’re passing the expected JSON key(s).

• Messages not tied to the right record? Double‑check you replaced the hard‑coded IDs on lines 10 and 20 in dialog_Create Message with your primary key.

Download + next steps
Download the Communication Log (attached here)

Credentials for the demo: Admin / Admin (update before production).

Have 30 minutes? We’ll help you drop the add‑on into your file, point it at your primary key, and confirm the trigger/JSON parameter setup.

Appendix (for power users)

• Consider calling the load script on both OnRecordLoad and OnLayoutEnter if you allow record switching and fast layout navigation.

• If you need more than a single log per context (e.g., separate internal vs. external threads), duplicate the add‑on instance and drive each with a different context key.

• Source control: version your add‑on bundle and keep a lightweight readme of local changes for your team.