The New Contract page (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.
/it/contracts/new) provides a form for creating a new vendor contract. It accepts an optional vendor_id query parameter to pre-select the associated vendor.
Overview
The page usesuseVendorContractMutations for creation and useVendors to populate the vendor selector. If the URL includes ?vendor_id=<id>, the vendor field is pre-selected. On success, a toast notification fires and the user is redirected to /it/contracts/:id for the newly created contract.
Form fields: vendor_id (required), contract_name, contract_number, contract_type, status, start_date, expiration_date (optional), renewal_date (optional), auto_renew (boolean), contract_value (optional), payment_terms (optional), contract_description (optional), document_url (optional).
Who it’s for
No explicit secondary permission gate beyond the outerITViewGuard (it.view). Creating contracts requires it.contracts.create.
Before you start
- The vendor must already exist in the system (
/it/vendors). - Have the contract details (name, type, start and expiry dates, and value) ready.
Steps
Open the new contract form
From the Contracts list or a Vendor detail page, click New Contract, or navigate to
/it/contracts/new. Append ?vendor_id=<id> to pre-select a vendor.Select a vendor
Choose the vendor from the dropdown. All active vendors in the organization are listed.
Fill in contract details
Complete the contract name, number, type, status, start date, and expiry date. Optionally provide contract value, payment terms, description, and a document URL.
Configure auto-renewal
Toggle Auto Renew if the contract renews automatically. Set the renewal date if applicable.
Related
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.
Documentation sources
Documentation sources
- src/routes/it.tsx
- src/cores/it/pages/vendors/NewContractPage.tsx
- src/cores/it/hooks/useVendorContractMutations.ts
- src/cores/it/hooks/useVendors.ts