FTF-101
Local development
Develop locally, no code change to promote
Web, portals, apps
A toggles file in your repository
- Your toggles live in a file committed with the code. Locally, and in CI, the client answers from it — the same answers FTF gives, checked against one shared set of cases.
- FTF's dashboard opens that file in your repository folder and edits it with the same screens used for FTF's environments.
- When you're done, you promote your changes into the first environment — like a Git push: only your changes go, and a conflicting change in FTF stops it.
- A deployment that can't reach FTF uses a toggles file exported from FTF, and its changes are imported back.
Guidewire InsuranceSuite
The same file, by design
- Designed the same way: the platform loads the same toggles file at startup, so a developer's local server behaves like any other environment.
- The design pairs it with a purpose-built toggle and release console — the same shape as the web one — rather than a generic settings screen.
- Available to design partners — talk to us. FTF GW client
No code change to promote from local to test to production — only the configuration each
environment supplies says where toggles come from.
| File | Committed? | What it holds |
|---|---|---|
config-ftf.json | Yes — identical everywhere | Your company's toggle prefix and the application's name |
toggles-ftf.json | Yes, with the code | The toggles, for local development and CI |
ftf-env.json | No — each environment supplies its own | FTF's address and the environment's key. Present: ask FTF. Absent: use the file |