For the case of an service provider organization-specific billing rate
for a worker we would not want the worker to choose which organization
they are associated with, we would want that setup as part of the
project.
Does that make sense? In this case using a global or user-selected
setting would be a bad thing as most businesses wouldn't want their
billing setup to be driven by such a thing.
-David
On Dec 4, 2008, at 2:49 AM, Hans Bakker wrote:
I am still getting the rate update into the system. David asked to
have
the organization company(party) added to the basic rate table.
This has rather big implications:
1. if i want to select any applicable rate in the system, i need to
know
the organization partyId.
2. if i generate an invoice for a project I have to know by which
organization the project is executed, this can be stored in the
'roles'
part and would be nice if could be added automatically.
3. if a project is done by more than one organization we even need
it on
the task level.
Shouldn't we have a organization partyId set in the preferences of the
logged-in user? or should we add the preferred organizationPartyId to
the userLogin?
I was only wondering why there is no check for userPrefTypeId in the
UserPreference entity? shouldn't that have a check against the enum
entity for example?
I saw there was discussion in the past but as far as i could see no
consensus....
so what is the opinion of the community?
Regards,
Hans
--
Antwebsystems.com: Quality OFBiz services for competitive prices
