Panel (form)

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

Each row is a quoted product or service, with quantity and value. Their sum is the opportunity's value — which in turn feeds the funnel and the forecast.

Each item links a catalog product to the opportunity, with description, quantity and unit value. The "Recurring" flag is what separates the deal's two totals: a recurring item makes up the monthly value (MRR), a non-recurring item makes up the one-time value. It's this separation, done item by item, that lets you read the recurring portfolio without mixing in one-off projects — and it's from it that the numbers the funnel and the dashboard weight are born.

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.

This is an anchor screen of the detail: the natural place to add and adjust items is inside the opportunity, where they appear next to the stage, the values and the forecast — and where the deal total recalculates in context. Well-entered items are what back up the opportunity's value: a deal with a value typed "on the side", with no items to explain it, becomes a number with no memory when someone asks where it came from.

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 opportunity items?" — 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?".