SDK Bulk api calls suppress email to initiator.

When performing job operations or bulk record updates via the SDK alowl the developer to either suppress the emails or decide if and who the notifications should be sent to.

I have an external app that writes to a Vault Object that has a trigger that performs the following:

1) update related object

2) change state of the record.

For this external app the end users receive notifications from vault either concerning a batch operation completed or a job operation has completed.

I have had to jump through hoops to suppress the job operation via a message queue - but should we really have to do this?





Please sign in to leave a comment.