Panels

Start and End delimit the effective period: the row without an end date is the current one. Job position and Range record the position in the salary structure for the period — the range comes from the bands of the position itself. Salary is the monthly amount for the period; Hourly rate, the hourly equivalent for calculations based on hours. The annual adjustment applied in the job positions record can generate these changes automatically, when the option to generate the salary change is checked.

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.

Each row is a change with an effective date — promotion, raise, change of position. Payroll cost and hourly cost use the effective date, so entering it with the wrong date changes the cost of months that have already been closed.

The Employee cost screen starts from the base salary of one of these effective periods: once the employee is chosen, the period selector lists each change with the start date and the salary. With no row here, the cost has nowhere to start from and the screen warns. Keep one row per real change — hiring, merit, promotion, raise — with the correct start date, because that is what defines which salary applies in each period.

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.

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