Changelog

Publish each delivery's news in client-friendly language. The published changelog is visible on the Client Portal — keep the text free of technical jargon.

Communication of improvements, fixes and deliveries to customers — this is the role of the "Changelog" screen within the platform.

What the customer reads about the new feature — written as a benefit, not as a field name. House rule: if the text only makes sense to whoever wrote the code, it isn't ready yet.

Here you record ONE changelog entry: the title of the improvement or fix, the release and the product/package it shipped in, the publication date and the description. Two switches close the record: "Published" says whether the entry is in effect, and "Visible to customer" decides whether it goes into customer-facing communication — you can keep an internal record published without exposing it. The entry then appears in the changelog list, which is the history of what was communicated.

This list accepts slicing by link: "?q=text" opens already searched, "?fd_=value" filters by a dictionary field (in a relationship field, it matches by label, not by id) and "?excluidas=1" opens the trash. It is the number-trail path: a total in another report can link straight to the set that formed it. Normal navigation pays no extra query — the filter only runs when the link carries a parameter.

"Published" controls whether the entry is in effect — a draft communicates nothing. "Visible to customer" is a second gate: it decides whether that entry appears to the customer or stays only in the internal view. The useful combination is precisely the asymmetric one: publish internal technical changes without customer visibility, and reserve the visible text for what the customer understands and values. Review both before saving — checking one doesn't imply the other.

This form belongs to the screen engine: in the header there's previous/next navigation, which goes through the records in the same order as the list you came from — useful for reviewing a sequence of entries without opening them one by one. The screen also respects your preference of 1, 2 or 3 columns of fields (adjustable per screen, with a global default in User preferences), and the "?" button opens this help on any screen.

Access is governed by profile: whoever administers the account grants "view" (and the other verbs) on the Access screen. If someone on the team cannot find this screen in the menu, the path is to ask the administrator for the grant — absence from the menu is not a bug, it is permission.

The Excel, PDF and CSV buttons of this list export the WHOLE SET of the current slice — not just the visible page. Whatever filter is applied counts: refine first, export afterwards. The columns follow your saved column preference, and saved views keep slices you always use (e.g. only what is visible to the customer). The trash, with what was deleted, is accessible via "?excluidas=1".

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 record's activity panel, each note has "Turn into request". The click creates a ticket with the note's text, who wrote it and the link to this record — nothing is retyped. Use it when the note is a request for action ("someone needs to review this"); the note stays where it was. The button only appears once the record has been saved; a read-only session (demo) doesn't create one.

"What changed for my customer?" — when that question comes up, this is the screen that answers it.

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