Vacation

Organizes who leaves when, avoiding the "everyone in January" problem. The record feeds the schedule and the cost (advances/provisions according to the regime).

Register the period per employee; approvals follow the company's workflow. Registered vacations help the manager avoid promising deadlines with the team away.

For CLT there are legal rules (periods, ⅓ bonus, deadlines) — confirm with the accountant. For PJ it's a contractual agreement: register it the same way for the planning to count.

The Team Capacity screen considers current allocations; keep vacations registered so the board tells the truth.

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.

Two requests from the same team in the same period can be spotted by sorting the list by the start of leave or by filtering the period — the accrual and leave-period columns exist for this, and a saved view keeps the checking filter for next time. Before approving, check who else is away on the same dates: capacity compromised by overlap later shows up as a shortage of people in planning.

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