XLSX import
Spreadsheet data is validated and normalized before entering the workflow.
- XLSX
- column validation
- normalization
- error handling
CASE / EXCEL / WEB
XLSX / WORKFLOW / INTERNAL APP
An Excel-based process moved into a controlled web application.
Instead of relying on manual spreadsheet operations, the workflow moved to a central web panel with XLSX import, business rules and safe state control.
CONTEXT
The spreadsheet worked as a tool, but not as a controlled process engine.
The operational workflow depended on data imported from Excel, sorting and manual movement of rows according to transport rules.
The goal was to keep XLSX as a convenient input format while moving business logic into a web application with predictable behaviour.
Business logic outside Excel
Sorting and transport rules are enforced by the application instead of user formulas.
- sorting
- transport rules
- ordering logic
- state control
Controlled operations
Row movement and reset actions are explicit and protected against accidental use.
- row movement
- double reset confirmation
- state history
- fewer mistakes
One working environment
Users work in one browser-based panel rather than multiple spreadsheet copies.
- central view
- consistent data
- browser access
- simpler deployment
ENGINEERING TAKEAWAYS
What changes when a process moves from Excel to the web.
- Excel can remain an input format without remaining the process engine.
- Central validation removes inconsistencies between spreadsheet copies.
- Critical actions should be explicit and protected.
- The main value is controlled business logic, not merely a web interface.
CASE / NEXT
SIMILAR ENVIRONMENT?
Discuss the environment