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. |
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. > smime.p7s (3K) Download Attachment |
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. |
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. > smime.p7s (3K) Download Attachment |
Just curious - how is a SalesOpportunity different from a Request (or
CustRequest in OFBiz)? What does SalesOpportunity model? -Adrian On 9/15/2011 7:19 AM, 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. >> |
In reply to this post by Scott Gray-2
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. |
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 (3K) Download Attachment |
then we have to agree to disagree?
Ok my last question, you are going to block this?' cannot spend too much time on this... Regards, Hans On Thu, 2011-09-15 at 19:08 +1200, Scott Gray wrote: > 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. > > > -- Ofbiz on twitter: http://twitter.com/apache_ofbiz Alternative ofbiz website: http://www.ofbiz.info http://www.antwebsystems.com : Quality services for competitive rates. |
Ask for comments and then ignore them, well done Hans. If you don't have time to wait for opinions and have proper discussions then keep your changes local until you do.
Regards Scott On 15/09/2011, at 7:33 PM, Hans Bakker wrote: > then we have to agree to disagree? > > Ok my last question, you are going to block this?' > cannot spend too much time on this... > > > Regards, > Hans > > On Thu, 2011-09-15 at 19:08 +1200, Scott Gray wrote: >> 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. >>> >> > > -- > 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 (3K) Download Attachment |
Ok sounds fair, let wait for other comments.
On Thu, 2011-09-15 at 19:37 +1200, Scott Gray wrote: > Ask for comments and then ignore them, well done Hans. If you don't have time to wait for opinions and have proper discussions then keep your changes local until you do. > > Regards > Scott > > On 15/09/2011, at 7:33 PM, Hans Bakker wrote: > > > then we have to agree to disagree? > > > > Ok my last question, you are going to block this?' > > cannot spend too much time on this... > > > > > > Regards, > > Hans > > > > On Thu, 2011-09-15 at 19:08 +1200, Scott Gray wrote: > >> 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. > >>> > >> > > > > -- > > 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. |
In reply to this post by hans_bakker
even if it is done automatically, all efforts cost time which is what
workeffort is about. This feed back to budgets. and since this system is about business, tracking cost is very important. on a coding level I think the Model for SFA is sprawl and could have been developed with in the frame work we have alreary. Using PartyRleationships the way the datamodel book implemented it would have made the dealing with things a lot easier and a lot less data handled. Hans Bakker sent the following on 9/14/2011 11:10 PM: > 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. >>> >> > |
In reply to this post by hans_bakker
I wonder if this business case is analogous to "Marketing Tasks" on
page 293 of Volume 2 of the Data Model book? Cheers, Anne. On 15 September 2011 18:12, Hans Bakker <[hidden email]> wrote: > Ok sounds fair, let wait for other comments. > > On Thu, 2011-09-15 at 19:37 +1200, Scott Gray wrote: >> Ask for comments and then ignore them, well done Hans. If you don't have time to wait for opinions and have proper discussions then keep your changes local until you do. >> >> Regards >> Scott >> >> On 15/09/2011, at 7:33 PM, Hans Bakker wrote: >> >> > then we have to agree to disagree? >> > >> > Ok my last question, you are going to block this?' >> > cannot spend too much time on this... >> > >> > >> > Regards, >> > Hans >> > >> > On Thu, 2011-09-15 at 19:08 +1200, Scott Gray wrote: >> >> 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. >> >>> >> >> >> > >> > -- >> > 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. > > -- Coherent Software Australia Pty Ltd PO Box 2773 Cheltenham Vic 3192 Phone: (03) 9585 6788 Fax: (03) 9585 1086 Web: http://www.cohsoft.com.au/ Email: [hidden email] Bonsai ERP, the all-inclusive ERP system http://www.bonsaierp.com.au/ |
Administrator
|
In reply to this post by hans_bakker
I did not look into details yet, but why SalesOpportunityWorkEffort exists if we don't use it?
Also I agree with Scott on 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 This is also what BJ outlined (the need of a WorkEffort) Also Anne's remark about "Marketing Tasks" on page 293 of Volume 2 of the Data Model book is worth reading (again WorkEffort), even if it's particularily in the Financials domain. Jacques From: "Hans Bakker" <[hidden email]> > Ok sounds fair, let wait for other comments. > > On Thu, 2011-09-15 at 19:37 +1200, Scott Gray wrote: >> Ask for comments and then ignore them, well done Hans. If you don't have time to wait for opinions and have proper discussions >> then keep your changes local until you do. >> >> Regards >> Scott >> >> On 15/09/2011, at 7:33 PM, Hans Bakker wrote: >> >> > then we have to agree to disagree? >> > >> > Ok my last question, you are going to block this?' >> > cannot spend too much time on this... >> > >> > >> > Regards, >> > Hans >> > >> > On Thu, 2011-09-15 at 19:08 +1200, Scott Gray wrote: >> >> 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. >> >>> >> >> >> > >> > -- >> > 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. > |
Free forum by Nabble | Edit this page |