Trigger Process on Changed Field?

I want to trigger a process based on a change of the Assigned To user. But Sugar does only allow me to check for a user's relationship within a given object. 

BUT I just want to see if the field has changed, not to whom it changed but only that it changed.

Later on, that new Assigned To shall do an approval. 

It seems Sugar is unable to allow this simple requirement, or am I just blind?

(using only Sugar 8.0.1 without any addons. Just the plain Process Definitions module)

  • Hi Kai Opitz,

    Per enhancement request # 79259 (you will need to be a support-authorized contact to view this link), it appears that this functionality is not yet available in SugarBPM (formerly Advanced Workflow). I recommend filing a support case pointing to this enhancement so that they can weigh the importance of implementing this feature.

    You have a few options to achieve this functionality in your current version of Sugar:

    1. For basic logic processing, you can create a workflow to trigger based off the Assigned User field changing. This functionality was Sugar's original workflow architecture so it is much more limited in the actions it can process based off a triggering event.
    2. For more complex processing, a custom logic hook can be developed. If you do not have immediate developer services, the company I represent, Upsert, can help you achieve your desired process flow.
  • Hi Kai Opitz,

    I haven't tried this myself, but I'm guessing that you can create a calculated field that's set equal to the Assigned-To user's name or id. Then you should be able to access this calculated field in SugarBPM process and trigger the process on a change in this field.

  • Is it possible to do this in Sell 13.1 BPM?

    Want to automatically create a task for the NEW Assigned To user when this field is changed to them in a Lead record.

    If not, any updates to a resolution?

  • Hi  ,

     This should be possible directly with the 'Relationship Change' start event, however bug # 87640 prevents processes from triggering when the assigned user is added or changed on a record. 

    We have worked around this defect with our clients by creating a custom field on the desired module. We make the field calculated with the following formula:

    Fullscreen
    1
    related($assigned_user_link,"user_name")
    XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX

    With that formula, the field will always have the user name of the current assigned user. Once that field is created, we then have the process definition start event set to trigger on when that custom field changes (i.e. when the assigned user is changed on the record, this field changes too). 

    I hope this helps!

    Chris

  • Worked perfectly!  Thank you Chris.

  • hi  

    Not sure about v13.1 but just checked and it is possible in v13.3

    .

    CRM Business Consultant