BPM - creating copy of same module

In Sugar Sell 10.1, a new feature was introduced which addresses this need, but similar to Neeraja, it is at the Opportunity level as opposed to Quote. Basically, if you have an Opportunity which includes renewable Revenue Line Items (e.g. a subscription), Sugar will detect that when you mark the Opp as Closed Won, and generate you a new Opp for next year (or however long your service runs for).

https://support.sugarcrm.com/Documentation/Sugar_Versions/10.1/Sell/Application_Guide/Opportunities/#Services_and_Renewable_Revenue_Line_Items

This new feature is really nice and I hope it makes its way to the Quotes module.  I'd like to see the Opportunity and Quote modules tied much more closely together to remove some of the repetitive data entry required to keep Opportunities and Quotes in sync.

Justin Kuehlthau,

When using RLI (Revenue Line Items), from an Opportunity, it is possible to create the matching Quote.

1- open Opportunity record

2- navigate to RLI subpanel

3- select all RLI that you want to quote for

4- click on "Generate Quote"

5- save the record

Hope it helps

Hi Enrico Simonetti,

The problem is that after the Quote is worked, modified and Won, users have to manually update the Opportunity to reflect the state of the Closed Won Quote.  This manual process is tedious and leads to errors.

Some of these new features, and data structures, have encouraged me to rethink the way "we've always done it" in Sugar. I know a number of customers where exactly what you've described is what occurs - and we used to set up logic hooks to address it.

However, using the feature that Enrico described, it is possible that I might start advising a different flow,i.e.

1. Generate the quote as per his directions.
2. If the client requires changes to line items, make those changes at the Opp>RLI level
3. Generate a new quote to reflect the current state of line items
4. Repeat steps 2-3 until Quote is accepted

In this way, the Opp already reflects the latest state of the Quote, i.e. are in sync. The other ideal part of this is that the intended logic around creating renewal opportunities will flow perfectly down - since RLIs are already at their latest state.

Some of these new features, and data structures, have encouraged me to rethink the way "we've always done it" in Sugar. I know a number of customers where exactly what you've described is what occurs - and we used to set up logic hooks to address it.

However, using the feature that Enrico described, it is possible that I might start advising a different flow,i.e.

1. Generate the quote as per his directions.
2. If the client requires changes to line items, make those changes at the Opp>RLI level
3. Generate a new quote to reflect the current state of line items
4. Repeat steps 2-3 until Quote is accepted

In this way, the Opp already reflects the latest state of the Quote, i.e. are in sync. The other ideal part of this is that the intended logic around creating renewal opportunities will flow perfectly down - since RLIs are already at their latest state.