Skip to content

Case study · F&I

Power Apps Workflow for Environment Refresh Requests

A motor vehicle protection products provider had no clear way to track environment refresh requests across multiple teams. iBoss built a Power Apps, SharePoint, and Power Automate portal with request tracking, audit trails, role validation, reminders, and search.

Client
A motor vehicle protection products provider
Disclosure
Anonymised

Headline metrics

About 120 hours
Development effort
5000 requests
Power Apps limit addressed

Additional context

Replacing email-driven environment refresh tracking with a searchable, auditable workflow portal.

01 / Challenge

The problem in front of us.

The client received numerous environment refresh requests but lacked a defined tracking process. Multiple teams were involved, email trails circulated for single requests, simultaneous requests caused confusion, follow-ups were manual, and tasks sometimes stretched longer than normal because status visibility was poor.

02 / Approach

How we set the work up.

iBoss identified a portal-based workflow using Power Apps, SharePoint, and Power Automate. The design focused on fast request creation, status visibility, role-based validation, reminders, search, and auditability across devices.

03 / Solution

What we built.

The management portal lets users raise requests by choosing the environment and sub-environment while relevant data is captured automatically. Request tiles show Unique ID, Environment, Owner, Sub-Owner, Start Date, and Status. The portal includes search, email reminders near deadlines, role-based validation, and audit trails. iBoss also addressed the Power Apps limitation of processing only 5000 requests through code.

04 / Outcome

What it has held up to.

The team can now raise requests with a button click, access the application from mobile, desktop, laptop, web, and tablet, track request status without relying on email, review audit trails for each request, and run the formerly manual workflow with less time and effort. The development effort was about 120 hours.

Stack

What it runs on.

  • Power Apps
  • SharePoint
  • Power Automate

Tell us what you're trying to ship.

We'll start with a two-week diagnostic. No slides, no promises we can't keep.