We’ve had a large number of requests for this sort of functionality, but if you aren’t one of the customers making this request then you may not entirely understand what we are talking about here. What I mean by dynamic forms, is that the SR/IR/CR form changes the fields it shows and the ordering of the fields as you see fit based on the template id of the WorkItem. Let’t look at a few scenarios where this would be useful.
One common scenario is when you have a particular Request Offering in the Service Catalog that serves a very particular purpose, most commonly something like a project request or a new user access request. In either of these scenarios the general information you might be requesting from the user is not going to fit readily into the standard fields for the service request.
With this in mind you are left with a few options. You can extend the service request class to contain additional fields to hold this information and name each field according to the information it will contain, or you can extend the workitem with a generic set of fields to contain the information from both types of request (we consider this best practice), or you can try and fit the information into the default fields. For this article we are going to work with what we consider to be best practice.
Continue reading “Cireson Portal: Dynamic Forms by Template ID, Part 1”
I enjoy visualizing data. I believe it gives a different layer of insight to the data that we already have and bubbles up information we may have either felt like we knew already, or demonstrate to us something new entirely. It’s really a matter of bringing broad understanding to something that is otherwise foreign and nearly unusable.
For these exact reasons I’m really excited about the potential of Power BI and Power BI Desktop, but even more so the combination between the two.
Continue reading “Power BI Desktop + SCSM 2012”
If you’ve been following along with our series you now have a beautiful Power BI dashboard for your incidents that is using real data injected directly into Power BI from SCSM using Powershell and the Power BI API.
All that to say, we are missing one very important capability, and that’s how we update the data regularly without the SCSM admin having to log into the system in the middle of the night to refresh the data for the CIO currently in the UK. This is where Azure Automation comes in.
Continue reading “Automation Series 1, Part 4: Azure Automation”
In the third post of our automation series we will focus on report and dashboard creation from within the Power BI web app. The intent of our dashboard today will be to show only a few key metrics:
- Incident creation by date
- Count of Incidents by classification
- Count of Incidents by Status
Continue reading “Automation Series 1, Part 3: Power BI Reporting”
In the second part of our series we will be focusing on Power BI and how to access the API through Powershell, as well as the benefits of using the API. We will also discuss a few of the limitations that exist within the API currently that could limit what you want to do with the API.
This is part 2 in the series, if you are looking for the first post you can find it here:
Automation Series 1, Part 1: Service Manager Dashboards in Power BI through Azure Automation
Continue reading “Automation Series 1, Part 2: Powershell and Power BI”
This blog is the first in a series that I’ll be writing, starting today and continuing through the next few weeks, that will focus on how IT shops can easily automate the process of dashboard creation within Power BI and then present this information to their users in a very mobile friendly fashion through the Power BI app. Going a step further, we will use Microsoft’s Azure Automation in the cloud to run on-premise runbooks to collect the data from Service Manager and upload the data into Power BI using Powershell and the Power BI API.
Continue reading “Automation Series 1, Part 1: Service Manager Dashboards in Power BI through Azure Automation”