Feature Request se case building for Salesforce - Enterprise-Approvals

@lalikuma ,

Looking at the Salesforce API documentation here, it appears this would be possible to do as an Event-triggered Path. My concern would be whether or not the bot could submit the approval on behalf of the approving user; if so, this is a very straight forward use case. 

If you cannot submit the approval on behalf of the approver, then you could configure the bot service account as an approver so that the bot can submit the approval, then add a comment to the approval with the name/email of the actual approver. The API above seems to facilitate adding a comment at the same time as submitting the approval, so this does not seem much harder than if you could submit the approval on behalf of the approver. It’s worth noting that the approver would show as the bot service account, while the comment added would show the actual approver.

Let me know if I can clarify any of the above, or if you have any follow-up questions!

Dray

@kyril.remillard - Is this supported within the Native configuration with Salesforce ??

Salesforce is not in our list of supported systems for native approvals (here). In short, the Salesforce auth requirements mean that any hypothetical feature built would have to work the same as I outlined above, so it will be better solved using Creator Studio (faster to build, easier to deploy, more custom, etc).