Arranging forms: moving rows, keeping pairs together
The order a form is filled in is the order the person at the desk works in, and that differs between a front desk and an HR office. Admins can reorder the rows of the main forms — rows, not fields, so the layout stays symmetrical and the paper still matches.
- Open the form — client, unit, employment, or invoice lines — as an admin, and press Arrange at the top right.
- Drag rows. Each row has a handle. A row with two fields moves as one; the fields never swap sides or split. Single-field rows move the same way.
- Locked rows stay put: rows that print on a document in a fixed position (the lease's parties block, the payslip header) or that the platform needs first (the unit on a client form). The lock icon says why on hover.
- Done saves for the whole business. To save for one role instead — the HR office fills the employment form in a different order from a manager — choose Save for: Admin.
- Reset returns the shipped order. Changes are logged with who and when.
What cannot be done here
Removing a field — never, from any screen; a field you do not use can be hidden only by a setting that exists for that purpose, and most fields have no such setting because the document behind them needs them. Changing a label. Putting three fields on a row. Moving a field between rows. Per-person form layouts. Each of these would make the form something support cannot reason about from the name alone.
Why rows
Two fields on a row split it equally; every single-line control is the same height; a form reads as a grid. Letting rows move preserves all of that. Letting fields move would break it on the first drag, and you would spend the next hour repairing alignment instead of running a building.
Related
Describes the platform as it is today. Something out of date? Tell us. · help 0.12.3