Share
An organisation chooses to share a caseflow, a page or a service. Before it goes in, everything that points back to it is removed: names, suppliers, people, addresses and dates.
Start from what another organisation already built
The CaseFlows community is a shared library of open specifications: caseflows, pages and services that organisations chose to share. You take one over into your own platform, adapt it, and it stays yours.
Most processes have been designed before
A leave request, an expense claim, a job application, a quote: almost every organisation has them, and almost every organisation designs them from scratch. The differences that matter are usually small, a rule here, an extra approval there. The rest is the same work, done again.
Because a way of working in CaseFlows is written down in an open specification, it can be shared without sharing software or data. What travels is the design: the phases, the case roles, the fields, the rules. Your data never leaves your platform.
How it works
Find
When you ask for something new, the code assistant first looks in the library at how others did it, the way a designer looks at examples before drawing a screen.
Take over
What you take over is a copy in your own platform. You change it as you like. Nothing is ever merged into it automatically, and it never depends on the original.
Give back
Ran into something, or improved it? Through the code assistant you leave feedback on what you took over, anonymously, so the next organisation starts from a better version.
What is in it today
Counted each time this site is built, the same way as in the community overview of CaseFlows itself.
Shared by organisations
12caseflows
9concepts without a caseflow
1page
1service with its handlers
From CaseFlows
40caseflows
65concepts without a caseflow
A caseflow is a process with its phases, case roles and rules. A concept is the information it works with, such as a client or a project role. A page is a screen design, and a service is a task with the providers that can carry it out.
What runs today, and where it is going
Runs today
- The library itself, with caseflows, concepts, pages and services.
- The code assistant consults it before it designs something new, and through it you can take an entry over into your own platform.
- Feedback on an entry, without your name on it.
- Contributions go in after a review by CaseFlows, which checks that nothing in them points back to their source.
Where it is going
- Browsing the library yourself, not only through the code assistant.
- Sharing directly from your own platform, as a deliberate choice of its owner.
- Hearing when something you took over has a new version or new feedback, so you can decide whether to follow.
- Within a sector, organisations that start from the same contributions come to use the same words for the same things. That makes working together across organisations a matter of recognising, not translating.
Not an app store
- Open, not packaged. Every entry is an open specification you can read in full before you take it over, and keep if you ever leave.
- A copy, not a dependency. What you take over is yours. A change to the original never changes your process.
- Anonymous by default. Other organisations do not see who shared an entry or who uses it.
Want to start from the community?
Start with one process, and see what others already built for it.
Request early access