Skip to main content
Version: Tryton 8.0 (LTS)

sale_project_task

Tryton 8.0 · Reference generated from the official source code

This page combines editorial guidance with evidence extracted from the selected official branch. Always test the flow with your own permissions and configuration.

Purpose​

The Sale Project Task Module adds the option to create tasks when selling services. The fulfillment of the sales is linked to the progression of these tasks.

The analysis found 5 Python files, 17 XML files, 14 views, 5 actions, 0 menus, and 0 reports.

Functional user guide

Who should use it​

This module is relevant to people responsible for sale project task processes, company configuration, and result review. Administrators should participate whenever dependencies, permissions, or sequences are introduced.

What you will be able to do​

After configuration, you will be able to identify the records added by sale_project_task, execute actions in the correct state, and understand the information shared with other modules.

Requirements and preparation​

Before activation, verify company, currency, users, and groups. Install and configure required dependencies first. When real data exists, rehearse activation and upgrades on a restored copy.

Activate dependencies first, review company configuration, and rehearse the complete workflow before production use.

Required dependencies​

  • currency — must be installed and configured before testing this module.
  • ir — must be installed and configured before testing this module.
  • product — must be installed and configured before testing this module.
  • project — must be installed and configured before testing this module.
  • sale — must be installed and configured before testing this module.

Optional integrations​

  • project_invoice — enables an additional integration; test the combination explicitly.
  • project_revenue — enables an additional integration; test the combination explicitly.
  • Activate the module and sign in again to load menus and permissions.
  • Review new company configuration options and defaults.
  • Assign groups to test users using least privilege.
  • Create small, verifiable master data before bulk imports.
  • Run one complete scenario from draft to final state and inspect related records.

Module objects and concepts​

  • product.product: groups 1 model(s), including product.product. These records form the information users inspect or modify during the process.
  • product.project_task: groups 1 model(s), including product.project_task. These records form the information users inspect or modify during the process.
  • product.template: groups 1 model(s), including product.template. These records form the information users inspect or modify during the process.
  • project.work: groups 1 model(s), including project.work. These records form the information users inspect or modify during the process.
  • sale.configuration: groups 2 model(s), including sale.configuration, sale.configuration.sale_method. These records form the information users inspect or modify during the process.
  • sale.line: groups 1 model(s), including sale.line. These records form the information users inspect or modify during the process.
  • sale.sale: groups 1 model(s), including sale.sale. These records form the information users inspect or modify during the process.

Typical workflow​

  1. Select the correct company and date before creating a document.
  2. Complete master data before lines or details.
  3. Use form buttons for state changes; saving is not the same as validating or posting.
  4. Review warnings, totals, related documents, and traceability.
  5. Verify effects on dependent modules before closing the process.

Actions, states, and wizards​

  • manual_task_creation — action or transition that starts manual task creation. Check permissions, current state, and related records before running it.
  • manual_task_invoice — action or transition that starts manual task invoice. Check permissions, current state, and related records before running it.

Controls before production​

  • Define who creates, reviews, confirms, cancels, and reads.
  • Test closed periods, unauthorized users, and incomplete data.
  • Verify numbering, currency, rounding, and time zone where applicable.
  • Document error correction without direct database edits.
  • Include its tables and files in backup and restore procedures.

Troubleshooting​

  • If a menu is missing, verify activation, module-list update, groups, and a new login session.
  • If a field rejects a value, inspect its domain, company, state, and configured dependencies.
  • If a button is hidden or disabled, check permissions and valid transitions; never change state with SQL.
  • If results differ, reproduce a minimal case and compare related records before and after.
  • Keep the full traceback, version, active modules, and minimal data needed to diagnose an error.

Developer guide

Architecture and extension points​

The package contains 10 Python classes and declares or extends 8 models. It uses Boolean, Char, Float, Function, Many2One, MultiValue, One2Many, Selection. Developers should first determine whether a class creates a model or uses PoolMeta to extend one, preserve super() calls, and avoid duplicating dependency rules.

Registered or extended models​

  • product.product
  • product.project_task
  • product.template
  • project.work
  • sale.configuration
  • sale.configuration.sale_method
  • sale.line
  • sale.sale

Field types used​

  • Boolean
  • Char
  • Float
  • Function
  • Many2One
  • MultiValue
  • One2Many
  • Selection

Detected classes and public methods​

Classes: Configuration, ConfigurationSaleMethod, Line, Line_Revenue, Product, ProjectTask, Sale, Template, Work, Work_Invoice

Methods: check_method(), copy(), default(), default_sale_task_creation_method(), default_task_creation_method(), func(), get_invoice_line(), get_sold_works(), get_tasks_progress(), get_tasks_revenue(), get_tasks_state(), get_works(), is_done(), manual_task_creation(), manual_task_invoice(), multivalue_model(), on_change_company(), on_change_product(), on_change_with_invoice_method(), on_modification(), set_quantities(), tasks_used(), view_attributes()

Code map​

Detected 5 Python files, 17 XML files, and 0 explicit access files. XML connects models to views, menus, actions, and reports; access CSV files establish initial permissions.

  • __init__.py
  • doc/conf.py
  • message.xml
  • product.py
  • product.xml
  • project.py
  • project.xml
  • sale.py
  • sale.xml
  • view/product_project_task_form.xml
  • view/product_project_task_list.xml
  • view/product_project_task_tree.xml
  • view/product_template_form.xml
  • view/product_template_list.xml
  • view/sale_configuration_form.xml
  • view/sale_line_form.xml
  • view/sale_line_form_revenue.xml
  • view/sale_line_list.xml
  • view/sale_line_list_revenue.xml
  • view/sale_line_list_sequence.xml
  • view/sale_sale_form.xml
  • view/sale_sale_list.xml

Test plan​

  • Activation on an empty database and upgrade from the previous revision.
  • Create, update, copy, and delete according to state and access rights.
  • Every button, transition, and wizard with valid and invalid scenarios.
  • Applicable multi-company rules, translations, time zones, and currencies.
  • Combined installation with required and optional dependencies.
  • Backup and restore of records, attachments, and generated reports.

Compatibility and upgrades​

Keep server and modules on series 8.0. Before upgrading, compare tryton.cfg, __register__ migrations, state changes, XML IDs, and permissions. A successful build does not replace a rehearsed migration or functional data reconciliation.

Official documentation evidence​

Topics found: Configuration · Design · Sale Project Task Module · API Reference · Setup · Usage

    • doc/index.rst: The Sale Project Task Module adds the option to create tasks when selling services. The fulfillment of the sales is linked to the progression of these tasks.

View source code