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
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
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
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
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.
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
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
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,
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
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
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 mailingl...@antwebsystems.com wrote:
Ok sounds fair, let wait for other comments.
On Thu, 2011-09-15 at 19:37 +1200, Scott Gray
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
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
-
13 matches
Mail list logo
