Essential concepts

Tryton is a model-driven modular platform. Its interface, rules, and documents depend on company, user, and language context.

Learning objectives

• Model: data contract and business rules. When finished, verify the result with a test record and document ownership.
• Record: persistent instance of a model. When finished, verify the result with a test record and document ownership.
• View: form, list, calendar, or graph presentation. When finished, verify the result with a test record and document ownership.
• Action: opens models, runs wizards, or produces reports. When finished, verify the result with a test record and document ownership.
• Workflow: explicit transitions between states. When finished, verify the result with a test record and document ownership.
• Domain: expression that filters or constrains values. When finished, verify the result with a test record and document ownership.
• Context: execution information; it does not replace access rights. When finished, verify the result with a test record and document ownership.

Concepts to master

• Model: data contract and business rules.
• Record: persistent instance of a model.
• View: form, list, calendar, or graph presentation.
• Action: opens models, runs wizards, or produces reports.
• Workflow: explicit transitions between states.
• Domain: expression that filters or constrains values.
• Context: execution information; it does not replace access rights.

Guided practice

1. Activity 1. Model: data contract and business rules. Perform it in staging first, record preconditions, and compare expected and actual results.

2. Activity 2. Record: persistent instance of a model. Perform it in staging first, record preconditions, and compare expected and actual results.

3. Activity 3. View: form, list, calendar, or graph presentation. Perform it in staging first, record preconditions, and compare expected and actual results.

4. Activity 4. Action: opens models, runs wizards, or produces reports. Perform it in staging first, record preconditions, and compare expected and actual results.

5. Activity 5. Workflow: explicit transitions between states. Perform it in staging first, record preconditions, and compare expected and actual results.

6. Activity 6. Domain: expression that filters or constrains values. Perform it in staging first, record preconditions, and compare expected and actual results.

7. Activity 7. Context: execution information; it does not replace access rights. Perform it in staging first, record preconditions, and compare expected and actual results.

How to verify the result

• Company, user, language, time zone, and date match the scenario.
• Permissions allow only operations assigned to the responsibility.
• Changes are traceable and related documents remain consistent.
• The procedure is repeatable and has a documented correction path.
• A restored backup can reproduce the process without relying on production.

Common mistakes

• Confusing save with confirm, post, pay, or close.
• Testing only as administrator and assuming access rights work.
• Changing states or totals with SQL to bypass validation.
• Upgrading without inventory, restorable backup, and post-upgrade reconciliation.
• Documenting only the happy path while omitting cancellation, correction, and exceptions.

Developer perspective

Identify the models, fields, buttons, domains, and access rules involved. Before extending the process, locate the module that owns the rule, review its tests, and preserve invariants through super(). A correct customization must work across companies, languages, permissions, and states.

Production checklist

• Company, user, language, time zone, and date match the scenario.
• Permissions allow only operations assigned to the responsibility.
• Changes are traceable and related documents remain consistent.
• The procedure is repeatable and has a documented correction path.
• A restored backup can reproduce the process without relying on production.