17 articles about Model-driven apps, in reading order.
Model-driven apps
Building an app doesn't give it to anyone. Share it with a role, check who that actually reaches, and the app appears on their launcher and nobody else's. The sharing travels in the solution, so you don't redo it in every environment.
Model-driven apps
A form is tabs, rows and sections, with a header that stays put whichever tab is open. Lay one out in the Form Designer, give a table a second form for a different team, and let people switch between them on the record.
Model-driven apps
A note is fixed text on a form, like a heading, an instruction or a warning, written in Markdown and shown beside the fields it's about. Here is how to add one, what it can contain, and why it can't be used to slip markup into a form.
Model-driven apps
A field's type decides what it stores. Its control decides how people fill it in. Turn a yes-or-no field into a switch with its own words, show a date in the Persian calendar, and put a control you built yourself on a form.
Model-driven apps
A view is a list of a table's records, and it's where most people spend their day. Choose its columns, put them in order, give a column a width, and decide which list an app opens on.
Model-driven apps
Each column of a view can have its own header, date format, alignment and control, without changing the field. Turn "Purchase Date" into "Bought", write dates out in full, line up the amounts, and show a yes-or-no column as switches.
Model-driven apps
Build a filter from conditions in groups, each group either And or Or, and put one group inside another. Use it once while you browse a list, or save it on a view so everyone who opens the view gets it.
Model-driven apps
Two small views decide how people pick a record in a lookup. A lookup view chooses the columns of the Advanced lookup grid, and a quick find view chooses which columns typing searches, so "Berlin" finds the contacts in Berlin.
Model-driven apps
A timeline puts every call, email, meeting and note about a customer in one column on their form, newest first. Filter it by kind, start a new one already filled in, and set it up in the Form Designer from any table that points at the record.
Model-driven apps
Any table with a date can be read as a calendar. Pick which field says when a record starts, colour the blocks by a choice, and people click an empty slot to book it, with the rooms side by side on the day sheet.
Model-driven apps
Add your own buttons to a list's or a form's command bar. Most need no code, because they open a view, start a record or open an address. When the button depends on what the user ticked or typed, it runs a short script.
Model-driven apps
A command bar can use your organisation's words and follow the order people work in. Rename the platform's own commands, hide the ones a list doesn't need, drag everything into place, and divide it into groups.
Model-driven apps
A dashboard in Parsware is a screen you draw. Counted tiles, charts, the table's own grid and its quick create form sit on one page, and the page goes into an app's navigation like any table.
Model-driven apps
Every table keeps four stamps for you, Created On, Created By, Modified On and Modified By, plus an Owner. Put them in a view or on a form and people see names and dates, not ids, with nothing to set up.
Model-driven apps
In Parsware, saving a table is applying it. The database table and its columns exist before the screen comes back, a form and a view come with it, and a change that would cut stored data short is refused.
Model-driven apps
Every Parsware environment comes with an Organisation app. It holds your units as a chart, the people in each one, and who does which kind of work where, which is what processes route work by and what "my unit and below" access is measured against.
Model-driven apps
Deleting a table in Parsware removes its definition and its data from the environment, so the platform first checks what still depends on it. A lookup that points at the table, or an app that shows it, blocks the delete and is listed by name.
