* associate Requirement Document to a validation workflow.
* set role acquisition to 0

git-svn-id: https://svn.erp5.org/repos/public/erp5/trunk@19812 20353a03-c40f-0410-a6d1-a30d3c3de9de

git-svn-id: https://svn.erp5.org/repos/public/erp5/trunk@16851 20353a03-c40f-0410-a6d1-a30d3c3de9de

Associate Task Report to delivery_causality_interaction_workflow.
Associate Task Report Line to delivery_movement_causality_interaction_workflow.

git-svn-id: https://svn.erp5.org/repos/public/erp5/trunk@16223 20353a03-c40f-0410-a6d1-a30d3c3de9de

git-svn-id: https://svn.erp5.org/repos/public/erp5/trunk@16026 20353a03-c40f-0410-a6d1-a30d3c3de9de

A project is no longer considered as an order (result of discussion of august 2006 and joint design with Rafael). Orders should hold the "offer" hierarchiczal structure (with requirements, people, etc.) while projects are only a tool for reporting and structuring tasks, accounting, etc. I implemented a quick and dirty project_workflow to make project usable in a configuration with security. But the project module has still be be reviewed to integrate what is useful in the sev project and to integrate all the design of august 2006. Same for order.

git-svn-id: https://svn.erp5.org/repos/public/erp5/trunk@14838 20353a03-c40f-0410-a6d1-a30d3c3de9de

git-svn-id: https://svn.erp5.org/repos/public/erp5/trunk@13001 20353a03-c40f-0410-a6d1-a30d3c3de9de

Task Report starts to use causality workflow.
Included builder to generate invoice from Tasks.

git-svn-id: https://svn.erp5.org/repos/public/erp5/trunk@10496 20353a03-c40f-0410-a6d1-a30d3c3de9de

git-svn-id: https://svn.erp5.org/repos/public/erp5/trunk@9984 20353a03-c40f-0410-a6d1-a30d3c3de9de

git-svn-id: https://svn.erp5.org/repos/public/erp5/trunk@7051 20353a03-c40f-0410-a6d1-a30d3c3de9de