Create a Task to Follow-up on a Call without losing the Call to Contact or Account connection

Hi Bud Hartley ,

There is no direct way to create sibling records in SugarBPM. The best way I can think to achieve this use case is to do the following:

1. Create fields on the account module for the fields from your Calls module that you want to carry over to the follow up task (e.g. Call Name, Task Due Date, Task Details)
2. Have a process configured so that when a call is completed, it updates those fields on the parent account
3. Have a second process on the accounts module that triggers when any one of those fields change, that it then creates a related task

Chris

Impressive workaround to get this done without code.

I personally have not tried BPM yet, but if things get so complicated, maybe, in cases like this one, a custom logic hook would be a bit cleaner without all the extra fields which, would all end up being just temporary and therefore empty columns in the table?

FrancescaS

I agree that a logic hook would be a cleaner approach if I were to solve this use case today. For customers who don't have developers on-hand or dedicated to the project, there is often a tradeoff of having a solution admins can directly maintain versus a developed solution that is more efficient but requires specialized resources. SugarBPM does a great job at satisfying the former and, with creativity, can accomplish a lot of solutions that would typically default to custom code.

The most important part of employing those 'creative' solutions is making sure the system is well-documented (e.g. using comment text on the fields in Studio, documenting changes at the process definition level and within the process canvas itself), so others (and sometimes the person who did it ) know what purposes those pointless-at-first-glance fields serve. 

Chris

I agree that a logic hook would be a cleaner approach if I were to solve this use case today. For customers who don't have developers on-hand or dedicated to the project, there is often a tradeoff of having a solution admins can directly maintain versus a developed solution that is more efficient but requires specialized resources. SugarBPM does a great job at satisfying the former and, with creativity, can accomplish a lot of solutions that would typically default to custom code.

The most important part of employing those 'creative' solutions is making sure the system is well-documented (e.g. using comment text on the fields in Studio, documenting changes at the process definition level and within the process canvas itself), so others (and sometimes the person who did it ) know what purposes those pointless-at-first-glance fields serve. 

Chris

Oh yes, the documentation is VERY important.  In addition to the Help and Comment Text for the fields I've been writing Comments in the Process and often Word Documents that document the document the thinking.  Thanks again Chris.  The Sales Manager is very happy with the result.