Path | Duration | Level | Before you start | |
🔵 Configurator · Level 1 | 35 min | Starter | [[07 · Reglas - un formulario que reacciona | Rules - a form that reacts]] |
A form is filled in once, but its responses are consulted many times: in the web history, in the mobile cards, in a PDF that's archived or sent to a customer. The Summary tab decides how they look. Designing it at the same time as the form prevents unreadable histories.
🎯 By the end you'll know
How to configure the history table: columns, order, names and consolidated values.
How to design the mobile card of each response.
How to configure the PDF of the response.
How to mark which fields will go to Power BI.
How to edit several responses at once with bulk editing.
🧠 The idea: three views of the same response
View | Who uses it | What it needs |
History table (web) | Whoever reviews and filters many records | Few columns, the ones that help search and decide |
Card (mobile) | Whoever is on the floor | The essentials at a glance: what, when, who and how it is |
Whoever archives, audits or sends | The complete, clean record, with a logo |
💡 Ask yourself this before configuring: when someone looks for a control three months from now, what columns will they need to see to find it?
🛠️ Guided practice
Open the Packaging control in the Form Builder and go into the Summary tab.
Step 1 · The history table
In Table, mark as visible: Line, Product, Shift, Batch, Temperature, Result and Expiry date.
Drag the columns to leave this order: Line · Product · Batch · Shift · Result · Temperature · Expiry date.
Change the name of the Temperature (°C) column to T ª to make the table more compact.
On Temperature enable a consolidated value (for example, the maximum). It will appear in the footer of the history.
Enable the system fields Creation date, Creator user and Status.
Step 2 · What gets sent to Power BI
In the same table, mark for Power BI only the fields you're going to analyze: Line, Product, Shift, Result, Temperature and Rejection reason. You'll use this in lesson 14.
⚠️ Don't mark everything "just in case". Every field that's sent to Power BI and isn't used only makes the dataset heavier.
Step 3 · The mobile card
In Card presentation (you'll see the preview on the right):
Card element | Field |
Main field (title) | Product |
Secondary field | Batch |
Date and time | Creation date |
User or department | Creator user |
Additional information 1 | Line |
Highlight (top corner) | Status, with its automatic color |
Images | Main image (the Photo field) |
By using the Status as the highlight, the card will change color depending on the result of the control.
Step 4 · The PDF
In the PDF tab:
Select and order the document's fields.
Include the header with ID, creation date, user and status.
Disable the option to show empty fields: OK controls have no corrective action, and that way the PDF stays cleaner.
Choose your company's logo.
Step 5 · Fix several responses at once
Create three test controls with the wrong shift. In the history, select them, click Bulk edit, choose the Shift field and the correct value, and confirm.
⚠️ Bulk editing replaces the previous value in all the selected responses and also triggers the events of each modified response. Keep this in mind when, in the next lesson, you configure email alerts.
🔍 Check that it works
The web history shows the columns in your order, with the temperature maximum at the foot.
On mobile, each control appears as a card with the product as the title and the status colored.
The PDF of an OK control doesn't show the empty corrective action.
⚠️ Common mistakes
"I hid a field in the Summary and it still appears in the form." The Summary only controls the history and the export. For the form, rules are used.
"A new field doesn't show up in the export or in Power BI." When you add a field to the form, also check the Summary: it has to be marked as visible or for Power BI.
Hiding a column from a profile to "protect" it. The visibility details hide the column from the history and the export, not from the form.
Bulk editing a disabled field. It's not possible: bulk editing respects the Form Builder configuration.
🏋️ Challenge
The quality manager wants only their profile to see the Corrective action column in the history, and the PDF that's sent to the customer not to include it. Configure it and check it with operario.prueba and calidad.prueba.
📚 Learn more
➡️ Next lesson: Events - letting the process move on its own