Re: Dev - Party Application

Posted by Ean Schuessler on Apr 27, 2006; 3:20pm
URL: http://ofbiz.116.s1.nabble.com/Dev-Party-Application-tp167779p167783.html

On Wednesday 26 April 2006 23:12, Chris Howe wrote:
> I think the link to party instead of userlogin is to
> allow the same party to limit their permissions by how
> they're logged in (since one party may have multiple
> user names) but still be able to track all the actions
> of that person as one person.

I don't think it lets you do that. Since the association is by party, the
UserLogin will have no influence over the behavior of the application.

> Take for example the
> scenario that a sales rep has.  Having the current
> setup allows a sales rep to use one user name and see
> his cost for the product when he is in private.  Then
> have him use a different user name when he is infront
> of his client where he certainly doesn't want to
> reveal his cost, but rather his client's cost.  This
> allows the salesrep to learn only one application.  In
> addition if a username is abandoned, it doesn't
> abandon the record of the person.

Association by UserLogin would not prevent pricing by Party. Since there is
only one Party associated with a given UserLogin you can still do Party based
operations from the UserLogin. The only negative side effect is that all the
Parties in these types of roles (ie. Vendor, etc.) would have to have
UserLogins and that seems a little undesirable.

--
Ean Schuessler, CTO
[hidden email]
214-720-0700 x 315
Brainfood, Inc.
http://www.brainfood.com
 
_______________________________________________
Dev mailing list
[hidden email]
http://lists.ofbiz.org/mailman/listinfo/dev