Tags

Give flexibility without bloating the registry: instead of creating a new field for every temporary slice, you tag and filter.

The same tag can mark a client, contract, request or opportunity — which allows cross-module slicing.

A good tag fits in one or two words and works in more than one context — the same tag marks requests, projects, clients and contracts, so names that are too generic say nothing ("important") and ones that are too specific can't be reused ("client-x-meeting-march"). Before creating one, look for an existing tag that already serves the purpose: two synonymous tags split the records and hide half the set in each filter.

Uncontrolled vocabulary produces "urgent", "URGENT" and "urgent!" as three different tags. It's worth agreeing on a standard before spreading them around, and reviewing the list every now and then.

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.

For a temporary or experimental slice, yes. If the criterion has become permanent and feeds a report, its place is a real field in the record.

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