Docs Designing the system 15
What your design means for the people using it
On this page


- Live screens. Lists and forms follow every change as it happens, whoever made it. A screen that is not current says so.
- No role, no object. Someone who opens an object's list, a record or its New form (a link, a bookmark) without a role on it reads You have no access to it, or it is not live: ask its stewards for a role, with the way back home. The page says the same for an object that does not exist or is not live yet, so it never tells them whether it does.
- Copy from any list. Pointing at a cell of any list (an object's, a screen's table, a query's result) shows a small copy button at its right edge: one click puts the value (a lot number, a quantity) on the clipboard, and it shows a tick. Cells being edited, and empty ones, have none.
- Rules as they type. Your rule pipe runs in the form on every keystroke, as advice, and again on the server when they save, which decides. The message they read is the one your script threw. The advice never holds the form up: a rule that takes more than a few seconds in the browser, or a browser too old to run rules beside the page (Firefox before 114), is skipped there, and the person reads the rule's words when they save.
- Why? Anything they cannot change or do has a Why? that explains it from your policies, states and rules. Write hints so it also says what to do instead.
- Changes that wait for approval. Where your design says so (Stewards, Approval of record changes), the fields concerned are tagged needs approval on the form. As soon as someone changes one, the form sums up every change it would send (as it is → as edited), who approves it, and asks why; Save becomes Submit for approval. Once they are sure, they submit, and the change is sent to the stewards instead of being written; the record shows it in a banner (as it is → as asked, who has signed, who is awaited) until it is approved and applied, rejected (with why) or withdrawn. While it waits, the record goes on: a lot is moved in, tracked in, another field corrected, and the change still waits, and is applied on the record as it is when the last approver signs. Only when what it was asked on changes (one of its fields; for an action such as a hold, the record's state; or who must approve it, a value your approval follows) is it void, at once: not applied, the approvers no longer asked, and its requester told what changed and who changed it, free to ask again on the record as it is. Approvers sign on the record or on Approvals (Changes to records); a new record's request has a page of its own.
- A list: the box at the start of its bar finds records by any value you may read (a reference by its name, the state); click a column's head to sort by it (again for the reverse order, a third time for the list's own order). Sorting and finding cover every record, not only the rows shown, and the order you chose is kept for that list in your browser.
- Archived records leave the lists (Show archived brings them back), and are read-only until someone allowed to restores them.
- When the database is unavailable, nothing can be saved: a banner says so, Save is disabled, and what they typed stays on screen. If a save was interrupted and its outcome is unknown, they press Send again: the same change is never saved twice.
- A transaction's page reloaded by accident (F5, a kiosk restarted in the same tab): the browser asks first while something is typed. Reloaded all the same, the form comes back to where it was, in that tab, for the person signed in: what was typed is back (a password or a sensitive input is typed again), and one run before the answer came is looked up. If it ran, the page says so and shows what it did; if it is not known to have run, what was typed is back and the page says so: send it again as it is, and it is never done twice. Change any input first and it is a new run. Closing the tab, or another person signing in there, forgets it.
- A record's form reloaded by accident works the same way, for its Save, its actions, archiving and the New form: the fields changed come back (a sensitive one is typed again) and the page says so, adding when the record was changed by someone else since they were typed. A save, an action or a create sent just before the reload is looked up: if it went through, the page says so (the New form links to the record made); if it is not known, press Save (or Create, or the same action) again as it is: it is the same change, never made twice, and it is refused, not saved over, if someone changed the record in between. Discard forgets it.
- Everything is audited: who changed what, when, and which rules ran, including refused attempts and what services did on their behalf.
- A new version loads by itself. When the server is updated, open screens reload on their own, straight away if nothing is being edited; otherwise a banner says a new version is ready, and it loads once they save or discard. Tablets and phones can install OpenCore MES as an app (on HTTPS), and show a page of its own while the server cannot be reached, coming back by itself.
Spaces around what is typed are dropped. A lot number typed as " 4711 " is kept as "4711", in a form, a transaction, a plan's screen, an import or a web service call, and a field of only spaces counts as empty, so a required one asks again. Spaces inside a value stay; a long text (several lines) keeps its lines and indents as written. Passwords are kept exactly as typed.




Languages: the plant's, each person's, and your design's words
The plant's language is set in People & departments → Formats → Language: the language pages are drawn in unless a person picks another, and the languages offered. It is a change like any other, approved by governance. Dates, times and numbers keep the plant's formats whatever the language.
Each person picks their own from the menu under their name, or on the sign-in page (the device remembers it). The page is drawn again in it, right to left for Arabic or Hebrew. A language no longer offered is kept for them and the plant's is used.
The platform's words (Save, the sign-in page, a refusal) come from a language pack installed for that language, as a suite is: without one they are English. The Suites page lists the packs installed, how much of the platform's words each says, and whether a native speaker reviewed it.
Your design's own words (an object's label, its fields' and states', an enum's values, a transaction's label and its signature's meaning, a screen's titles) are translated in the design itself, on its Translations tab: each word as you wrote it in English, beside its translation into one of the plant's languages, the missing ones marked. A word said in several places can be said differently in one of them. Translations are approved with the change, each language its own part of it, by the design's stewards.
- A word you reword in English shows in English until it is translated again: an old translation is never shown for new words. The tab lists translations no word says any more, to remove.
- What is stored never changes: a state, a value, a record's fields are kept as designed; only what people read is translated. Reports, exports, the audit trail and the HTTP APIs keep the design's own words.
- A signature means what its signer read. When someone signs a transaction (or approves a record's change) in another language, the words they read are kept with the meaning as designed and their language. If the translation changed while their page was open, the signature is refused and they read it again.
- An AI asked to translate reads the words to translate, and what each language is missing, through
get_texts, and saves translations into the change as any other edit.