Records, fields, relations, UI surfaces, matching, and demo data.
01 · Templates
Business templates should accelerate setup without taking ownership away.
Moltaro Templates are designed as guided business starters: they can prepare records, processes, reports, roles, demo data, and operational logic, then leave the applied result as ordinary Moltaro configuration your team can keep changing.
A template can describe one object, one process, or a whole starter system.
The same planning model can stay small for a reusable business object or grow into a composed business starter when the operation needs records, stages, reports, security, and setup guidance together.
Preview plan
Business starter
A guided template proposes configuration before anything is applied.
Boards, stages, actions, routing context, and responsibility.
Objects, process, reports, roles, reference data, and post-apply work.
A reusable business object such as person, organization, asset, request, contract, order, product, inspection, or reference data.
A repeatable workflow surface such as complaint handling, fulfillment, onboarding, approval, procurement, or service request routing.
A composed starter that combines objects, boards, reports, roles, seed data, logic, and post-apply checklist for a business scenario.
Templates should create useful configuration, not only placeholder tables.
A business starter is valuable when it prepares enough of the operational system to review, adapt, and start training with realistic data.
Entity definitions, fields, child tables, references, constraints, matching intent, and reusable dictionaries.
Table, form, card, detail, drawer, and action surfaces that let users work with the generated object immediately.
Board definitions, columns, status mappings, item context, and route hints when the business pattern includes process.
Validation, before-save mutation, actions, triggers, schedules, and generated NetOperationProject source when behavior is part of the starter.
Recommended role sets, mappings to existing roles, assignment presets, field-access guidance, and post-apply security tasks.
Synthetic demo records, reference dictionaries, runtime navigation proposals, and cleanup tracking for safe evaluation.
A template should show its plan before it changes the workspace.
The plan explains what will be created, reused, skipped, warned about, or blocked. That keeps setup fast without making the workspace mysterious.
Select the business patternPick a template, answer the guided questions, and resolve required dependencies.01
Review the generated planSee artifacts, compatibility checks, collisions, warnings, and optional plan items before apply.02
Create ordinary configurationMoltaro applies selected items through normal services so validation, audit, and security rules still matter.03
Keep changing the resultAfter apply, entities, boards, functions, roles, and reports are normal workspace configuration.04
Templates should connect to what the customer already modeled.
A good business starter does not duplicate a customer, asset, product, or team structure just because it needs one. It asks whether to reuse a compatible object or create the missing one.
A request template can ask for a customer object; an order template can ask for customer and product objects; a property template can ask for owner, tenant, unit, and inspection objects.
Existing objects can satisfy a slot when they expose the capabilities the template needs, with explicit mappings where fields differ.
Collisions, incompatible objects, and unresolved choices should appear in preview instead of being hidden behind automatic guesses.
The catalog can grow by business pattern, not by empty screens.
The public promise is a catalog of useful starters that can be composed over time. Each one should still produce editable Moltaro configuration.
Person, organization, household, contact person, affiliation, branch, and party-role structures.
Complaint intake, support case, claim review, service request, incident, or application workflow.
Order, quote, order line, product or service catalog, totals, status, and fulfillment context.
Property, building, unit, lease reference, inspection, maintenance request, service provider, and location context.
Member, program, enrollment, cohort, attendance, benefit, entitlement-like access, or reporting starter.
Assets, equipment, rooms, checklists, findings, evidence, corrective actions, and recurring review.
Templates matter because they create a system, not a one-off demo.
The strongest starters connect records, boards, reports, security, demo data, runtime navigation, and C# extension points while keeping every artifact editable after apply.