19 articles about Apps, in reading order.
Parsware Platform
What Parsware is and how its parts fit together, shown through one real application, from the tables underneath it to the phone screen, the approval process and the printed report.
Parsware Platform
A step-by-step walkthrough, from an empty solution to a working app. Create a table, add five kinds of field, build a filtered view, and open it with real rows in about ten minutes.
Parsware Platform
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.
Parsware Platform
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.
Parsware Platform
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.
Parsware Platform
A model-driven app, Contact desk, with the Contact list screens and the Contact table side by side in its navigation. The drawn screens open as its home page, their own links stay inside it, and the task inbox comes with it.
Parsware Platform
Contact list opened from the Shell's app list, with nothing around it: every screen at its own address, a top bar that says who's signed in and signs them out, and the platform's own bar switched off so the drawing fills the window.
Parsware Platform
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.
Parsware Platform
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.
Parsware Platform
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.
Parsware Platform
Who may open an app, what they may do with a table, and which of its records they see are three separate questions in Parsware, answered by users, roles, teams and policies. This is the map: what each piece is, where it lives, and which question it answers.
Parsware Platform
A new user is an email, a name and a password you hand over yourself. We added Alex Morgan, had a short password refused, gave Alex the Field Sales role, and watched their first sign-in open on the one app that role is shared with.
Parsware Platform
One app, two roles. We copied Field Sales into a read-only role, gave it to Jordan, and opened the same Accounts list as Alex and as Jordan: the same records, with and without the commands to change them.
Parsware Platform
A team is a group of people that records can belong to, and it can hold a role. We put Alex and Jordan in Field Sales North, gave the team the Field Sales role, and watched Jordan's open session gain New on its next refresh, with no sign-out.
Parsware Platform
A role says what someone may do with a table; the policy beside each permission says which of its records that reaches. We narrowed Jordan's read on accounts from every record to Mine and my teams', handed an account to the team, and Jordan's list went from a hundred accounts to four.
Parsware Platform
The unit policies need an organisation to measure against. We built one in the Organisation app (Head Office with a North and a South region), put three people in it, and gave Jordan read access on My unit and below. From Head Office, Jordan sees the accounts both regions create, and nothing owned outside the chart.
Parsware Platform
Any Studio app can be published at a web address of its own. One panel says which app, which address, who can open it, and which screens a stranger may see before signing in; one tick puts it on the internet, and the same tick takes it off. We published the landing page sample and opened it on a desktop and a phone.
Parsware Platform
One case, followed from both sides: a customer raises it on the portal, the support team answers it inside the platform, the customer replies with a photo, and the status says whose turn it is at every step. The customer and the team never share a screen, and each one sees only what is theirs to see.
For Power Apps
Parsware for Power Apps installs two model-driven apps. Parsware Studio is where makers draw reports and screens, and it only exists in development. Parsware is what every environment gets, and it starts almost empty on purpose, because the reports and screens your users open belong in your own apps.
