Approval email flow is not honored in logic apps - azure

It looks little weird. The approval email is however received.
My Logic App has a number of actions to collect & process the data from SharePoint Online. All actions with regards to the processing are working as expected. Even the Approval step is getting executed
However, the "Send Approval Email" action does not wait for a response.
Any help here would be appreciated.

The 3rd party mail filters (like G Suite and Mimecast) will autoselect the User options in 'Send email with options' action. For that reason, please set Show HTML confirmation dialog to Yes in order to avoid this problem related to the functionality.
Reference : https://learn.microsoft.com/en-us/connectors/office365/

Related

Customize Email body of send approval message in power automate

I have added action to send approval in power automate. But in email I can see created by name as who has last updated the flow. Is there any way we can remove created by or customize the approval email body or any other way I can handle this? I need only requested by name here(who has created a list item). Here is the image for reference,
Thank you !!
I believe that you found your solution. However, my take on your question is as the attached.
1.Ensure you select "Custom Responses-..." for your approval type.
2.Feel free to customized your own email body in the "details" section.
This is how you do it
The customized email
Hope this solution solves your issues.

How to disable workflow initiated email from SP workflow

I have a workflow in SharePoint 2013 that sends out emails to the user whenever their requests gets worked on. They however also get an email that says "A workflow has been initiated on the following list item".
Is there any way to disble that email from being generated or sent to the requestor?
Please advise, thank you.
With SharePoint Designer, you can change or simply remove the initial email send to the Author.
There are some workaround to do, since you'll have to copy the OOTB Workflow before editing him.

Sending Test Email in Workflow

I am editing a workflow (that I did not create) and inside the email that it sends, there is this link that I cannot click on. So I want to have the workflow send me the email so I can click on it through my email client to see where it leads to. Is it possible to send an email without having to run the workflow? There is an if statement that it has to go through in order to send the email and I don't want to go through the trouble to initiate it.
It's not possible to make a workflow generate an e-mail without running the workflow through the branch that creates the e-mail...
This is one reason why debugging workflows isn't very easy.

The e-mail message cannot be sent. Make sure the outgoing e-mail settings for the server are configured correctly Office 365

Here i developed one Info Path form and when user submits the form then approval process start in Office 365.
First approval goes to manager of the submitter and he got the email for that it will work fine.but recently one user got below log in workflow history.
"The e-mail message cannot be sent. Make sure the outgoing e-mail settings for the server are configured correctly."
i Google it and in many blogs and forums they have mentioned that it is permissions issue but i checked it also User has permissions because,After this record i enter another record and approved it with this user and got the email.
and it is also not SMTP issue because i developed and published Info Path form on Office 365
Now so much confused what to do.
Any help highly appreciated.
Thanks,
Manoj.
Problem: I had a workflow that was supposed to pause, and thereafter send an email reminder. Results: nothing. Tried: everything. Got the same error every time: The e-mail message cannot be sent. Make sure the outgoing e-mail setting for the server are configured correctly.
Clues: SP was sending other emails, so I knew the email config was probably OK.
Tests: I moved the Pause Step after the email Step, and POW! it worked immedioately. So, there problem seems related to the Pause Step.
SOLUTION: Following the idea of Johan_0904, I returned the Pause Step to the front; and on the Send Email Step, I clicked "Add Else Conditional Branch". I never used the "Add Else Conditional Branch". But I did add the condition: "%Complete" "Greater Than" "-1". This condition is always TRUE. And the "Send Email" command worked thereafter. QED.

Approve/Reject in email generated by SharePoint

When I make a meeting in Outlook, the recipient gets a approve/reject button in the top of the email. I'd like to do a similar thing with SharePoint: when a task is created, an email is sent to the person the task is assigned to, and the email asks the recipient to either accept or reject the task. I've seen demos of people doing this with a custom ASPx page, but I'd like to make it directly in the email. How should I go about doing that?
I'm used to making workflows in Visual Studio, so I'm happy with code examples for setting up an email and/or parsing the response
Cheers
Nik
The approve/reject buttons in Outlook shows up because the email is in the iCalendar format. I dont know if this is the best way, but you can send out your own iCalendar emails using C# code and set the response email to a mail server you control. From that mail server you can process the email and use the SharePoint WebService API to approve the item in SharePoint.
I like JMD's suggestion but I don't know how you'd interact with SharePoint from the mail server.
It might be a easier to send an HTML-formatted email with two links (...) for the Accept and Reject buttons. You could use CSS to format them so that they look like real buttons.
You could then create an ASPX page (or better an IHttpHandler implementation) to perform an action based on parameters passed to it via a URL. You'd want to pass in the site, web and list details and the list item ID along with a value to indicate whether the item is approved or rejected.
Then set the URLs of your "buttons" in the email to call your handler and pass in the appropriate parameter values.
The downside to this is that the "buttons" would be part of the message body and not part of the Outlook chrome but, on the other hand, they would be usable from any email client.

Resources