Can i ensure all Contacts under an Account automatically get assigned to the Account's Assigned To/User?

In current versions of SugarBPM, a Start Event can be set to react to a Relationship Change.

Then, a Change event can be configured to change the Assigned To field.

To achieve the goal of ensuring all Contacts were assigned to the Account owner when creating a new Contact, I

1. made a process definition targeting Accounts.
2. configured the Start Event to apply to Relationship Change and criteria for Contacts Added
3. added a 1-minute Wait Event (to ensure the new Contact's relationship was established before trying to change its field values)
4. added a Change Field action that set the Assigned To field in all related Contacts to Record Owner
5. added an End Event doing nothing.

With the BPM scheduler running, every Contact including the one I just created is assigned to the Account's owner during the next scheduler run.

Note: Without the Wait Event, all Contacts except the one just created are updated, but the new Contact is not updated.

One thing to note about this configuration is that SugarBPM will save all related contacts to the account regardless of whether the assigned user needs updated on each contact. While the account::contacts relationship is typically a relatively small number of records, this solution could cause performance issues for more robust relationships.

Another potential issue is that re-saving records may cause additional logic (e.g. Sugar Logic, SugarBPM, logic hooks, etc.) to trigger unexpectedly. 

If either of these are a concern, you should consider alternatives where only the child record being created/related to the parent record is updated rather than all records within the relationship.

One thing to note about this configuration is that SugarBPM will save all related contacts to the account regardless of whether the assigned user needs updated on each contact. While the account::contacts relationship is typically a relatively small number of records, this solution could cause performance issues for more robust relationships.

Another potential issue is that re-saving records may cause additional logic (e.g. Sugar Logic, SugarBPM, logic hooks, etc.) to trigger unexpectedly. 

If either of these are a concern, you should consider alternatives where only the child record being created/related to the parent record is updated rather than all records within the relationship.

Hey Chris Raffle,

I experienced this feature request in lots of projects. maybe it is time to create an enhacement request for a system setting that allows to set the assigned user accordingly to (specified per module) attached records :-)

Bests
Björn