Process definition

This solution isn't "pretty" :-)

Set a parallel path, one with "wait 30 days" which would move to whatever action you want, and a second path with a receive message set for "Date Modified changes" that would progress to the next step - which might be to just terminate the process.

Thank you Bud for you reply, the problem I see with this is that it will execute the process whether or not the date of last modification changed. It is an alert for the user, if the last modification date of the record does not change in 30 days , an email is sent informing that there were no changes in that record for a month

That is correct.  I said it wasn't "pretty".  You will have the process running for each record.  Depending on which happens first (30 days or a modification) the next step will be executed.  If the record is modified, you will need to terminate the process, if the 30 days pass you should terminate the process after the email is sent.

That is correct.  I said it wasn't "pretty".  You will have the process running for each record.  Depending on which happens first (30 days or a modification) the next step will be executed.  If the record is modified, you will need to terminate the process, if the 30 days pass you should terminate the process after the email is sent.

Thank you Bud, I now undestand with that image, I'm going to try this way  

Hi Perla Soto,

As Bud Hartley mentions, the solution to achieve this in SugarBPM is not pretty. There are a few additional things to consider. Using wait timers of such a long duration can introduce performance issues. If you have 1000s of records being modified in the module in a 30-day timeframe, I strongly recommend looking into a more performant option like a custom scheduler. 

Also, be aware of other things that can change the date modified of the record other than user interactions. If you have any Sugar Logic formulas in this module that pull data from related modules, the date modified will update each time one of the relate module records is updated. Additionally, if you have other SugarBPM processes, those can cause the date modified value to update if they make any changes to the record.

Chris

Agreed Chris!  It's not pretty, and if you have a lot of these it can impact performance.  Also, the Date Modified is changed based on many factors that may have nothing to do with a lead (or contact) interaction.  A custom scheduler is a much cleaner option.

I installed an add-on from the Marketplace called Last Activity:

https://www.sugaroutfitters.com/addons/last-activity-dates

Now, I'm looking at the Last Call and Last Email in a weekly Report instead of having a process that triggers a notice to the Sales Rep.

Hi Chris, You are right, we changed the criteria to a drop-down field, now the trigger is when the lead was converted to an account, this way it was easier for us to solve the process