Panels (BI)

Type classifies the absence (vacation, leave, unexcused absence…) and it is by type that the views group. Hours quantifies partial absences — half day, early departure — without consuming the whole day. Status tracks the absence's cycle, from recording to completion. Start and End delimit the period, and the Note records the context that the type alone does not tell — the reason, what was agreed with the manager.

Here you see and fix loose child records, one by one. In day-to-day work, however, the right thing is to create and edit them inside the parent record's form: that is where the business rules run (recalculated totals, validations, numbering, history). Editing directly here is useful for auditing and for correcting a specific case — but it can leave the parent record with an outdated total, and that raises no error on screen.

The absence reduces the person's capacity in the period and appears in the team's planning. Recording it with the right date matters more than it seems: it is what prevents the team from being planned with someone who will not be there.

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.

In the employee record: open HR, Employees, go into the employee and use the Absences tab — it is one of the details of the form itself. This screen exists as the dictionary anchor for these fields, not as the place where they are maintained. Keep the records up to date: a recorded absence is what deducts the available hours for the period, and planning done on hours that do not exist charges its price later.

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?".