Screen Templates - Best practices

1. Concept & Purpose

In Build.One, Screen Templates are reusable design patterns that provide the structural and functional foundation for ERP applications.

They define how a screen or process is laid out and interacted with, ensuring consistent handling of similar data types and processes across the system.

2. Benefits

• Consistency – Common UX and interaction logic across all modules.
• Maintainability – Changes to a template automatically improve all related applications.
• Efficiency – Faster creation of new modules by reusing proven designs.
• User Familiarity – Predictable navigation and behavior accelerate adoption.

3. Usage in Build.One

The core principle: For each recurring pattern in your ERP, define it once and store it as a template.

1. Identify the Pattern – Decide on the standard design for a process or data type.
2. Assign to an Entity Category:
• Entities – e.g., payment terms, countries, units of measure.
• Master Data – e.g., customers, products.
• Transaction Data – e.g., order headers, postings, goods movements.
• Tree Structures – e.g., bills of materials (BOM), hierarchies.
3. Store the Template – Save it centrally for reuse in all relevant applications.
4. Adapt Without Breaking the Pattern – Adjust only what’s necessary for the specific entity.

4. Best Practices for Modern ERP Patterns

1. Pattern → Template Rule – For every defined pattern, create and store a corresponding template.
2. Limit Variety – Maintain a manageable set (typically 6–10 patterns) to keep complexity low.
3. Align with Business Processes – Match templates to how the business searches, creates, and maintains data.
4. Integrate Actions – Combine search, view, and edit where it reduces steps and avoids redundant screens.

5. Example Core Patterns

(Use these as inspiration, not as a fixed list)

• Search Screen (Suchansicht) – Locate and filter entity records.
• Maintenance Screen (Verwaltungs-/Bearbeitungsansicht) – Edit and manage details.
• New Entry Screen (Neuanlage) – Add new records.
• Movement / Transaction Screen (Bewegungs-/Transaktionsansicht) – Process-specific workflows.
• Entity-Specific Templates – For unique structures like payment terms or BOMs.

6. Styling & Consistency Guidelines

• Naming – Clearly reflect the entity and function (e.g., “Customer Maintenance”).
• Visual Consistency – Use uniform colors, typography, and spacing across templates.
• Layout Standards – Keep controls, action buttons, and field positions consistent.
• Responsiveness & Accessibility – Design for usability on all devices and user groups.

• 1. Concept & Purpose
• 2. Benefits
• 3. Usage in Build.One
• 4. Best Practices for Modern ERP Patterns
• 5. Example Core Patterns
• 6. Styling & Consistency Guidelines

For detailed creation instructions, see

Screen Templates Screen Templates and

Create own custom templates Create own custom templates

Back to Use Cases

Back to Build.One Help-Center Home