Etapas do funil

Funnel detail (dictionary anchor). — this is the role of the "Funnel stages" screen within the platform.

Four fields define the stage: Order positions the column on the kanban (the sequence the deal goes through); Color visually identifies the stage; Probability (%) is the stage's default weight in the weighted pipeline — an opportunity in a 60% stage counts 60% of its value in the forecast; and "Goes stale in (days)" is the deadline after which an opportunity idle in the stage is flagged as stuck too long on the kanban. Probability and staleness are the two yardsticks that give the funnel a management reading.

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.

The order of the stages is the order of the funnel, and each stage's probability is what weights the sales forecast. Changing the probability changes the forecast value of ALL the opportunities that are in that stage.

This is an anchor screen of the detail: the normal path to create, reorder or adjust stages is the Funnels screen, where the stage appears in the context of the whole funnel. And the usual caution with a funnel in use applies: existing opportunities hang on the current stages, and changing probability or order changes the reading of the weighted pipeline and the kanban from then on. Fine-tuning is welcome; restructuring a live funnel deserves prior agreement with the team.

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.

"Where do I see funnel stages?" — 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?".