TNB
cf1e09e1c4
Update product naming in docs, marketing, architecture, use cases, and capabilities materials. Rename related notes, screenshot folder, and marketing image filenames. Keep git/repo identifiers (e.g. tallyflow-iot) and generic industry IoT language unchanged.
29 lines
1.2 KiB
Markdown
29 lines
1.2 KiB
Markdown
# tallyflow-web Review
|
|
|
|
**Tech Stack:** Vue.js (Vue 2 based on structure)
|
|
|
|
## High-Level Architecture
|
|
- Classic Vue + Vue Router + Vuex store
|
|
- API layer in `src/api/`
|
|
- Views in `src/views/`
|
|
- Shared components in `src/shared/`
|
|
|
|
## Key Areas to Investigate
|
|
- Asset / Zone management
|
|
- RFID / Edge integration points
|
|
- Reporting & exports
|
|
- User workflows (receiving, movement, printing)
|
|
- ERP integration surface (API and webhooks)
|
|
- Photo display and filtering with tags (Capture integration)
|
|
|
|
## Initial Observations
|
|
- **Core Entities**: Things (assets), Zones, Maps, Organizations, Users, Reports, Exceptions, Webhooks, API Keys.
|
|
- **Key Workflows Visible**:
|
|
- Asset import (`ImportAsset.vue`)
|
|
- Zone import and management (`ImportZone.vue`, `Zones.vue`)
|
|
- Location tagging (`LocationTags.vue`)
|
|
- Exception tracking and detail views (`ExceptionDetail.vue`, `ReportExceptions.vue`)
|
|
- Reporting on zone durations, events, zone categories (`ReportZoneDurations.vue`, etc.)
|
|
- Map-based visualization (`Map.vue`)
|
|
- **Tech Notes**: Uses Leaflet for maps, Chart.js for reports, Vuetify for UI. Strong emphasis on ERP-adjacent data flows (imports, reports, exceptions).
|
|
- **Next**: Review API layer and shared components for integration patterns (RFID, printing, Edge). |