TenkaTenka
Sign in

Tenka Help Center › Today's visits (mobile)

Today's visits (mobile)

Your visit route with location check-in, customer briefing, and result logging directly on the timeline.

🕒 Updated on Sep 13, 2026📖 ~3 min read

What you find on this screen

A portrait of the screen, read from the screen itself — it changes when the screen changes.

Form fields

Tipo*Categoria do item.
Título*Título do item.
DescriçãoDetalhe do item.
OrdemOrdem de exibição.
Visível ao clienteExibir este item no portal do cliente.

Start here

Para que esta tela existe
Dictionary anchor screen for the detail (changelog items). It doesn't appear in the menu. — this is the role of the "Changelog item" screen within the platform.

How to

As linhas de uma versão do changelog
Each item belongs to a version and appears in the changelog the customer reads. An item without a published version is invisible to them — that's how you prepare the note before announcing it.
What each item field means
An item is ONE line within a changelog version. "Type" classifies the nature of the line, so the communication can be read by category. "Order" defines the display sequence within the version — what matters most comes first. "Visible to customer" decides, item by item, what goes into external communication: the same version can have internal lines and public lines side by side. "Title" and "Description" are the text the final reader sees.

Rules

Esta é uma tela de apoio — o caminho normal é pelo cadastro principal
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.
A visão salva guarda busca, filtros, colunas e ordenação
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.
O erro de preenchimento aparece no campo, ao sair dele
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.

Frequently asked questions

Que pergunta do dia a dia se responde aqui
"Where do I see changelog items?" — when that question comes up, this is the screen where it gets answered.
Por que esta tela não aparece no menu?
Because it's an anchor screen: it exists to give names, labels and help to the FIELDS of the changelog item (the detail dictionary), not to be the work path. The normal flow is through the main changelog register — that's where each version's items are added, ordered and edited. If you got here through a link, nothing is broken: use the main register to change the content.
Como descobrir quem mudou um campo desta ficha?
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?".
Was this article helpful?
Tenka Academy

Step-by-step learning paths for your industry, inside the platform.

Explore the Academy