crm3
This commit is contained in:
18
ROADMAP.md
18
ROADMAP.md
@@ -21,6 +21,9 @@ MRP Codex is being built as a streamlined, modular manufacturing resource planni
|
||||
- CRM reference entities for customers and vendors
|
||||
- CRM customer and vendor create/edit/detail workflows
|
||||
- CRM search, filters, and persisted status tagging
|
||||
- CRM contact-history timeline with authored notes, calls, emails, and meetings
|
||||
- CRM shared file attachments on customer and vendor records
|
||||
- Theme persistence fixes and denser responsive workspace layouts
|
||||
- SVAR Gantt integration wrapper with demo planning data
|
||||
- Multi-stage Docker packaging and migration-aware entrypoint
|
||||
- Docker image validated locally with successful app startup and login flow
|
||||
@@ -30,14 +33,12 @@ MRP Codex is being built as a streamlined, modular manufacturing resource planni
|
||||
|
||||
- Prisma migration execution is committed and documented, but local Windows Node 24 schema-engine behavior remains inconsistent; use Node 22 or Docker for migration execution
|
||||
- The frontend bundle is functional but should be code-split later, especially around the gantt module
|
||||
- CRM contact history, shared attachments, and deeper operational metadata are not built yet
|
||||
- CRM deeper operational metadata and lifecycle reporting are not built yet
|
||||
|
||||
## Planned feature phases
|
||||
|
||||
### Phase 1: CRM and master data hardening
|
||||
|
||||
- Contact history and internal notes
|
||||
- Shared attachment support on CRM entities
|
||||
- Better seed/bootstrap strategy for non-development environments
|
||||
- Deeper CRM operational fields and lifecycle reporting
|
||||
|
||||
@@ -87,13 +88,14 @@ MRP Codex is being built as a streamlined, modular manufacturing resource planni
|
||||
- Stronger validation and error reporting across all APIs
|
||||
- More automated tests for auth, settings, files, PDFs, and workflow modules
|
||||
- Better mobile behavior in module-level pages
|
||||
- Ongoing responsive-density tuning for module-level layouts and data-entry screens
|
||||
- Consistent document-template system shared by sales, purchasing, and shipping
|
||||
- Clear upgrade path for future module additions without refactoring the app shell
|
||||
|
||||
## Near-term priority order
|
||||
|
||||
1. CRM contact history and internal notes
|
||||
2. CRM shared attachments and operational metadata
|
||||
3. Inventory item and BOM data model
|
||||
4. Sales order and quote foundation
|
||||
5. Shipping module tied to sales orders
|
||||
1. CRM deeper operational fields and lifecycle reporting
|
||||
2. Inventory item and BOM data model
|
||||
3. Sales order and quote foundation
|
||||
4. Shipping module tied to sales orders
|
||||
5. Live manufacturing gantt scheduling
|
||||
|
||||
Reference in New Issue
Block a user