Não conformidades

You don't register a nonconformity. It is born the moment an item fails inspection, with the severity the checklist defined and the deadline the severity determines. Nothing depends on someone remembering to write it down.

What failed inspection and hasn't been resolved yet, by severity and deadline. Each pending item becomes a quote for the customer to approve or a service order for the team to fix. — this is the role of the "Nonconformities" screen within the platform.

Open the pending item, check the severity and click generate corrective order. The order is born pointing to the same equipment and already linked to the pending item, so when it closes the pending item closes too - without anyone having to close it in two places.

Critical severity is born with a same-day deadline, high with one week and medium with one month. The deadline isn't decorative - it is what orders this queue and feeds the red card on the installed-base panel.

Check the boxes of the same customer's pending items and use "Quote selected": a single proposal comes out with all the lines named. It's not just convenience — one inspection finds five pending items in the same building, and five separate R$ 400 proposals are five negotiations the building manager won't take to the owners' meeting; one R$ 2,000 proposal with the five lines and the standard for each is a single decision. The count of checked items appears in the header before the click, so you can confirm the selection took.

When you save a view with the Views button, it stores four things: the search text, the applied filters, which columns appear (and in what order) and which column the list is sorted by. Applying the view restores everything at once — including resetting the sort and the page you were on, so the result is exactly what the view describes. Views saved before this version remain valid: whatever they didn't store simply doesn't change when applied.

Nas fichas, sair de um campo já dispara a conferência do que dá para conferir na hora: campo obrigatório deixado em branco e e-mail mal formado. O aviso aparece embaixo do campo e desaparece quando você começa a corrigir. Campo numérico não precisa de aviso: ele simplesmente não aceita letra enquanto você digita. Isso é conforto, não a validação final: ao salvar, o sistema confere tudo de novo do lado do servidor.

"What has failed and I haven't fixed yet?" — when that question comes up, this is the screen that answers it.

Each pending item has two possible destinations: becoming a service order (a repair covered by the contract) or becoming a proposal (a service to sell). When a path is used, its button gives way to the status label — "SO in progress" or "already quoted" — so the row never offers the same way out twice. What can't exist is the third way out: a pending item open forever. If both labels appear, both paths have already been taken and what's missing is to execute, not to decide.

Open the record and look at the Timeline on the right: it shows each change as "from one value to another", with the person and the date. When there are many changes, use the two filters at the top of the timeline — one by field, the other by person. The search runs in the database, so old changes show up just the same. You can also ask Tenkai: "who changed contract 482?".