Path	Duration	Level	Before you start
🔵 Configurator · Level 1	60 min	Starter	[[04 · Datos maestros - Assets, Productos, Entidades y Estados	Master data - Assets, Products, Entities and Statuses]]

The time has come to build. In this lesson you'll create the Packaging control in the Form Builder, choose each field type well, give it clean identifiers and publish it so your team can use it.

🎯 By the end you'll know

How to move around the Form Builder and its tabs.
How to choose the right field type for each piece of data.
How to define IDs that will serve you later in rules, events, queries and Power BI.
How to organize the form with blocks and rows.
How to configure the minimum needed to publish: module, status group and permissions.

🧠 The idea: every field is a piece of data someone will analyze

When designing a form it's tempting to think only of the operator's screen. But every field is also a piece of data that will later be filtered, used in a rule or drawn on a chart. Three decisions make the difference:

1. The field type. Always use the most specific type possible:

Data	Bad	Good
The machine	Short text	Asset selector
A measured value	Short text	Numeric
An OK / NOT OK result	Short text	Single choice
A reusable list	Single choice copied into each form	Entity selector
A date	Short text	Date or Date and time

2. The ID. Each field has a Title (what the user sees) and an ID (how Mairu recognizes it in rules, events, queries and integrations). The ID must be unique, start with a letter and contain no spaces, accents or special characters. Mairu proposes it from the title, but review it: temperatura is much easier to use later than Temperatura_del_producto_en_grados_C_.

3. Required, disabled or hidden.

I need…	Configure
It to always be filled in	Required
To show it but not let it be changed	Disabled
It to appear only in certain situations	Hidden + a rule (lesson 7)

🛠️ Guided practice: the Packaging control

Step 1 · Create the form and configure General

Go into Forms and create a new one.
In the General tab:

Title: Packaging control. ID: control_envasado.
Module: Quality > Packaging.
Status group: Packaging control (the one you created in lesson 4).
Enable Allow comments, so that Quality can leave notes on each control.

Step 2 · Add the fields

Click New field and create the following. Review each one's ID.

Title	Field type	ID	Configuration
Line	Asset selector	`linea`	Required · Line level only
Product	Product selector	`producto`	Required
Shift	Entity selector	`turno`	Shifts Entity · Required
Batch	Short text	`lote`	Required · Mark as scannable
Packaging date	Date	`fecha_envasado`	Required
Temperature (°C)	Numeric	`temperatura`	Required · placeholder "e.g.: 3.5"
Result	Single choice	`resultado`	Options OK / NOT OK · Required
Rejection reason	Entity selector	`motivo_rechazo`	Rejection reasons Entity · Hidden
Corrective action	Long text	`accion_correctora`	Hidden
Photo	Image media	`foto`	—
Operator signature	Signature	`firma`	Required

💡 In the Asset selector you can limit from which level to which level the tree is shown. Use the preview to check that the operator only sees lines.

Step 3 · Arrange the layout

Create a 3-column row and place Line, Product and Shift in it.
Create another 2-column row for Batch and Packaging date.
Group Temperature, Result, Rejection reason and Corrective action in a block called Control result.
Leave Photo and Signature at the end. Drag the fields to reorder them.

Step 4 · Permissions

In the form's Permissions tab:

Profile	Read	Create	Edit	Delete
Operator	—	✅	—	—
Quality	✅	✅	✅	—

These permissions are synchronized with Settings > Security: changing one changes the other.

Step 5 · Preview, save and publish

Click Preview and fill in the form. In the preview settings you can simulate another user or profile.
Save. If a warning icon appears, open it: it lists what's missing.
Publish. To publish, these are mandatory: title, ID, module, status group and at least one profile with permissions.

🔍 Check that it works

Log in as operario.prueba: in Quality > Packaging the Packaging control appears.
Create a control from mobile and scan a code as the batch.
As an operator, in the history you only see your controls. As calidad.prueba you see all of them.
Rejection reason and Corrective action are not shown: they are hidden until you create the rule in lesson 7.

⚠️ Common mistakes

"It won't let me publish." One of the five requirements is missing. Check General and Permissions.
"Users don't see the form." It may be saved but not published (white button), or their profile may not have permissions.
Changing IDs when the form is already in use. Rules, events, queries and Power BI point to the IDs. Define them well at the start.
Modifying a form with responses and not seeing the change in the old responses. By default, each response keeps the version of the form it was created with. If you want the old ones to use the latest version, enable Always allow the latest version of responses in General.
Making a big change to a form in use. Use Save as new form or Save as template to work on a copy.

🏋️ Challenge

Quality wants Production to be able to consult all the packaging controls without modifying or deleting them. Create the necessary profile (or use the Production supervisor from the lesson 3 challenge), give it just the right permissions and check with a test user that it sees all the operators' controls but can't edit them. What changes if you remove Read?

📚 Learn more

➡️ Next lesson: Repeated information - Tables and Subforms

Lesson 5 · Your first form