PA: Notification email sends old info

Hi KGM,

Thank you for showing the Process and where the record is reassigned in the process. That is helpful.

In the screenshot, the action you have circled appears (assuming from labels) to reassign the Campaign record to the current owner of the Campaign record. This sounds like it makes no change at all, based on the description of 'current owner in SugarCRM's documentation:

"Record Owner : The Record Owner is the user who is in the Assigned To field of the targeted Sugar record."

Double check to be 100% sure the circled action is the action that is triggering the notification email.

If it is the action sending out the assignment notification, can you offer a brief explanation as to what it is doing that causes this to change the Assigned To from one value to another? Thanks!

Thanks for your answer Patrick.

If we take the "rejection route", the thought behind this is to get the approver´s "fingerprint" onto the records. That is why the first update is to change the status (which is also needed since the record was rejected). Next update is to document in the record who rejected it (I do that by updating the "Description" field with so we´ll know later who rejected:

The last update (Assign to record owner) is only to trigger the email notification so the record owner (one who created the record) knows his/her record was rejected. I was planning to use the built in email notification (the "assign" notification, you know each time a record is assigned, Sugar sends an email notification to the new assignee), and that works except the notification email contains old data. It does not contain the new, updated status (even though the record has the new "Rejected" status, etc).

So the issue is not who gets assigned but the content in the notifcation email. But maybe I am using this wrong (even though I manage to trigger the notifcation email)...

Does that make sense?

Yes, I am trying to label the updates/actions with what happens to be transparent.

Thanks

KGM

Thanks for your answer Patrick.

If we take the "rejection route", the thought behind this is to get the approver´s "fingerprint" onto the records. That is why the first update is to change the status (which is also needed since the record was rejected). Next update is to document in the record who rejected it (I do that by updating the "Description" field with so we´ll know later who rejected:

The last update (Assign to record owner) is only to trigger the email notification so the record owner (one who created the record) knows his/her record was rejected. I was planning to use the built in email notification (the "assign" notification, you know each time a record is assigned, Sugar sends an email notification to the new assignee), and that works except the notification email contains old data. It does not contain the new, updated status (even though the record has the new "Rejected" status, etc).

So the issue is not who gets assigned but the content in the notifcation email. But maybe I am using this wrong (even though I manage to trigger the notifcation email)...

Does that make sense?

Yes, I am trying to label the updates/actions with what happens to be transparent.

Thanks

KGM

Hi KGM,

I might be doing something wrong, but in an instance where I the assignment notifications are working for manual changes, I can't get the process to trigger a notification when I reassign a Campaign record, so I am unable at this time to test or confirm what you describe.

Is there is a use case for not creating a Process Email Template and sending that to the Campaign owner with the field info you wish to share?