Notes and Domino applications carried a generation of approvals, requests and registers, each with its own database, its own forms and its own agents.
| Element | What it holds |
|---|---|
| Databases (.nsf) | one per application, often hundreds per company, with replicas per site |
| Forms and subforms | the screens, with computed fields and hide-when formulas |
| Views | the lists, with selection formulas and categorised columns |
| Agents | scheduled or triggered code: reminders, escalations, routing |
| ACLs and roles | who may read, author, edit; reader and author fields |
| Mail-in and workflow | approval chains built on mail routing |
| In hcl notes and domino applications | In SmartApps |
|---|---|
| A Notes form with computed fields | A screen with components, properties and expressions |
| A view with a selection formula | A grid on a data handler with a filter |
| A scheduled agent | A criterion on records, or an action on a clock |
| An ACL with reader fields | An access policy inherited from the source, plus the role's scope |
| A mail-routed approval | An approval flow with levels, alternates, clocks and escalation |
| A replica per site | One app, read in place, with the site as a scope |
| Documents stored in the database | Rows in the system of record, or files kept with the instance |
HCL continues to sell and support Notes and Domino; the reason to move is the duplicate data, the aging forms and the skills, and the moment is usually a platform contract or an ERP change.
A manufacturer kept 340 Notes databases, 60 of them still in daily use. The inventory grouped the 60 into 14 app types: 22 were request-and-approval forms, 11 were registers of equipment or suppliers that duplicated the ERP, 9 were escalation agents around late deliveries. The registers were retired in favour of screens on the ERP objects; the requests became process apps; the escalation agents became one data-driven app. The first ten apps were rebuilt in six weeks and the 60 in a quarter.
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.