PROPERTIES INSIDE ASSOCIATIONS

[tfpadilla]

I have created a custom model and to sum up my case, lets say I have two types of documents:

Invoices and Proofs of Payment..
I have an association between them, but the matter is that I can have:

One Proof of payment that includes parcial payments of several invoices.
For that reason I'd need to specify the porcentage payed for each association I specify between the proof and the invoices.

what I pretend is that everytime a user set an association with an invoice, a field (relative to the assoc.) might be filled with the %.

Could anyone help me with it or give different ideas to have what i need?

Thans in advance,
Teresa

[pmonks]

Provided the Invoices aren't shared between multiple Proofs of Payment, could you store the percentage contribution of each Invoice in the Invoice itself, rather than storing a set of (Invoice association, percentage) tuples in the Proof of Payment?

Cheers,
Peter

[tfpadilla]

First of all, thanks a lot for your instant reply, Peter.

The procedure  I though was:

Once the invoice arrives at the company, one user updloads it to invoices space.
Later, when we begin to pay it, one user uploads a proof of payment to the proofs space.
Since one proof can contains partial payments of several invoices, I thought that in the same process of uploading the proof, the user could set the percentage of payment of each invoice involved in this proof of payment.

Like you suggest, the user should upload the proof and then go to the invoices space, look for each invoice involved, edit the details of each one and set the percentage of each one.

I just wanted to minimize the users work.

What do you think?

Thanks again.

[pmonks]

Yep that's the trade off - increased data entry effort when the Proofs of Payment are created.

Another option would be to leave the content model as described above, but implement a custom Proof of Payment upload UI (eg. as a dashlet) that programmatically populates the different entities (invoices & proofs of payment) from a single form submission.  That way you still get the benefits of a simpler content model, and the benefits of an optimised UI.

Would that approach work, do you think?

Cheers,
Peter

[tfpadilla]

That sounds great.
Now,lets see if i know how to do it ( I am a newbie in Alfreco).

Thanks again,
Teresa