NET approval tool, a Python script with a web page, work until the person who wrote them leaves.
| Element | What it holds |
|---|---|
| The application | a web front end and a database |
| The database | often a copy of ERP data, plus the app's own tables |
| Business logic | in code, in stored procedures, in both |
| Integrations | direct SQL to the ERP, file drops, scheduled jobs |
| Users and roles | a local user table |
| The author | one person, or a vendor long gone |
| In custom-coded internal applications | In SmartApps |
|---|---|
| A screen in code | A screen composed from components, with the same fields |
| A copy of ERP tables | Data handlers on the ERP objects, read in place |
| Business logic worth keeping | A registered function the app's actions call by name |
| Business logic that routes | Criteria on arrows and decision nodes |
| A scheduled job that finds exceptions | A start criterion on records |
| Direct SQL writes to the ERP | Write-back through the released interface, acknowledged |
| A local user table | Roles resolved from the directory and the source systems |
Code that computes stays as functions; code that copies data or routes work is replaced by handlers and flows.
A telecom company's dock scheduling tool, written in 2015, read a nightly copy of inbound orders and wrote appointments to a table outside the ERP. The dock scheduling app replaced it in six days: carriers book slots on a portal screen against live order lines, the gate check-in runs on a phone, and the goods receipt is posted through the ERP's interface with the document number back. The 2015 code was archived with its last export.
It becomes a registered function the app's actions call by name, with its inputs and outputs logged.
The process owner, with the configurator role; the application team keeps the gates and the write-back switches.
The inventory is fixed-scope; the first ten apps carry a fixed price written before the work; the platform is priced by capacity with apps included.
We list the applications, the forms and the workflows you run today, group them by the app type they become, and write a fixed price for the first ten before any work begins.
