Hi Partner Support,
In Enterprise Winter '19 (8.3.0), I just performed the following and it worked as expected to assign the record to a group user:
1. Create a group user named 'Groupie'
2. Create a Process Definition targeting Accounts:
Start Event: applies to all updates, no criteria
Action: Change Field -> Assigned to: Groupie
End Event: do nothing
3. Edit and save an Account record.
Result: The Account was reassigned to the group user, Groupie, as expected.
I hope this helps!
Hi Vincent Amari,
Assign User in SugarBPM is a feature designed to reassign the process itself, not the target record. Due to how often this confused users, Sugar added the functionality to have it also reassign the target record as well as the process.
The intended way to change the target record's owner is to change the field value as I described above.
Given this, it is possibly the attempt to assign the process to a group user that results in the failure, as group users cannot take action in the instance, and the process needs to take action as a viable user.