Skip to content

Notes

Notes in Velosity serve as a critical communication and documentation tool across various stages of the manufacturing and sales lifecycle. They can be created manually by users to capture specific details or generated automatically by the system based on predefined rules.

Summary of Note Creation

Entity Created By Context / Trigger
Sales Quotes User Header or individual Line Items.
Sales Orders User Header or individual Line Items.
Production Orders User General notes on the production order.
Production Tasks User Added by shop-floor workers; recorded independently of production-duration capture.
Escalations User Communication threads to resolve production issues.
Customers User Notes regarding specific customer accounts.
People (Contacts) User Notes on individual customer or supplier contacts.
Sales Opportunities User Tracking progress and communication in the Sales Funnel.
Suppliers User Notes regarding vendors and procurement.
Products User Setup and configuration notes for items.
Maintenance User Documentation of maintenance activities or assets.
Inventory Locations User Notes regarding physical storage locations.
Quality (NCR, CAPA, 8D, etc.) User Documentation for Non-Conformance Reports, Corrective Actions, and Audits.
Smart Quote System Automatically added via rules using AddNote() (e.g., config.AddNote()).

User-Created Notes

Users can manually add notes to several key entities within Velosity to ensure clear communication between team members and departments.

Visibility

When creating a note, you can specify its visibility:

  • Internal: Visible only to Velosity users within your organization. Use this for internal coordination, manufacturing notes, or private observations.
  • External: Visible to both internal users and external parties (e.g., customers on a Sales Quote or a Velosity STORE order).

[!IMPORTANT] The "Both" visibility option has been removed. Notes are now explicitly either Internal or External.

Sales & Customers

  • Sales Quotes & Orders: Notes can be added to the header for general instructions or to specific line items for technical details.
  • Customers & People: Used to track relationship history and specific contact requirements.
  • Sales Funnel (Opportunities): Essential for documenting the sales process and next steps for potential deals.

Production & Shop Floor

  • Production Order Tasks: Shop floor workers (SHOP and TECH roles) can add notes directly to tasks. Notes do not affect production-duration capture.
  • Escalations: Handled as a threaded note system, allowing team members to collaborate on resolving production blockers.

Quality & Maintenance

  • Quality Documents: Notes are used in NCR (Non-Conformance Reports), CAPA (Corrective and Preventive Actions), 8D reports, and Audits to document findings and resolutions.
  • Maintenance: Used to record service history and notes on equipment or facilities.
  • Inventory: Notes can be added to Inventory Locations to provide specific handling or storage instructions.

Account / User Profile

  • Recent Notes Feed: Users can view a consolidated feed of recent notes across all entities (Sales Quotes, Sales Orders, etc.) that they have permission to see. This allows for a quick overview of recent activity and communication.

Automatically Created Notes (System)

Velosity automatically generates notes based on Smart Quote rules, ensuring that critical information is consistently captured without manual intervention.

Smart Quote Rules

During the configuration of a product in Smart Quote, notes can be automatically added to the Bill of Materials (BOM), SKU line items, or the configuration itself using the AddNote function in the "Then" block of a rule.

All notes added via Smart Quote rules default to Internal, so they do not appear on customer-facing quote output. Use the fluent visibility selector to make the intent explicit:

// Internal-only instruction for the quote creator; omitted from customer PDFs.
config.AddNote("Auto-added transceiver quantity explanation").Internal();

// Customer-facing note; may appear on the customer PDF.
config.AddNote("Customer-facing note").External();

// Internal-only instruction on a configured-item BOM line.
config.AddItem("ItemNumber", 1.0m).AddNote("Install after final inspection").Internal();

// Customer-facing note on a SKU line.
config.AddSku("WSE1082AB", 16.0m).AddNote("Lead time applies").External();
  • Configuration Notes: config.AddNote("Your note here"); adds an Internal note to the overall configuration. Append .Internal() or .External() to set visibility explicitly.
  • Item-Specific Notes: config.AddItem("ItemNumber", 1.0m).AddNote("Specific note for this item"); adds an Internal note specifically to the item being added to the BOM.
  • SKU Item Notes: config.AddSku("SkuNumber", 1.0m).AddNote("Specific note for this SKU"); adds an Internal note to the SKU line item.

Both item-specific and SKU item notes support .Internal() and .External(). Apply .External() only when the note should appear on customer-facing quote output.

These automated notes are essential for: * Communicating manufacturing requirements based on selected attributes (e.g., "Handle with care - fragile material selected"). * Documenting why certain items or tasks were added by the rules engine. * Providing clear instructions to the shop floor that are derived directly from the customer's requirements.