Skip to content
tenantcraft
← The Studio
Power Apps · Insurance

HR staffing request

Hiring managers ask to fill or change a position here. A checklist comes first, then a stepped form. The approval scenario decides who has to sign off, and submitting starts the approvals flow. In the demo, press Fill sample data to jump to a finished Scenario C request.

  • ToolPower Apps canvas app, as a SharePoint list form
  • Usershiring managers, finance and talent acquisition
  • Hands off tothe staffing approvals flow
apps.powerapps.com/play/hr-staffing-request

A working replica of a real Power Apps build, redone in HTML and JavaScript so you can click through it here. Algonquin Mutual Insurance is fictional; all names, people and numbers are illustrative. Open it full screen.

Want help building yours? hello@tenantcraft.ca

01How it works

Every build here sticks to standard connectors like SharePoint, Outlook and Approvals, so it runs on the Microsoft 365 licences you already pay for.

01

A checklist before the form

A first screen lists what to sort out before asking to hire: the job description, budget, other options and candidates. The form only opens once the box is ticked.

How to build it

  1. Add a second screen in front of the form with the checklist and an I understand checkbox.
  2. Greet the person by name with User().FullName, and tell them the owner will see who submitted.
  3. Enable the Next button only while the checkbox is ticked.
02

One form, seven steps

The live app has 85 fields across seven steps in a side rail. The demo keeps the steps and about 25 of the fields.

How to build it

  1. Keep one SharePoint form and show each card only on its step, with Visible: varStep = n.
  2. Show cards that depend on an answer only when it applies, like Type of change for a repurposed position.
  3. List every required field per step in one table, so the step status, the Next button and the missing list all read the same rules.
03

The scenario picks the approvers

Choose A, B, C or D and the form asks only for the approvers that route needs. Scenario C also adds a Business case step.

How to build it

  1. Show each approver people-picker only for the scenarios that need it.
  2. For Scenario B, decide the last approver from the type of change: division, vice-president or CEO.
  3. On submit, check the right approvers are filled before calling the flow, and say exactly which one is missing.
04

Submit starts the flow

Submitting saves the item and calls the approvals flow with the route and the approvers’ emails.

How to build it

  1. Run SubmitForm, then call the flow from OnSuccess with LastSubmit.ID.
  2. Pass the scenario and each approver’s email from Office365Users, so the flow needs no lookups.
  3. See it from the other side in the staffing approvals flow.

02More builds

All builds →

(Your process)

Still running it on email?

Sneak peek

Document preview

100%

Loading the document…