7 articles about Custom apps and controls, in reading order.
Custom apps and controls
When a screen needs something tables, forms and views can't say, you write it in React. A custom app is built on your own machine with two downloads from the help site, packed into one file, uploaded once, and opened from the Shell like any other app. We built a visitor board for reception.
Custom apps and controls
Everything a custom app does in Parsware goes through one object: who's using it, where it was opened, the data their role can read, saved queries, Custom APIs, object storage and the log. We grew the visitor board with company totals from a saved query, readable visit purposes, and a button that keeps today's list as a file.
Custom apps and controls
A field sometimes needs an editor the platform doesn't ship. A custom control is one React component that stands in for it: it shows the field's value, reports every edit, and leaves saving to the form. We built a badge-number field for the front desk outside the repository, packed it into one file and installed it.
Custom apps and controls
A custom control does nothing until a form uses it. In the form designer, select the field, choose the control under Custom Control, and save. We put the badge field on the Visitor form, where reception now types b-2210 and the form saves B-2210.
Custom apps and controls
A web resource is a file stored in a solution and served by the platform: a stylesheet, a script, an image, a page. We built the printable visitor badge as four of them, a page with its stylesheet, script and logo, and opened it at its address.
Custom apps and controls
A custom app or control is part of its solution, code and all. We exported Visitors from Development with its visitor board, its badge field and its web resources, imported it into Test, and watched an altered copy of the same file get refused.
Custom apps and controls
Packing and uploading a control for every change is slow. In a development environment, register its running dev server instead: save a change, refresh the form, and it's there. We fixed the badge field's dash this way, then packed 1.1.0 when it was right.
