Posted by
Nguyen Minh Triet on
Feb 02, 2006; 6:34pm
URL: http://ofbiz.116.s1.nabble.com/Users-Roles-and-Groups-and-Products-Bought-tp137162p137163.html
Hi,
Thanks Adrian for the info. From the looks of things, the solution you
proposed should allow us to meet our requirements.
Can you suggest any link, example or literature that would allow me to
fully understand each parameter involved and there interactions in the
creation of a 'Relationship'.
For example:
1. 'Parent Type' (of a relationship)
2. 'Valid From RoleType' and 'Valid to RoleType'
3. How does the RELATIONSHIP apply to the ROLES of parties for example,
as seen in the RELATIONSHIPS view of the PARTY tab:
'The party with ID... in the role of ... is a ... of the current party
in the role of ...'
Thanks,
Minh
Minh
---------------
Message: 4
Date: Wed, 01 Feb 2006 11:28:04 -0800
From: Adrian Crum <
[hidden email]>
Subject: Re: [OFBiz] Users - Roles and Groups and Products Bought
To: OFBiz Users / Usage Discussion <
[hidden email]>
Message-ID: <
[hidden email]>
Content-Type: text/plain; charset=us-ascii; format=flowed
Use PartyRelationship to tie the children to their parents. Your program
logic
can check for the existance of the relationship.
Nguyen Minh Triet wrote:
> Hi,
>
> I am looking closer at Parties. I am trying to see if a Parent-Child
> party logic can be implemented with what is currently present. For
> example, Party A buys a subscription to product X. Party B and Party C
> are said to both be 'children' of Party A. Party B and C both have
> access to what Party has bought but what child has bought is only
> available to itself.
>
>>From the Wiki, I see there are different notions applied to parties
such
> as Roles and Groups.
>
http://ofbizwiki.go-integral.com/Wiki.jsp?page=GroupsVsRoles>
> Questions:
>
> 1. Is it possible to create a Parent-Child structure for Parties or we
> will have to fiddle with groups and parties code to achieve this?
> 2. If such a structure can be laid out, can the products bought be
> propagated?
>
> I think the essential of this requirement of ours is that point 1 be
> present or implementable. Point 2 we can implement, I think, with some
> purchase history checks using the Parent-Child tree.
>
> Any suggestions or comments appreciated,
>
> Thanks,
> Minh
>
> _______________________________________________
> Users mailing list
>
[hidden email]
>
http://lists.ofbiz.org/mailman/listinfo/users>
_______________________________________________
Users mailing list
[hidden email]
http://lists.ofbiz.org/mailman/listinfo/users