I am looking at possible ways to define an account as 'active' or 'inactive'. A simple checkbox will do the trick to identify this however I am stuck on how to define it as a process (looking to automate). Initially I thought about defining it as:
Accounts>Date Modified - 3 weeks
However that poses an issue because an account does not necessarily get updated when a related record is added/modified.
Has anyone done this before and/or have some insight how I could go about it?
Hi Braedon,
Basing automation off date modified could also result in false positives since there are times the account record is updated (e.g. changing assigned user, an integration pushing some data into the record, etc.) that don't signify meaningful activity.
Can you elaborate more on your use case? What is the purpose of the active/inactive designation and are there specific correlating events that trigger a status change or ensure an account remains in either status?
Thanks for the additional detail. My first though on how this could be achieved would be to create custom date or datetime field in the Accounts module. Once that field is created, you would then create separate processes to achieve the following use cases in SugarBPM:
If you have a lot of related modules or a lot of related records within certain modules, I recommend this solution over using Sugar Logic formulas. Sugar Logic can create performance bottlenecks if a large number of calculations have to be performed against related modules.
