Yes sure....but depending on the type of request I need to automatically add records to the CustRequestRole....
at creation time i can add the appropriate roles however when i want to change the allocation i have to go to all the places the request gets created..... so isn't is better to add a partyId to the customeRequestType entity? On Mon, 2008-07-14 at 07:58 +0200, Jacopo Cappellato wrote: > Hi Hans, > > why don't you use the CustRequestRole entity and (if needed) define a > special role for this? > > Jacopo > > On Jul 14, 2008, at 5:14 AM, Hans Bakker wrote: > > > > > I have a customer who wants to allocate an incoming customer request > > to > > an employee group, to be processed. > > > > Therefore i was thinking about to add a partyId field to the > > CustomerRequestType entity. This partyId can be a group which can > > relate > > to employees over the partyRelationship entity. > > > > anybody any objections or a better suggestion? > > > > Regards, > > Hans > > > > >
