The Provance Blog will provide you with expert advice, insights and opinions in regard to IT Service Management, Microsoft, Microsoft Dynamics 365 and Microsoft System Center.
Flow is a tool by Microsoft that lets you automate workflows, synchronize files, collect data and get notifications between various Microsoft and non-Microsoft services.
Some examples of what you can do with Microsoft Flow:
With Microsoft Flow you can start from scratch or choose from a number of predefined templates as shown below
And in the screenshot below, you can see a simple scenario in which if a new record is created in SharePoint, a corresponding record is created in Microsoft Dynamics 365.
How to Build a Workflow Using Microsoft Flow and Provance ITSM
In this section, I will show you how to create a flow from scratch. In my view, Microsoft Flow is not intended for the novice user of Dynamics 365 or Provance ITSM, however, you also don’t need to be an expert in System Administrator knowledge or a developer to increase your productivity. It’s really for the Power Users, people that perform repetitive tasks and can analyze to see if there is a need for a workflow or various Dynamic 365 changes. Flow gives them the ability to automate a lot of their daily tasks. In the following scenario, I work for a Managed Service Provider and am using Provance ITSM to manage the services we provide to our customers. I’ll play the role of the Power User. My manager asks me that from now on, when we have a new release, we need to let our entire organization know a new version of our service will be released.
Before Flow, I would need to create the release record in Provance ITSM. Then, I would have to compose an email that details everything in the release. .
Using Flow, I can now just create a flow to do this. Here’s how:
Step 1: Log into https://flow.microsoft.com
Step 2: Select my flows. This screen will show all the flows I have previously created (and I can see if they are successful or if there are any failures). But, since I want to create a new flow, I am going to select Create from Blank so I can work some magic with this requirement.
Step 3: Specify a Trigger. This can be from a number of Office 365 and non-Office 365 services. For this use case, we want to review when a record is created from our Dynamics 365 instance.
Step 4: Select the Org and Entity we want to monitor. For this instance, our requirement is "When a Release is Updated”. So we will select the Release entity for the trigger when a release record is updated.
Step 5: We need to add a new step and we have the following to choose from:
Step 6: For this use case, we will choose "Add an Action" to modernize our communication to our organization. Instead of an email, we will create a Yammer post, but only when the status = Deployed.
Side note: If you’re not using Yammer you are missing out! Think of it has having your own company dedicated Facebook.
If the value is true, we want to post the message to Yammer. We can add dynamic content directly from the previous step. Now that we have it created let’s give it a name and take it for a run.
Step 7: Testing. We will test by creating a release in Provance ITSM as shown below
Now we can check yammer to see if the message was posted to the all company
Want more info? Read our series on how to take advantage of the Provance ITSM and Office 365 integration.
Watch our latest webinar on how to evolve from traditional ITSM to Modern Service Management.
Download ITSM Tools - an indepenent industry analyst firm - conducts a review of Provance ITSM.