Skip to main content

Documentation Index

Fetch the complete documentation index at: https://docs.encoreos.io/llms.txt

Use this file to discover all available pages before exploring further.

This page displays the detail view for a single IT purchase request. Navigate to it at /it/procurement/:id.

​
Overview

The Request Details page shows the request number, title, approval status badge, request type, priority, quantity, needed-by date, vendor, pricing (unit cost and total cost), budget code, delivery location, business justification, and approval history timestamps. Draft requests show Edit, Submit for Approval, and Delete actions. Non-draft requests are read-only.

​
Who it’s for

This route requires IT_PERMISSIONS.VIEW (it.view) via the module-level ITViewGuard. The list page also requires it.procurement.view; the detail page has no additional per-route permission beyond the module guard.

​
Before you start

  • The purchase request must already exist. Create one via the New Request wizard.

​
Steps

  1. Navigate to IT > Purchase Requests and click a request row, or navigate directly to /it/procurement/:id.
  2. Review Request Details: type, priority, quantity, needed-by date.
  3. Review Vendor & Pricing: vendor name, unit cost, and calculated total cost.
  4. Review Budget & Justification: budget code, delivery site, and business justification.
  5. Review Approval History: creation, submission, and approval timestamps.
  6. If the request is in Draft status:
    • Click Edit to modify it.
    • Click Submit for Approval to advance it through the approval workflow.
    • Click the delete icon to remove the request (with confirmation dialog).

​
Key concepts

  • approval_status — lifecycle values: draft, submitted, pending_approval, approved, rejected.
  • request_type — hardware | software | service | other.
  • priority — low | normal | high | urgent.
  • total_cost — computed as quantity * unit_cost.
  • rejection_reason — displayed when a request is rejected.

IT Service Management

IT Service Management overview.

Governance & parity

This page documents shipped product behavior. It is not medical, legal, or billing advice. Verify against your organization’s policies and applicable regulations before using it for clinical, compliance, or billing decisions. Protected health information (PHI) shown in the product is governed by your tenant’s access controls and is never exposed in this documentation.
  • src/routes/it.tsx
  • src/cores/it/pages/procurement/PurchaseRequestDetailPage.tsx
  • src/cores/it/hooks/usePurchaseRequest.ts
  • src/cores/it/hooks/usePurchaseRequestMutations.ts