Operations and business teams
- Build pages by placing widgets on a grid
- Bind widgets to ERP data with expressions
- Your own tables without a database project
Compose apps from widgets, bind them to ERP data or your own tables and publish them to the people who need them.
No separate platform to secure. Apps use the same data and permissions as everything else.
The people who build apps and the people who use them work on the same data and permissions.
Real screens from Fynd ERP, shown with demo data.
See every app in the organisation, its status and its published version.
Follow one app from an idea to daily use. Each step happens in Fynd ERP, so there is no separate platform to run.
The plant wants a simple screen to track canteen coupons issued per shift.
The builder adds a coupons table with date, shift and count columns.
Widgets are placed on a grid and bound to the table and ERP records with expressions.
A button on the page runs an automation when a supervisor saves the day's count.
The draft is submitted, approved and published as a version that never changes in place.
The parts of a low-code app builder teams ask about most.
Lay out pages with widgets on a grid or in a flow, and bind each one to data with expressions. Run queries, show messages and chain steps on clicks and changes.
Create your own tables with text, number, date, true or false, JSON and reference columns. Add relations and views, and import or export rows in bulk.
Edit a draft, submit it, approve it and publish it. A published version never changes in place, so you can always see what ran.
Call REST APIs and run automations from an app. Queries run on the server, so the browser never receives the credentials.
Your apps read and change the same records the standard screens use.
No. Most apps are built by placing widgets and binding them to data. You can add your own logic in code when you need it.
Yes, within the permissions of the person using the app. Every run is logged.
On the server. Queries run server side and the browser never receives the credentials.
You edit a draft, submit it, get it approved and publish it. A published version is never changed in place, so you can always see what ran.
Yes. A custom table belongs to the organisation and its rows can be used by every plant in it.