Blueprint guide
Blueprint connects your business model to data, actions, and screens. Define the model once, then extend it as your application grows.
The core ideas
Each idea is explained, with a batch-production example, in core concepts.
| Idea | In one line |
|---|---|
| Entity | A thing with an identity, such as a batch or a piece of equipment. |
| Facet | One aspect of a thing. Another module can add one through a descriptor. |
| Relationship | How things connect: a batch runs on equipment and consumes material lots. |
| Action and rule | The only way to change, and when the change is allowed. |
| Lifecycle | The states a thing moves through. |
| Trigger, effect, task and workflow | What starts an action, what it asks for next, and work for people. |
| Ledger and revisions | Who did what, when, and why; and which governed revision applied. |
| Module, configuration, evolution | How the model is assembled, varied per site, and changed safely. |
Then read Why Blueprint, the three planes, and connected applications. The primitives catalog shows what runs today.
Build your first application
- Request package access.
- Choose the packages you need from the package map.
- Follow developer setup and the tutorial.
- Start your app with the CLI.
Keep working
Use development profiles to run your app and servers together. See developer commands for migrations and seed files, and errors and remedies when something goes wrong.