Learning paths

You do not need to learn all of Tryton at once. Each path combines concepts, practice, and safety checks.

Learning objectives

• User: navigation, searches, favorites, attachments, and business workflows. When finished, verify the result with a test record and document ownership.
• Finance lead: company, chart, journals, periods, taxes, invoicing, and reconciliation. When finished, verify the result with a test record and document ownership.
• Administrator: installation, permissions, backups, restore, logs, and upgrades. When finished, verify the result with a test record and document ownership.
• Developer: Pool, models, fields, PYSON, views, wizards, reports, migrations, and tests. When finished, verify the result with a test record and document ownership.

Concepts to master

• User: navigation, searches, favorites, attachments, and business workflows.
• Finance lead: company, chart, journals, periods, taxes, invoicing, and reconciliation.
• Administrator: installation, permissions, backups, restore, logs, and upgrades.
• Developer: Pool, models, fields, PYSON, views, wizards, reports, migrations, and tests.

Guided practice

1. Activity 1. User: navigation, searches, favorites, attachments, and business workflows. Perform it in staging first, record preconditions, and compare expected and actual results.

2. Activity 2. Finance lead: company, chart, journals, periods, taxes, invoicing, and reconciliation. Perform it in staging first, record preconditions, and compare expected and actual results.

3. Activity 3. Administrator: installation, permissions, backups, restore, logs, and upgrades. Perform it in staging first, record preconditions, and compare expected and actual results.

4. Activity 4. Developer: Pool, models, fields, PYSON, views, wizards, reports, migrations, and tests. 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.