Rename product TallyFlow IoT → TallyFlow Edge across vault

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.
This commit is contained in:
TNB
2026-07-27 15:48:08 -04:00
parent 4d09d3195b
commit cf1e09e1c4
33 changed files with 128 additions and 128 deletions
@@ -14,7 +14,7 @@ flowchart LR
A[TallyFlow Assets Mobile] -->|REST / WebSocket| B[TallyFlow Core]
C[TallyFlow Print] -->|REST| B
D[TallyFlow Capture] -->|REST| B
E[TallyFlow IoT] -->|REST / MQTT| B
E[TallyFlow Edge] -->|REST / MQTT| B
B -->|REST / Integration Hub| F[ServiceNow]
F -->|REST| B
```
@@ -26,7 +26,7 @@ flowchart LR
| Direction | Typical Data | Trigger | Recommended Method |
|---------------------------|---------------------------------------|----------------------------------|-------------------------------------|
| **ServiceNow → TallyFlow** | Asset master data, locations, status | Scheduled or event-driven | ServiceNow Integration Hub → Core REST |
| **TallyFlow → ServiceNow** | Real-time location, RFID scans, condition updates | Mobile scan, IoT event, zone change | Core → ServiceNow REST / Flow Designer |
| **TallyFlow → ServiceNow** | Real-time location, RFID scans, condition updates | Mobile scan, Edge event, zone change | Core → ServiceNow REST / Flow Designer |
| **Bidirectional** | Asset status synchronization | On change or scheduled | Core as middleware |
## Key Integration Points
@@ -41,7 +41,7 @@ flowchart LR
- This data is pushed to ServiceNow for visibility in Asset Management, Work Orders, or CMDB.
### 3. Real-time Location & Condition
- IoT and mobile events flow through Core and are published to ServiceNow (via REST or Integration Hub).
- Edge and mobile events flow through Core and are published to ServiceNow (via REST or Integration Hub).
## Authentication & Security