A native RadStudio walkthrough
Documentation status: guide. Adapt this sequence to the target release; do not treat illustrative helpers as shipped APIs.
A customer-model execution path
The book's end-to-end example follows a Customer model through successive boundaries rather than claiming that one API call creates a complete system.
- Prepare the environment: select a compatible RadStudio toolchain, required packages, and the Runtime deployment; check prerequisites.
- Load source and metadata: the model defines class properties, collections, actions and services; loading resolves an APPLICATION metadata assembly.
- Activate runtime objects: the relevant
ClassItemrepresents a class at runtime; anObjectItemis a live object bound to metadata, actions and relations, not merely one database row. - Resolve the collection: select a collection provider from the declaration and configured Runtime. It may feed a dataset, service or client projection.
- Execute an action: check the target, parameters, result contract and applicable operationalization (declarative, functionalP, plug-in or service).
- Attach a view or endpoint: MVC or service publication projects the same application semantics without redefining domain identities.
- Exercise and close: test activated metadata, run one meaningful action, inspect diagnostics, stop services and release resources in the documented ownership order.
Things that must remain explicit
The source file, activated application model and semantic graph are not interchangeable. The example helper functions in the book are book-owned, not necessarily published Runtime methods. Native symbols mentioned in book listings require version verification before copying.
Next step by task
Declarative task application · Runtime object execution · Collections and views · Testing
LaTeX sources: runtime-end-to-end-walkthrough.tex; metadata-packages-and-plugins.tex; objects-container-and-runtime-models.tex.