In Sales (long sales) where is it possible to enter a reason for losing an #Opportunity?  We need a way of registering why the Opportunity was lost as well as linking to the competitor that ate our lunch.

Like 0

Like

1 comments

Hi John,

 

Within Opportunity, you could use the column "CloseReason" which is OOTB column. This could state the reason why it lost such as "No Budget" or "Lost" or "Stolen Lunch".

You could then use the column "Winner" which links to the "Accounts" lookup, to list the competitor who won the business - also an OOTB column

 

Hope that helps.

Show all comments

Dear Community,

Our business case requires us to prevent editting details and fields or adding new detail records after the opportunity has been closed (won or lost). We have some ways of doing it - run a business process that prevents write access, hide + button on details, disable save button, etc. 

 

But this use case sounds  a bit too common to us, as ideally, any opportunity must not be modified upon closure. 

 

We were wondering if there are any out of the box features that can handle this or any best practice that you all can suggest.

 

Thanks!

Like 1

Like

2 comments

Hi Shivani,

 

For section records, you can following this academy to block all fields based on lookup: https://academy.creatio.com/documents/technic-sdk/7-15/how-block-fields-edit-page

 

With this academy, it will hide all edit, add, delete action for detail also. But user can modifies by open detail edit page via double click action. If you want to prevent modifies details you can create process to update status to detail records and do the same with the academy above.

 

Regards,

Phuong Nguyen

 

The link provided by Phuong is a good route to go and the way I would do it. However, you can also do this in a process as well that triggers on a signal of opportunity modified where the stage is closed. You could just remove edit permissions for all access rights as well. Just thought I would mention this in case you wanted another approach. Note, if you go this route, you'll want to make sure any details on the opportunity inherit their permissions from the opportunity as well.

 

Ryan

Show all comments