Usage scenarios

One application, no FTF service

A single Guidewire application uses FTF's toggles on its own. Toggles are defined in a toggles file kept with the configuration; the application loads new ones when it starts and keeps them in its own database. Switching happens in its own toggle and release console.

A good start: trunk-based development and feature toggles in one application, with nothing else to run.

What you get, and what you don't yet

• Toggles, attributes, releases within the application, pending until implemented, history.
• The same Gosu call as in every other scenario — moving on later changes no code.
• Each environment is switched in its own console; nothing is promoted between environments for you.
• No releases across applications — that is the next scenario.

Integrated apps: policy, billing and claims on one FTF

Every Guidewire application in every environment connects to the FTF provider. FTF holds the toggles for each environment and tells each application to refresh its copy when something changes; each application still answers from its own copy.

What the business gets: one release switch takes a product change live in PolicyCenter, BillingCenter and ClaimCenter at the same moment; promotion carries tested settings from test to production with a preview.

How it runs

• One release across applications, each feature with its own kill switch. Releases
• Promotion upwards only, with a preview; production keeps its own release switch. Promotion
• Pending per application — a shared toggle stays off in an application until it's built there.
• Developers keep working offline, from the toggles file in their repository, and promote into the first environment when ready. Local development

Every other OFREP-compliant application joins the same FTF

Because FTF speaks OpenFeature's remote evaluation protocol, any OFREP-compliant application can use it: web and portals, and services in any language, alongside your Guidewire applications. A release spans all of them — a new product goes live on the website and in policy and billing with one switch.

Behind FTF, each environment's toggles live in FTF's own store, or in the LaunchDarkly or ConfigCat account you already have. Your applications only ever talk to FTF, so changing vendor — or moving to FTF alone — changes nothing in them. BYO provider

Each platform the way it works best

• Web and portals ask FTF directly, with FTF's small JavaScript client or OpenFeature's web SDK.
• Guidewire applications keep their own copy and evaluate inside the application. FTF GW client
• Any other service uses OpenFeature's own SDK for its language — no FTF library. Open standards
• Every one gives the same answer for the same customer, held to one shared set of test cases.