Calculating the numbers of days a field has a specific content

I'm pretty sure you are looking for this article.

Thanks André for the incredible quick response ;-)

Do I need to worry about this prerequisite on top of the article you referenced ? 

• In the SugarBPM settings, there is a setting called "Error Number of Cycles" that specifies how many times a process can loop before the system stops the process definition. By default, this is set to 10. As we are counting days, this number should be increased to allow the process to run for more than ten days. Please note that in some circumstances, increasing the number of cycles could negatively affect performance.

In our business we have sales cycles that can run over months , years...?

Thanks again 

Hugo

Hi Hugo,

You can ignore coding for the number of days for an error to be thrown (unless you want it).  I have a number of processes where I have a "Number of Days in Process" and some of those have been running for more than a year.

Thanks Bud,

During the Connect days in Cologne recently, they talked about the Premier version too (we have Enterprise on premiss, v12). Did I understand it well that out of the (Premier) box , such things as tracking how long a field is in a specific state, can be done with one of the tools delivered with the Premier version ?

Bye now

Hugo

Hi Hugo Geyskens ,

Currently, the 'Change Timers' functionality exists for the Cases module to monitor the duration a case record remains in a status or user assignment. This was added to version 13 of Enterprise so you should see it in your next upgrade.

The framework is there to do something similar with Opportunities, but I am unaware of any planned enhancements to extend that functionality to other modules. 

Chris

OK, thanks Chris,

So I have to turn to BPM to solve that request.

Will be a nice first BPM project for me .

Bye now

Hugo

Correct, Hugo! We have Enhanced Forecasting in Sell Premier, which tracks the history of fields in the Opportunities module and creates reports so you can see (among other things) how long an opportunity has been in a given state. We are evaluating how to expand this capability to other modules in the future, but do not have a timeline for it yet.

Thanks Lydia

:-)

Hi Bud,

In the meantime I have everything up and running as described in the document André was referencing to.

Indeed the 10-value for process cycle limit doesn't seem to have any influence on the process. One record cycled up to 22 times.

Bye now

Hugo

Hi André,
That solution from last year works as charme since then.

Now I have a slightly different version of that question.

We have a custom text field 'Next Step' which our sales should regularly update. I'm ask to put a custom numeric field next to it, to show how many days ago this Next Step was updated.
Is there an easy way to achieve this ?
I was thinking about storing the actual text content and check each day via a BPM timer if it has changed. If not , counter goes up by 1, if it did, counter is reset to zero. Only thing is : how can I create this in BPM...

Thanks,

Hugo