![]() ![]() So I went along with that approach (took me a few hours before I figured this out though).Īs you can see above, now there’s a placeholder called “Task ID” I could use to set the reminder. If the task ids match, the reminder will be set on that particular task. The only way to get around this, is by getting the the entire list of tasks and adding a condition that compares the task ids. It’s relatively easy to use the definition language and get the id from the response: You just need to know how □īut if you want to add this code (either between quotes or not) in the “Set a reminder” action, it will say you’ll have to enter a valid integer, otherwise it won’t work. You need this id to set the reminder on the task, but there is no placeholder in the Flow-designer, so I needed to use the Logic Apps definition language. The “Create a task” action returns an Id of the task that was created. I needed to add a condition that actually checks the Id received from the “Create a task” action to the list that resulted from the “Get tasks” action. My flow definition ended up looking like this:Īfter receiving the e-mail, a message is posted to Slack and a Task is created in Wunderlist, but I had some trouble adding a reminder to the task. Adds a reminder to the Wunderlist task, 4 hours after the e-mail was received.Sends a notification to my Slack channel.Triggers when a code review e-mail is received.To help myself with this process, I decided to design a flow that: My problem: I tend to forget this when I am a little backed up or have a lot of meetings during the day. We tend to get a lot of e-mails during the day, including Code Review e-mails when I need to review a colleague’s attempt to check-in some code. The task itself normally isn’t that time consuming, but you need to get to it as soon as possible of course. My first attempt: Code Review notifications It’s a very easy experience, but at the same time, it may be introducing a new kind of Access. ![]() Logic Apps are manageable and can go into source control, have version control etc. It won’t surprise anyone that the experience feels very much like Logic Apps, only it’s all a little bit simpler and it s part of your Office365 subscription, instead of Azure.įlows are not managed, there’s no source control. Microsoft Flow enables non-developers to build simple flows for themselves and enables them to automate certain tasks, also called IFTTT-flows. It is built on top of Logic Apps and it will even be possible to actually take the Flow and “demote” it into a Logic App. The flow triggers a rejection e-mail if someone is rejected, and triggers several e-mails when an applicant is accepted. By going through the applicants and simply replying “Accept” or “Reject” in Outlook, he automated the entire workflow, saving him a lot of time each morning. Instead of having to go through each application in his inbox and send a personalized reply, he setup a flow that actually did all the work for him. His talk was very inspiring and above all, it triggered me on actually using Microsoft Flow.Ĭharles triggered me with one simple example: his automation of reviewing job applications. I didn’t know exactly what I could get out of it and I didn’t really look into the product, until I saw Charles Lamanna’s talk at Integrate 2016. When Microsoft Flow was first announced I was not that impressed. ![]()
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |