Concepts
Configuration Scripts Ownership
After integration, you own the `ProofChat Integration` folder (Configuration + Custom Tools). The `ProofChat` folder remains owned by ProofChat and can be safely updated.
Summary
- Purpose: Make ownership boundaries explicit so you can upgrade without fear
- Audience: Developers integrating and maintaining ProofChat in a FileMaker solution
- Prereqs: /docs/integration/
Ownership at a glance
The highlighted area shows what scripts you own after integration.
What you own (safe to edit)
ProofChat Integration/Configuration/: Configuration scripts that ProofChat calls by name. These live in your file and are designed for you to edit.Custom Tools Examples/: Example scripts and patterns you can copy, adapt, or replace with your own tools.
Changes you make here are part of your solution and are preserved across updates.
What ProofChat owns (do not edit)
ProofChat/: The application folder—UI, engine, and assets provided by ProofChat. Treat this as read‑only. Updates may replace files in this folder.
How updates work
- Your configuration scripts remain in place; ProofChat continues to call them by name.
- Updating ProofChat may add, remove, or change files only in the
ProofChat/folder. - Because your scripts live under
ProofChat Integration/, upgrades should not overwrite your work.
Naming contract (important)
- Keep the provided configuration script names unless a page explicitly says otherwise. ProofChat locates these scripts by name.
- If you rename or relocate scripts, update any references accordingly.
Related
- Configuration Scripts - Main configuration documentation