| Q-Card | Short for Question Card, this is the generic term for any customizable input field used to gather data from the Requester, Approver, or Vendor within a schema. | section |
| Conditional Logic | A rule applied to Q-Cards or approval steps causing them to appear or be assigned only if specific conditions are met, which can be based on previous answers, attributes, or the status of the Vendor/Product. | section |
| Approval Flow | The configured, multi-step sequence of reviews and sign-off tasks a request must complete before finalization. | section |
| Editor | The primary configuration menu where Admins design and build Request Types (Schemas), define Q-Cards, and set up complex Approval Workflows and Automations. | section |
| Duplication Prevention | A feature that automatically surfaces alternative solutions (which may be marked as Purchased, Requested, or Not Purchased) during a software request submission to guide users toward existing tools and reduce waste. | section |
| Computed Attribute | An attribute where the numeric value is automatically calculated based on a formula applied to other attributes (e.g., calculating Annualized Contract Value or Weighted Vendor Score). | section |
| Vendor Selector | A specific Q-Card type placed in the Requester tab that allows the requester to select the relevant vendor. This is required for the “Send Vendor Questionnaire” step to successfully execute. | section |
| App Selector | A specific Q-Card that allows Requesters to choose a product from the catalog. In Software Schemas, it automatically displays alternatives and powers the duplication prevention feature. | section |
| Mark as Purchased Step | A critical system step is placed in the Approval Flow that finalizes a procurement action by updating the product status to “Purchased” and rolling up the spend value into the Total Approved Spend metrics for analytics. | section |
| Notify User Task | A lightweight task added to an approval flow that sends an automated message to internal or external recipients (e.g., billing@acme.com) without requiring an approval step. The task auto-completes and is tracked in the activity log. | section |
| Send Vendor Questionnaire Step | An automated task in the Approval Flow that sends questions from the Vendor Tab directly to the vendor’s contact email. | section |
| Create Request Step (Nested Flow) | An automated task that starts a new Opstream request (child flow) from within an existing (parent) flow, allowing Admins to componentize schemas and ensure dependent processes run in sequence. | section |
| Custom Statuses | Custom labels (e.g., “Awaiting Legal,” “Pending Vendor Info,” “Conditionally Approved”) created by Admins to improve granular visibility into where requests stand in the lifecycle. Custom statuses are globally applied to all requests. | section |
| Target Time (SLA) | A configurable setting in an Approval Task Card that represents the Service Level Agreement (SLA) for that specific review step, measured in calendar days. Performance against this target can be monitored in Analytics. | section |
| Events | A module that provides a calendar or table view of important dates driven by date-based attributes (e.g., contract renewal dates, SOC-II expiry dates) to ensure proactive management. | section |
| Webhook Step | A task that allows workflows to send real-time data from Opstream to external systems via a one-way webhook trigger (often categorized under Integration Steps). | section |
| Automated Data Model (AI-Suggested Attributes) | A feature that uses AI to scan data in connected systems (like NetSuite) and automatically recommend a unified, best-practice attribute model for Admins to review and adopt, accelerating configuration. | section |
| AI Extraction (Add-On) | A premium feature that automatically extracts key contract terms (e.g., renewal dates, liability caps, governing law) from uploaded documents, eliminating manual data entry for Legal. Extracted data must be manually Validated by an Admin. | section |
| Budget Intelligence (Add-On) | A premium feature that enables Finance and Procurement teams to define, track, and control budgets by automatically tying requests and spend data to specific budget lines, providing real-time visibility into the pipeline-adjusted balance. | section |
| AI Agentic Analytics (Add-On) | A premium feature that allows users to interact with data conversationally using natural language questions to instantly generate visualizations, charts, and reports, analyzing all Opstream data, including custom attributes. | section |
