Reference
Keyboard shortcuts, data formats, troubleshooting tips, and frequently asked questions.
Keyboard Shortcuts
GlyphFex supports keyboard shortcuts throughout the application. Press Ctrl+/ at any time to open the Keyboard Shortcuts dialog.
Navigation
Project
Entry Form
Dashboard
Export & Import
Command Palette
The Command Palette is the fastest way to access any function in GlyphFex. Press Ctrl+K to open it from anywhere in the application.
Start typing to search across all available commands. Results are organized into categories:
- Navigation — Go to any page (Dashboard, Analytics, Calendar, etc.)
- Action — Common actions (New Entry, Refresh, Export, Print)
- Entry — Recent entries section showing the 5 most recently modified entries, searchable by Reference ID or description
- Configuration — Open any settings dialog (Categories, Pipeline, Fields, Validation, etc.)
- Help — Open guides, Product Tour, Feature Overview
Press Enter to select the highlighted result, or Escape to close the palette.
Data File Format
GlyphFex stores all project data in a single .glyphfex file, which is a standard SQLite database. This design has several advantages:
- Portable — Move, copy, or email the file to transfer an entire project
- Easy backup — Just copy the file. No database export/import needed.
- No server required — Works completely offline for Personal (Solo) projects
- Inspectable — Open with any SQLite browser (like DB Browser for SQLite) to query data directly
Attachments
File attachments (drawings, photos, documents) are stored in a folder named {ProjectName}_Attachments/ located next to the .glyphfex file. When backing up or moving a project, copy both the .glyphfex file and the attachments folder.
Auto-backups
GlyphFex automatically creates backup copies of your project file each time you open it. Backups use a rotating scheme:
ProjectName.glyphfex.bak— Most recent backupProjectName.glyphfex.bak.1— Previous backupProjectName.glyphfex.bak.2— Oldest backup
.glyphfex-server file only contains the connection string — no actual data.
Troubleshooting
Common issues and how to resolve them:
"Cannot open project"
- Check that the file is not locked by another GlyphFex instance. Close other instances and try again.
- Look for a
.lockfile next to the project file. If GlyphFex crashed, a stale lock file may remain — delete it and retry. - Verify the file is a valid
.glyphfexfile and has not been corrupted. Try opening one of the.bakbackups.
"Connection failed" (SQL Server)
- Verify TCP/IP is enabled in SQL Server Configuration Manager
- Check that the Windows Firewall allows the SQL Server port (default: 1433)
- Confirm the correct machine name and instance name (e.g.,
SERVERNAME\SQLEXPRESS) - Ensure the SQL Server service is running on the host machine
- If using a dynamic port, make sure the SQL Server Browser service is running
"Entries not refreshing" (team mode)
- Verify the SQL Server connection is still active (try File > Open on the same project)
- Check that auto-refresh has not been interrupted — press F5 to force a manual refresh
- If the server was restarted, all clients may need to close and reopen the project file
"Save failed"
- Check that all required fields are filled in (look for red asterisks on the form)
- Verify the Reference ID matches the configured validation pattern (check for a red border)
- Ensure the Reference ID is not a duplicate of an existing entry
- Check that all required categories (from conditional rules) have a tag selected
"Concurrent edit conflict"
- Another user modified the same entry while you were editing it
- Choose Reload to see the latest version, Force Save to overwrite, or Cancel to go back
- See Concurrency Handling for details
Crash recovery
- Check the crash log at
%APPDATA%\GlyphFex\crash.logfor error details - The crash log records unhandled exceptions, first-chance exceptions, and task failures with timestamps and stack traces
- If GlyphFex crashes on startup, try opening a different project or creating a new one to isolate the issue
crash.log and include it when contacting support@glyphfex.com. This helps diagnose problems quickly.
Frequently Asked Questions
Can I use GlyphFex offline?
Yes. Personal (Solo) projects are fully offline SQLite files. No internet connection or server is needed. You can work on a laptop in the shop, on the road, or anywhere. Multi-user (team) projects require a LAN connection to the SQL Server host, but do not require internet access.
How many entries can I create?
In Trial mode, you can create up to 50 entries per project. With a licensed edition, there is no entry limit. The SQLite backend handles thousands of entries efficiently, and the SQL Server backend scales even further.
Can I migrate from Solo to Team later?
Yes. Go to File > Migrate to SQL Server at any time. The migration wizard copies all entries, configuration, and audit history to the new SQL Server database. Your original .glyphfex file is preserved as a backup. See Migrating from Solo for step-by-step instructions.
What happens to my data if my trial limit is reached?
Nothing is lost. All existing data remains fully accessible. You can view, edit, export, and move existing entries through the pipeline. You can also access all reports, analytics, and views. The only restriction is that you cannot create new entries beyond 50 until you enter a license key.
How do I back up my data?
For Personal projects, copy the .glyphfex file and its _Attachments folder to a safe location. GlyphFex also creates automatic backups each time you open a project, using a rotating .bak / .bak.1 / .bak.2 scheme. For Team projects, use standard SQL Server backup procedures.
Can multiple people edit the same entry?
GlyphFex uses optimistic locking to prevent data loss. If two users edit the same entry simultaneously, the second person to save will see a conflict dialog with options to Reload, Force Save, or Cancel. This ensures no one accidentally overwrites another person's work. See Concurrency Handling for details.
What are stale entries?
Stale entries are entries that have been stuck in the same pipeline stage longer than the configured threshold. They display a warning badge on the Dashboard and Calendar. You configure the stale threshold per stage in the Pipeline editor — for example, "stale after 14 days in Fabrication." This helps surface jobs that may have been forgotten or are blocked.
What is ISO Compliance Mode?
ISO Compliance Mode is a master toggle in the Audit & Compliance panel that enables all regulatory compliance features at once: full audit trail, mandatory change reasons on every edit, and hard delete disabled. This provides the change tracking rigor required by ISO 9001, AS9100, IATF 16949, and similar quality management standards.
How do QR codes work?
Each entry has a unique QR code that encodes a glyphfex://entry/{id} URI. Print Job Traveler PDFs with the QR code and attach them to physical jobs. When scanned with any barcode scanner connected to a PC running GlyphFex, the entry opens instantly. This is especially useful on the Shop Floor kiosk for quickly clocking in/out of jobs.
Can I customize the pipeline?
Yes — the pipeline is fully configurable. You can create any number of stages, set SLA targets (in calendar or business days), mark stages as completed, configure stale detection thresholds, designate quoting stages, and even create multiple pipelines within a single project. Stages can be reordered, renamed, color-coded, and deleted at any time.
Glossary
| Term | Definition |
|---|---|
| Entry | A single job, order, quote, or work item tracked in GlyphFex. Each entry has a unique Reference ID, tags, fields, attachments, and a full audit history. |
| Pipeline | A sequence of stages that an entry moves through, representing your shop's workflow from start to completion (e.g., Quote → Engineering → Fabrication → Shipping). |
| Stage | A single step within a pipeline. Each stage can have an SLA target, stale detection threshold, and business-day settings. |
| Tag | A label applied to an entry within a category. Tags help classify and filter entries (e.g., Material: Stainless Steel, Priority: Rush). |
| Category | A named group of related tags. Categories organize your tagging system (e.g., "Material" is a category; "Mild Steel" and "Aluminum" are tags within it). |
| SLA | Service Level Agreement. In GlyphFex, the target number of days an entry should spend in a particular pipeline stage before moving forward. |
| NCR | Non-Conformance Report. A quality record attached to an entry documenting defects, disposition, corrective actions, and resolution status. |
| Audit Trail | A chronological record of every change made to an entry, including who made the change, when, what fields were modified, and (optionally) why. |
| Built-in Field | One of 14 pre-defined data fields (Customer Name, PO Number, Due Date, etc.) that can be enabled or disabled per project. |
| Custom Field | A user-defined data field with one of 5 types (Text, Large Text, Dropdown, Date, Number). Custom fields extend the entry form with shop-specific data points. |
| Template | A saved configuration that pre-fills new entries with default tags, field values, and pipeline settings for common job types. |
| Ref ID | Reference ID — the unique identifier for an entry (e.g., Q-2026-001, WO-4521). Can be validated against a regex pattern for consistent formatting. |
| Revision | A version counter on an entry that tracks how many times it has been modified. Used for optimistic locking in multi-user environments. |
| Archive | A holding area for completed entries that are no longer active but should be preserved. Archived entries can be restored at any time. |
| Recycle Bin | A holding area for soft-deleted entries. Items in the Recycle Bin can be restored or permanently deleted (if hard delete is allowed). |
| Kiosk Mode | The Shop Floor view optimized for touchscreen or large-button operation, designed for shop floor operators who need to clock in/out and advance entries quickly. |
| Gantt Chart | A visual timeline on the Calendar page showing each entry as a horizontal bar spanning its active duration, with color-coded pipeline stages. |
| Optimistic Locking | A concurrency strategy where GlyphFex checks if an entry's revision number has changed before saving. If another user modified the entry, a conflict dialog appears. |
| Change Reason | A written explanation required when editing an entry (in ISO Compliance Mode). Stored in the audit trail for regulatory traceability. |
| ISO Compliance | A mode that enables audit trail, mandatory change reasons, and disables hard delete — providing the change-tracking rigor required by ISO 9001 and similar standards. |