Data entry in Apps
Questions, checklists, measurements and photo capture belong to the App that people use. Konnie, an external agent or a developer authors ordinary React controls and the task's logic. There is no separate Forms feature, Form editor or Form component to configure.
Ask Konnie to create or change the inputs in the relevant App. Describe what the person needs to enter, when questions apply and what the saved result should mean. Review the App draft, preview the task and publish the App separately when it is ready.
Choose where the information belongs
| Result | Destination |
|---|---|
| A new shared record type for requests, observations or measurements | A connected Model |
| Records in an existing Custom Table | The existing Custom Table |
| Answers, notes or photos about an existing order, position or holder | Evidence linked to that object |
| Production progress, material movement or another business action | The existing operational API |
The App connects directly to its destination. Bind the Model's create action when rules govern creation. An Automation can handle a separate reusable process. Use the native operations to change stock or complete an order. See Collecting data with Apps.
Adapt the experience
The App defines its fields, labels, instructions, defaults, conditional questions, required answers, calculations and sequence. It can be a short single screen or a longer task with several steps. Its layout is independent of the stored data.
Useful customer-editable choices can appear in normal App settings. Other changes are made in the App source, including through Konnie. There is no mandatory field editor or second publication to keep in sync. Keep English and German labels and validation messages consistent.
Continue a saved draft
An App can save working input privately for the signed-in person. Check its save indicator before leaving: Saved, Saving, Not saved, an error and a conflict mean different things. A saved draft can be reopened in the same App/context. If saving fails, keep the screen open and retry. If another window changed the draft, use the offered reload or reconciliation action before continuing.
Submitting records and uploading files require an internet connection. A resumable draft is not an offline submission queue. If a submission is unconfirmed, use the App's Check or retry action for that same request. Do not start another request merely because the response was lost. The App should keep its original request identity and inputs until the result is confirmed.
Uploaded files and a saved business record are separate results. Keep successful upload references when a later action fails; the App should show the actual state rather than treating a selected file as a completed upload.
Verify the result
Test required and conditional inputs, keyboard use, touch controls and narrow layouts in both languages. Reopen a saved draft and check recovery from a lost response. Use an authorized test record to confirm that one submission produces the intended stored result without duplicates.
Report editing and report-template design have their own workflow. A generic Table or evidence save does not automatically create a signed report or PDF. See Working with reports.