• Description
• Benefits
• Best Practices for ERP Patterns
• Example Core Patterns
• How to use it
• Styling & Consistency Guidelines

Description

In Build.One, Application Templates are reusable design patterns that speed up ERP application development.

They define the structure, layout, and interaction logic for typical screen types, allowing you to build new modules faster and more consistently.

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

Templates can be created for:

• 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

By reusing these templates, you ensure consistent user experience, reduce maintenance effort, and align screens with core business processes.

Benefits

• Consistency – All modules share a unified design language.
• Faster Development – Start from proven templates instead of building from scratch.
• Lower Maintenance – Central updates automatically improve all dependent screens.
• Improved UX – Predictable navigation and behavior across the ERP.

Best Practices for ERP Patterns

1. Pattern → Template Rule – Every defined pattern should have a stored template.
2. Limit Variety – Keep a manageable set (typically 6–10 patterns) to avoid overcomplication.
3. Align with Business Processes – Map templates to entity lifecycle: search, create, maintain.
4. Integrate Functions – Where possible, allow editing and actions directly from search or overview screens.
5. Reuse Across Entities – Adapt patterns for different entities without creating unnecessary duplicates.

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.

How to use it

1. Create a screen
2. Design it with the placeholder objects

Object	PlaceHolder Object
Datasources	designPhDatasource
Grids	designPhGrid
Forms	designPhForm
Toolbars	designPhToolbar
Ribbons	designPhRibbon

3. Connect them in the flow designer to reflect your screen flow
4. Save your screen
5. In the screens overview and search for the attribute “Template Object” in the “List of Screens” and set it to ‘true’ for your newly created template screen and select “save”
6. Next time you create a screen the template will be selectable

Styling & Consistency Guidelines

• Naming – Use clear, descriptive names (e.g., “Customer Maintenance Screen”).
• Visual Standards – Apply consistent colors, typography, and spacing across templates.
• Layout Consistency – Keep key controls and navigation in predictable locations.
• Accessibility & Responsiveness – Ensure usability on all devices and for all user groups.

Back to Documentation

Back to Home Page