Pack do produto

Anchor screen for the detail dictionary. Does not appear in the menu. — this is the role of the "Product pack" screen within the platform.

Besides name, description and status, the pack carries two fields that define the commercial side: the Billing model says how that pack is charged, and the Unit says in what measure it is counted. These fields give meaning to the price recorded for the pack — the same product can have one pack charged one way and another pack another way, which is why price and version are recorded per pack, not for the whole product.

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.

Defines which items and quantities make up a pack. Changing the composition applies to future sales; orders already issued keep what was sold at that moment and do not change retroactively.

The pack is the piece the rest of sales references: in the product form, prices (with validity) and versions are registered per pack — without a pack, the new price and new version buttons stay disabled. And in the customer record, the linked packs make up the Subscription tab: the customer's monthly amount is the sum of the pack links. Changing a pack therefore affects both the catalog and the recurring billing of the customers who have it.

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 product packs?" — whenever 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?".