SCAN / SEARCH ORDER
ORDER INPUT
NEW ORDER
Order Key = Customer Code-PO#-JOB#
WIP CONTROL
PROCESS UPDATE
FG COMPLETED
SELECT REPORTS
EXPORT FORMAT
FG STOCK
KEY FIGURES
WIP BY PROCESS
WIP ANALYSIS
ORDER STATUS
CURRENT PROCESS — where open orders are sitting
OVERDUE ORDERS
DUE SOON — next 7 days
AT RISK / DELAYED
Overdue and incomplete, or due within 3 days and less than 70% complete.
CUSTOMER-WISE WIP SUMMARY
PROCESS LOG — complete history of every status change
ADMIN CONTROL
USERS
User records are stored in MySQL. Create, edit, enable/disable, assign role and reset password through the API.
ROLES / PERMISSIONS
Approved Phase 3 roles. Do not add roles here. Permission changes in production will be saved by the PHP API in Phase 4. This matrix is read-only in the current frontend.
AUDIT LOG
System-wide, append-only. There is no edit or delete control. The server becomes authoritative for Audit Log in Phase 4.
CLOUD / SERVER BACKUP
Production backup architecture is MySQL → server backup → secure storage. CREATE BACKUP writes an XML file on the server. XML restore remains for migration and emergency recovery.
CREATE BACKUP writes XML on the server and downloads a copy. Server backup history is listed below.
XML BACKUP & RESTORE — MIGRATION / EMERGENCY
Keep this available until the master XML has been migrated into MySQL. Restoring replaces all current data. A safety backup is downloaded first.
Restore validation runs before data is replaced.
EXCEL BACKUP & RESTORE
Readable .xlsx for review. Not a restore file.
Use only when no XML backup is available.
DATA STATUS
AUTOMATIC BACKUP
CURRENT WIP — EXCEL TEMPLATE / BULK IMPORT
First-time WIP load or a controlled bulk refresh.
Existing Order Keys are updated, new ones added. A preview is shown before anything changes.
MONTHLY ARCHIVE
Exports completed orders and their process log to a dated file, then optionally removes them from active WIP.
SYSTEM SETTINGS
Administrative settings only. Dark Mode and the sidebar collapse preference stay in the header as user preferences.
There is no system-settings API. Server configuration is in backend/.env.
USER / UI RESET
Safe reset of filters, sidebar state and temporary UI preferences. Order data, process statuses and the Audit Log are not changed.
SYSTEM / DATA RESET
The API does not expose a destructive factory reset of MySQL. Use CREATE BACKUP and RESTORE FROM XML under BACKUP / RESTORE to replace WIP data. The password field below is unused for production data.
Administrator permission is required. This password is a usage barrier, not enterprise-grade security.