Build behaviour (Flow-Driven Development)
The Store
Free, tested flows, logic, system maps and whiteboards: try one on its page, fit it to your systems, and copy it in, or take its code.
Open Store in the appWhat's in it
The Store has free flows, logic, system maps and whiteboards, with clear names and version numbers (@rabbinatix/…). Nothing is installed: adding a package copies it into your organization or project, where it is yours to change. Or you take its generated code.
- Flows. A complete flow with its logic, APIs, data operations, test data, test cases and requirements, written for roles such as "Client app", "Auth service" and "User store" instead of your real systems. The built-in ones cover signing in (Email & password login, Sign in with Google, Two-factor sign-in (code), Sign out and refresh a session), accounts (Email & password registration, Verify an email address, Password reset request), payments (Place an order, Payment webhook) and everyday features (Upload a file, List, search and page, Newsletter sign-up). Each comes with its unhappy paths as test cases: wrong input, expired links, a declined card, an outside service that doesn't answer in time.
- Logic. Single functions you can call from any logic: text, money, validation, dates, lists, objects and data, basics and utilities.
- System maps. A set of systems and the APIs between them, such as an online shop. Add to my map adds them to your map in one go; systems you already have with the same name are reused.
- Whiteboards. Common journeys, drawn and ready. Use this whiteboard makes a new private draft from one, open and ready to edit, and Copy as text copies its text.
Packages for the same journey are linked as a kit. A flow's page lists Also as a whiteboard and Fits these system maps; a whiteboard's page lists Also as a flow; a system map's page lists the flows and whiteboards that fit it.
The Store has six tabs: Flows, Logic, System maps, Whiteboards, Added and Published by you. Search, filter by category and sort. You can browse without signing in; you sign in to add something.
Look before you copy it in
Open a flow to see:
- a lane preview, where the lanes are roles;
- the roles and what kind of system each needs;
- the APIs, data operations, test cases and requirements;
- its settings and optional steps, with their defaults.
Try it runs a test case on the preview, without writing anything to your organization or project.
Customize and copy in a flow
Press Customize & copy in. Four steps fit the template to your organization or project, with a Live preview on the right that compiles the result and runs its test cases after every change.
- Systems: for each role, pick one of your systems (the best match is chosen for you) or Create a new system…. Set the base path for each API provider.
- APIs & data: for each API and data operation, reuse one you already have or create it. Reusing compares the template's contract with yours. If your API already has logic, your logic is kept.
- Settings: values such as the token lifetime, optional steps such as publishing a login event, field names (for example
emailtousername), the flow's name and its owner team. - Review: what will be created and what reused, contract changes, compile problems and each test case's result. Leave Create tickets for new work ticked to get an API request per new endpoint and a task to implement the flow.
Press Copy in. Everything is created in one step, with fresh keys, and the new flow opens. Its test cases pass just as they did in the review. In a project that reviews changes before they go live, the copy waits in your changes: taking its flow back there takes back the rest, and the tickets it made are deleted too.
If you are missing a permission, step 1 says which and offers Request access.
Where copied objects came from
When the flow has a client app, its screens come too: Email & password login adds *Sign in* and *Welcome*, Email & password registration adds *Create account*. See Screens.
Copied flows, logic, test data and expected results carry a chip, such as "From the store: Email & password login v1.0.0", that links to the store page. The Added tab lists each one with its date, who did it, and what was created and reused.
Remove undoes it. Objects you haven't changed are deleted; ones you changed are listed and kept unless you tick them. Systems, APIs and operations you reused are never touched.
Logic packages
Open a logic package to see its README, How to use it, and Examples that run live on the page. Try it runs it on your own input, and the version select shows older versions.
- Add to my logic copies it into your organization or project as reusable logic. Call it from any logic with a Call Function step. See Reusable logic.
- Download code downloads a zip of the generated TypeScript, the runtime and a README.
- Copy code copies the code.
Once added, Added here on the package page shows each time it was added, what it created and where that is used.
Publish your own
Flows and functions you build can go in the Store too. See Reusable logic.
Related
- Reusable logic and packagesBuild functions that belong to no system and call them anywhere, add logic packages, and publish your own flows and logic.
- FlowsBuild a flow from the logic it starts at, see it cross your systems in lanes, and move it from draft to verified.
- Test cases and runsWrite test cases as acceptance tests, run the flow and watch it move through your systems, step back in time, and compare runs and versions.
- The board and ticketsTrack work as tickets on one board: types, columns, tags and sprints, mentions that open the exact place, and the planning views.
