Extending Skybow Solutions with MS PowerApps

Currently, I am developing a simple ticket system with the Skybow Solution Builder in Office 365 after work. With Skybow (almost) everything can be implemented as a low-code solution. But then I wanted to generate an overview of all tickets and their status.

I wanted to visualize this – analogous to Microsoft Planner – as a pie chart or donut. How many tickets are open? How many are closed or have a different status? I wanted to present this information to the user at first glance. In addition, the user should be able to quickly and easily customize the diagram according to his or her own wishes. This requirement also had to be implemented as a no-code or low-code solution.

At this point, I did not get on with development at first, as a JavaScript framework seemed to be the only solution. ChartJs (https://www.chartsJS.org) would surely be the tool of choice, though:

  1. After the tiring last couple weeks, I did not feel like a lot of coding after work.
  2. Low-code customizing was no option.
  3. PowerApps have a sort of control that can do the same.

But wait a minute: Can that be done with PowerApps, too?

Yes, sure 😊.

2018-07-01_13-48-29

(English screenshots will come later. Hope you can do without for the time being. „Kreisdiagramm“ is a pie  chart, for example…)

Pie charts should work. 😊 But can I integrate PowerApps into Skybow Solutions? Yes, of course:

  1. PowerApps have a web adress.
  2. SharePoint offers a page viewer WebPart.
  3. Skybow uses SharePoint.
  4. And I really did not want to spend more than five minutes for this issue 😉

This is how it works:

First, we create an app at https://PowerApps.microsoft.com. To make everything easy to read and to fit into the Solution layout, I opted for custom size settings: 400×200 should be fine:

2018-07-01_13-53-40

Now, I paste the pie chart in the empty Screen1:

2018-07-01_13-55-48

Once the size is customized, the result looks like that:

2018-07-01_14-05-06

Getting data on the ticket status by low-code

And now for the data I want to display: I need an overview according to the ticket status. For this purpose, I need to know how many tickets are open, on hold or closed.

To achieve this, I create a collection in the OnVisible event that I want to link to the chart:

2018-07-01_14-08-46

The code again:

2018-07-01_14-09-53

In that way, I get a collection of the numbers of tickets according to their status. And I link this collection to the chart:

2018-07-01_14-35-11

As a result, the chart displays all values:

2018-07-01_14-13-07

Now I save and publish everything, so that the chart can be integrated into the Skybow Solution. For this purpose, we need the web address of the PowerApp. This can be found in the details when sharing the app:

2018-07-01_14-19-08

2018-07-01_14-15-53

This link must be pasted in the URL field of the settings for the page viewer WebPart. But before, the WebPart needs to be pasted at the desired postiion on the page:

2018-07-01_14-26-46

Afterwards, open the WebPart properties and enter the WebLink of the App:

2018-07-01_14-29-06

Now, the Skybow Solution is married to the PowerApp, and the desired statistics are displayed:

2018-07-01_14-33-14

Other features that would be nice to have

Useful extensions for this solution would be:

  1. Always up-to-date usin the TimerComponent:
    Normally, several users are  working with a ticket system. To make sure every user sees the latest status of all tickets in his or her overview, integrating the PowerApps TimerComponent is the way to go. In that way, the chart could be updated every five minutes for example.

 

  1. Which chart do you want to see?
    Offering a selection of charts would be useful for the user. This could be implemented by re-setting the items property of the chart after every selection in a drop-down or tile menu.

 

  1. The whole picture at a glance: statisticsn, burn-down charts & Co.
    Darüber Moreover, in many cases the user is looking for information about the overall status of a field of work, about particular projects and team, or cross-area analyses for the leadership. For example:

 

  1. How many tickets are processed per day or week?
  2. How many tickets are closed per day or week?
  3. How many new tickets were created in a particular period?
  4. How long does it take before a ticket gets a new status?
  5. How do all these values develop during the year?

I will deliver answers in the upcoming articles.

Do you have any comments or questions? Feel free to contact me via Twitter @papariedel.

Happy low-coding 😊

P.S.: Of course, these requirements can be fulfilled in SharePoint in other ways, too. But Skybow is my favourite Framework.