Full AppULTRA2 screens, copy-paste YAML for Power Apps Studio

Helpdesk App for Power Apps

A ticket inbox and an SLA dashboard, the two screens every internal helpdesk needs. Scroll to see why each part of the screens is there, then copy the YAML at the end.

Screen 1 of 2

The support overview

The screen a support lead keeps open: is the team keeping up, and what needs attention right now.

Step 1 of 5

A KPI band answers "are we okay?"

Helpdesks are judged on a handful of numbers: SLA compliance, first response, resolution time, satisfaction. Each tile is a plain container with a label, a value and a bar, so changing what they show, or how many there are, is a copy-paste, not a rebuild. The demo values are placeholders for your own.

Step 2 of 5

The "SLA at risk" list says what to do next

A dashboard should not just report, it should point. This list surfaces the tickets closest to breaching, with countdown chips doing the prioritizing. The rows come from a small table; point them at your tickets source and the screen starts working for you.

Step 3 of 5

Distribution bars give context

Open by priority and by channel show where the load is coming from. Each bar is two rectangles: a track, and a fill whose width is a percentage. That is the simplest chart Power Apps can draw, and for a dashboard it is usually the only one you need.

Step 4 of 5

Dark mode is part of the template

This is the first PowerLibs full app whose generated YAML ships a real dark palette. Set the preview to dark before copying and the code you get uses the dark colors.

Step 5 of 5

One setting, two characters

The same screen with the style setting switched to Neutral: monochrome instead of semantic colors. Both looks come from the same generator, so the choice is one dropdown, not a redesign.

ServiceDesk · Support OverviewLive preview
AK
ServiceDesk · Support Overview
Today, live across all queues
SLA Compliance
94%
47 of 50 within SLA
First Response
28m
Target: 1h
Avg Resolution
3.1h
Target: 8h
CSAT
4.6
312 ratings
SLA at risk2 breaching soon
P1Email server rejecting external mailMarcus Schmidt · AK32m left
P1Payroll export fails with error 500Jana Weber · -54m left
P2VPN disconnects every 30 minutesTom Becker · LB2.1h left
P2Meeting room panel frozenKlaus Müller · TW3.8h left
Open by priority
P1 Critical
4
P2 High
9
P3 Normal
11
Tickets by channel
Email
46%
Portal
32%
Phone
14%
Chat
8%
Agents
AKAnna K.6 open
LBLars B.5 open
TWThomas W.4 open
JSJulia S.0 open

Screen 2 of 2

The ticket inbox

One screen for the whole workflow: pick a view, scan the list, work the ticket. The pattern Zendesk and Freshdesk use.

Step 1 of 5

Views replace folders

Agents do not browse tickets, they work a queue: All Open, My Tickets, Unassigned, Resolved. Each view is one Filter over the ticket collection, and the counts next to them are live CountRows. Adding a view means adding one row to a small table and one line to a Switch.

Step 2 of 5

The list shows only what triage needs

Priority, subject, requester, status pill and the SLA clock, nothing else. Every row is a single gallery template: add or remove a field once and every row follows. That is the point of building lists as galleries instead of hand-drawn rows.

Step 3 of 5

The detail pane keeps you in flow

Selecting a row sets one variable, and everything in this pane reads from it: properties, description, actions. Start work and Resolve run a Patch on the collection, so the list, the counts and the pane all update together. Try it in the preview.

Step 4 of 5

Dark mode is part of the template

The inbox ships the same dark palette as the overview screen. Set the preview to dark before copying and the generated YAML follows.

Step 5 of 5

The primary color setting

The primary color is a setting. Change it once and the generated YAML uses it everywhere: the rail logo, the active view, the buttons. This is the same screen with a different primary color.

ServiceDesk · Ticket InboxLive preview
AK
ServiceDesk
Ticket Inbox
VIEWS
QUEUES
IT Support12
Facilities5
HR3
All Open5 tickets
Search
NewP1#101
Email server rejecting external mail
RequesterMarcus Schmidt
CategorySoftware
AssigneeUnassigned
SLA32m left
DESCRIPTION

Bounces started this morning, NDR 550 5.7.1...

Reply to Marcus...

Try the inbox

This preview is interactive. Switch views on the left, select tickets in the list, and use Start work and Resolve in the detail pane. The pasted screen behaves the same way in Studio, because the YAML contains the same logic.

ServiceDesk · Ticket Inbox, interactiveLive preview
AK
ServiceDesk
Ticket Inbox
VIEWS
QUEUES
IT Support12
Facilities5
HR3
All Open5 tickets
Search
NewP1#101
Email server rejecting external mail
RequesterMarcus Schmidt
CategorySoftware
AssigneeUnassigned
SLA32m left
DESCRIPTION

Bounces started this morning, NDR 550 5.7.1...

Reply to Marcus...

Work with the screens

Pick a screen and copy its YAML. In Power Apps Studio, right-click the Screens node in the tree view and paste. Both screens paste into one app without name collisions.

Set up in 4 steps

  1. 1.Set the app layout to Responsive

    In Power Apps Studio open Settings, then Display, and set App layout to Responsive. With the Fixed layout the app shrinks on a phone instead of reflowing.

  2. 2.Copy the Support Overview

    Pick a screen in the tabs below and press Copy YAML. Start with the Support Overview.

  3. 3.Paste on the Screens node

    In the Tree view, right-click the word Screens itself and choose Paste, or press Ctrl + V. Not inside an existing screen: that keeps the controls but drops the screen's OnVisible.

  4. 4.Repeat for the other 1 screen, then wire the sidebar

    Paste each screen the same way. Then set the screen field of each sidebar item to the screen it should open. The Instructions tab shows the exact lines.

2 screens, each one is pasted on its own

Helpdesk App: Support Overview

ULTRANEW
Helpdesk App for Power Apps | PowerLibs | PowerLibs