Overview
An ERP screen designed for everyone fits nobody exactly. Your invoice screen carries fields your industry never uses; the tab labels use the vendor’s vocabulary rather than yours; the column your team checks most often is three clicks away.
The Screen Modifier changes that for your installation, without code and without waiting for a release. You describe what should change — on the sales invoice screen, hide these two fields, rename this tab, add a column to the list, move this group to another page — and Nama ERP applies your instructions on top of the original design each time a screen is built.
That layering is the important part. Your customisations sit over the system defaults rather than replacing them, so an upgrade improves the underlying screen without discarding your changes.
Features
Choose exactly how far a change reaches
One modifier can target a single screen or the whole system:
| Scope | What it changes |
|---|---|
| Entity type | One screen — the sales invoice, and nothing else. |
| Entity type list | A named set of screens, so one change lands on several related ones. |
| Master files | Every master-file screen — customers, items, accounts. |
| Documents | Every document screen — invoices, receipts, journal entries. |
| All screens | Everything in the system. |
The broad scopes earn their keep on sweeping changes: removing one unused element from every screen at once, rather than editing hundreds of them.
A drag-and-drop editor, not a form about a form
Filling in configuration collections by hand is precise but slow. The visual layout editor gives the same power on a canvas: it renders the real screen as users will see it, you rearrange it directly, and the result saves straight back into a modifier record. Mobile and quick-create layouts are respected, so what you see is what that view will actually look like.
Modify a screen, or create a new one
A modifier can either change the screen users already open, or produce a new named screen alongside the original — so a simplified entry layout for the warehouse can exist beside the full one for accounting, from the same underlying entity.
Lists and filters too
Screens are not only edit forms. Modifiers control list views as well: which columns appear, what quick filters are offered, and how results are presented — the difference between a list your team scans and one they have to interrogate.
A clean way back
Screens can be regenerated to apply the defaults together with every active modifier, or reset to system defaults entirely — so an experiment is always reversible.
Where it fits
Screen Modifier decides where things appear. Field behaviour — input masks, allowed values, read-only rules, calculated fields, how a lookup searches — belongs to Fields and Entities Settings, and business logic belongs to Entity Flows. Together they cover most of what other systems would quote as a customisation project.
Read the full Screen Modifier documentation.
