It really doesn't seem very difficult to me and coupling SalesOpportunity and WorkEffort will give you much more flexibility in the future.
Regards Scott On 15/09/2011, at 7:00 PM, Hans Bakker wrote: > I do not agree, i want to list all commevents on an opportunity which > gets now too difficul > > Hans > > On Thu, 2011-09-15 at 18:19 +1200, Scott Gray wrote: >> Not necessarily every communication event, but if it requires action then a >> WorkEffort seems like the logic choice to track the work done. >> >> If you were to send more emails in connection with the opportunity then they >> would be linked to the existing WorkEffort. >> >> Ask yourself this, why is there a SalesOpportunityWorkEffort entity? What >> purpose does it fulfill if not the type of problem that you are describing >> here? >> >> Regards >> Scott >> >> On 15/09/2011, at 6:10 PM, Hans Bakker wrote: >> >>> Sure I am all in favor to use the existing datamodel, this means however >>> that every communication event will have a workeffort connected to it >>> because somebody has to handle it? sounds a it bureaucratic?, >>> >>> then as a result of the creation of the opportunity more emails are sent >>> from the opportunity, we need a workeffort to create another >>> communication event? What kind of information the workeffort adds? >>> >>> Regards, >>> Hans >>> >>> >>> On Thu, 2011-09-15 at 17:37 +1200, Scott Gray wrote: >>>> It is possible to have a link between CommunicationEvent and >>>> SalesOpportunity via SalesOpportunityWorkEffort -> WorkEffort -> >>>> CommunicationEventWorkEffort. >>>> >>>> The business case could be redescribed as: >>>> - Email Received (CommunicationEvent) >>>> - WorkEffort created to handle the communication >>>> - Communication deemed to be a sales opportunity and record is created >>>> >>>> Regards >>>> Scott >>>> >>>> On 15/09/2011, at 4:13 PM, Hans Bakker wrote: >>>> >>>>> Business case: >>>>> An email is received requesting more information about certain services >>>>> where the originator could be interested in. >>>>> The support person receives the email and creates an opportunity in SFA >>>>> for the sales people. >>>>> >>>>> Problem: >>>>> currently it is not possible to have a link between CommunicationEvent >>>>> and SalesOpportunity entity. >>>>> >>>>> Proposal: >>>>> create a new entity: >>>>> SalesOpportCommEvent: >>>>> key: salesOpportunityId, communicationEventId >>>>> >>>>> comments please? >>>>> >>>>> Regards, >>>>> Hans >>>>> >>>>> >>>>> -- >>>>> Ofbiz on twitter: http://twitter.com/apache_ofbiz >>>>> Alternative ofbiz website: http://www.ofbiz.info >>>>> http://www.antwebsystems.com : Quality services for competitive rates. >>>>> >>>> >>> >>> -- >>> Ofbiz on twitter: http://twitter.com/apache_ofbiz >>> Alternative ofbiz website: http://www.ofbiz.info >>> http://www.antwebsystems.com : Quality services for competitive rates. >>> >> > > -- > Ofbiz on twitter: http://twitter.com/apache_ofbiz > Alternative ofbiz website: http://www.ofbiz.info > http://www.antwebsystems.com : Quality services for competitive rates. >
smime.p7s
Description: S/MIME cryptographic signature
