How do I add a new field to a screen in my ERP without a developer?
In Intagya ERP you open the screen you want, such as a quotation, and click Builder in the top bar. Then click Field and drag the right type, such as text, date or choice, to its place on the screen and write its name. The change stays a draft until you click Publish; the system checks it first, then staff see it. You can undo any published change with one click. Intagya Builder is an add-on paid once from the app store.
The sales manager of a supplies company asks for something simple: a box on the quotation called Requested delivery date. The accountant wants Payment Terms to be required before any quotation goes out.
In most companies this small request becomes a message to the developer, a week of waiting, then an invoice.
A month later a second request of the same kind arrives.
Why does a small change need a developer at all?
Because in most systems a screen lives in files only someone who writes code can reach. A mistake in those files can stop the screen for everyone, so the owner is afraid to change it himself, and he is right.
Intagya Builder takes another way: the change happens on the screen itself while you look at it, and it does not reach staff before you review and publish it.
How do I add the field myself, step by step?
- Open the screen, such as a new quotation, and click Builder in the top bar.
- Click Field on the floating bar at the bottom of the screen.
- Drag the right type, such as Date, to where you want it. You see where it lands before you let go.
- Write the field's name on the screen, and a short tooltip if you like.
- Click Publish.
To change an existing field, click it and a card opens beside it. It has the label, the tooltip and three choices: hidden, read only and required. Each can take a condition you write in words, with no code.
What if I write a wrong or unsuitable name?
Before publishing the system checks everything you wrote. Emoji, long dashes and repeated marks block publishing. A very long name, or English on an Arabic screen, is flagged for review.
Each item has one button that fixes it, such as Use the suggestion, so your screens never look different from the rest of the system.
My advice: name fields the way your team talks, not the way textbooks do. Requested delivery date is clearer to a salesperson than Customer expected delivery date.
Will every employee see the new field?
You decide. The card has a Who can see it section where you pick the groups that see it.
The difference matters: a field you added with the builder and limited to some groups is truly locked, so nobody else can read its value, even from reports or exports. A standard system field is hidden on the screen only. If the information is sensitive, such as an agreed profit margin, put it in a new field limited to management.
What happens to my changes when the system is updated?
This is what worries any company that tried customizing before. In Intagya Builder, if a change no longer fits the screen after an update, it stops by itself and the screen goes back to normal, so nobody's work stops.
The system administrator sees a notice on that screen with the reason. He can make the change again himself, or click Request a repair and our team fixes it for one customization hour.
What else can I change besides fields?
Printed documents too. From Printing you hide a part of an invoice, quotation, purchase order or delivery slip, change its printed name and add a field, then preview the document before publishing.
On list and kanban screens you add a line to the card or a new search filter. Ready packs add the fields your sector needs in one go. And with intagya AI you write what you want in one sentence; the change reaches you as a draft that you review and publish.
Will I still need a developer after that?
For names, fields, conditions and who sees what: no. Complex calculations, a link to an outside program or a report with a special layout are still a developer's work. Do not try to turn the builder into a tool for everything.
Start tomorrow with the one screen your team complains about most. Ask them which two boxes they miss, add them, publish, then ask them again a week later.
Read: what should I ask before choosing an ERP?
Read the Intagya Builder guide step by step
FAQ
How much is Intagya Builder?
100 USD paid once per workspace, shown in your currency, with no monthly fee. You request it from the app store, then Request activation.
Who can change screens?
The system administrator of your company, and the employees he gives this right to. Deleting a field added with the builder is for the system administrator only.
Do staff see the change while I work on it?
No. Everything you change stays a draft until you click Publish, and Undo on the floating bar throws the whole draft away.
Can I undo a change I published?
Yes. Changes lists everything published on the screen, who published it and when, with an Undo button beside each change.
Does Write what you want send my data to the AI?
No. Only your sentence and the names of the screen's fields leave the workspace. intagya AI answers with a request from a closed list: add, rename, hide or show a field, or add a hint or a page, and the change lands as a draft that only you publish.
Can an employee who is not the owner publish a change?
When the owner turns on Changes need the owner's approval, the employee sends the changes with Send for approval, and they show to everybody only after the owner approves them in the Approvals app.
Do the new fields show in the mobile app?
Soon, with the next release of the Intagya app, read only and with the same limits on who sees each field.
Is this your business?
Want to see IntagyaERP on your own workflow?
Book a demo, tell us how your business runs, and watch the system handle a real scenario from your company.
Book a demo