Purchase Approval on Runtime Agent

Deploy template #74 Purchase Approval Workflow to a runtime agent so managers on the factory floor can approve purchase requests at /approvals without Studio login.

Why export purchase approval to an agent?

• Approvers work on-site without Studio licenses or VPN to cloud.
• Form submissions and approval DB stay local on the gateway PC.
• Same graph as cloud — only the decision UI moves to /approvals.

Step 1 — Load template #74

1. Studio → Templates → Purchase Approval.
2. Customize form fields and Request Manager Approval approver email.
3. Ensure Wait → Check → Switch branches match your procurement process.

Step 2 — Activate and export

1. Validate and Activate.
2. Export Runtime:
   • Target OS matching the on-site PC.
   • Operator approval support — enabled (approval nodes detected).
   • Dashboard port 9090.
3. Install the ZIP as a service — Export Runtime to Edge.

Step 3 — Submit a purchase request

1. Share the Form Input URL from the active workflow (or trigger via webhook).
2. Employee submits item, amount, and justification.
3. Run creates a business approval on the agent.

Step 4 — Manager decides on agent

1. Manager opens http://<agent-ip>:9090/approvals.
2. Enters their email (must match [email protected] or your configured approver).
3. Approves or rejects.
4. Workflow continues: procurement task on approve, log on reject.

Step 5 — Remote access token

If approving from a laptop on LAN (not localhost), use the export token once:

http://192.168.1.50:9090/?accessToken=<DashboardActionToken>

Token is in exported appsettings.json when Operator approval support was enabled.

Studio vs agent

	Studio	Runtime agent
Approval inbox	Jobs → Approvals	/approvals
Identity	Login + roles	Approver email/name match
Database	Studio approvals.db	Agent local DB

Related tutorials

• Approvals on Runtime Agent
• Request, Poll & Branch (#237)