> Temporal database of business documents 

Here are the reason why I think we must keep track of printed documents instead 
of keeping temporal data:
* You must have the garantee to print exactly twice the same document. By 
keeping temporal data, you will not solve this problem. For example suppose 
that the company changes his header/footer.
* It does not work well with module inheritancies and features. Suppose you 
have temporal data on partners and addresses for invoices. Then you install the 
base_contact module that change them to add the contact concept. On invoices, 
you will see contacts and not anymore addresses. This may not work correctly 
with temporal data. 
* Using temporal data can be complex and heavy. It may slow down the database. 
You have about 10 tables that are linked to invoices: UoM, produts, partners, 
contacts, address, invoice lines, payment term, accounts, ... I don't imagine 
keeping a copy of all of them.

If you need temporal data just to keep track of changes, the audittrail does 
that correctly.

> To beat the drum one more time, Financial Statements. 
I agree, it's in the trunk (but not fully finished)

> We still need a way to have true multiple views of the same model/object. 
> We need this functionality to become part of Tiny/Open without the need to 
> resort to
> manual table manipulations. 
No need for manual operation, you can do that using the menu Administration > 
Custom > Low Levels > Actions

On the trunk, we now have new systems that allows you:
* to have access rights on fields (to hide/show fields according to user 
group).  This can be done through the view editor.
* put visibilities based on any field value (for example, if you set the type 
of a product to service, the volume and weight fields disappear).  This can be 
done through the view editor.
* use groups to show/hide fields: if you don't set 'Extended View' group to a 
user, all forms will be simplified. (we assigned extended fields to the group 
extended view). This can be done through the view editor.




_______________________________________________
Tinyerp-users mailing list
http://tiny.be/mailman/listinfo/tinyerp-users

Reply via email to