Custom code and API, for when the visual builder isn't enough

Start with what can be configured: entities and fields for the data, rules and workflows for the processes, and list, board or calendar views for everyday work. Code comes in when the screen or the logic you need doesn’t fit those pieces — and these are the cases where it pays off:

• A dashboard with the company’s own indicators — charts, totals and comparisons that no ready-made view shows.
• A record page, list or form designed for one specific task, in place of the screen Megorix generates from the fields.
• Server-side logic no rule covers: calculations across several entities, special validations, scheduled tasks.
• A connection to another program through its API, with the credentials stored encrypted.

Dev Studio is the Megorix code editor and runs in the browser, with nothing to install. A widget is a React component written in TypeScript, in one file or several.

1. 1

   Create the widget and choose where it appears: a page of the system, a dashboard, a section of a page, or in place of an entity’s list or record page.

2. 2

   Write the code with Megorix interface components — tables, forms, dialogs, tabs — and with functions that read and save records, upload files, generate PDFs or call an external system.

3. 3

   Watch the result in the preview, compiled in the browser as you type. When you save, the server compiles the code and checks the types.

4. 4

   Every save is a draft. When you publish, a version is kept — and any earlier version can be restored.

• Only administrators save and publish code; everyone else uses the result with the permissions they already have.
• Widgets also serve the website and online store: as a whole page, the header, the footer or a section inside a page built in the builder.

The Megorix REST API gives access to the data of every module — list, search, create, update and delete records — to files and to PDF generation. Each API key acts as a service user, with that user’s roles, visibility rules and field permissions; it can have an expiry date and a list of allowed IP addresses. The documentation follows the OpenAPI format.

To connect to another program, Megorix stores the connection — HTTP, FTP or SFTP, with basic, token, API key or OAuth2 authentication — with the credentials encrypted. A mapping says what to send when something happens, for example when an order is confirmed, retries if the call fails and logs every delivery. The other system’s response can be written back to the record; in the other direction, inbound webhooks receive signed notifications.

That is how, at a haulage company, the details of a completed delivery go to the invoicing program, or how, at a repair shop, the number of the document issued is kept on the repair order. See the integrations MegaPC already has in place.

Connected to Megorix over MCP, Claude can create modules, entities and fields, widgets, rules, workflows and store pages from a description — if the person connecting it is an administrator and grants that permission. Everything it builds stays as a draft, in the test environment, until someone reviews and publishes it. Read more about AI in Megorix.