Cadastro próprio

Each record type built in the object builder opens here — the title, the columns and the fields are the ones your company defined. If the name at the top says "Reports" or "Fleet", it is because someone in your account created that record type; the screen is the same, the content is yours.

The list and the form of a record type created in the Object Studio. — this is the role of the "Custom record" screen within the platform.

This form shows the fields of the record type your company created in the Object Studio, with the right control for each type (text, number, date, list, yes/no). Required fields cannot be saved empty, and invalid numbers or dates are refused naming the field.

The date field of this record type is typed, not picked from a calendar — and that is on purpose: the record stores values in free format, and a calendar with a fixed mask would come out in Brazilian format for all languages. Type in dd/mm/aaaa or aaaa-mm-dd; both are accepted. List fields show the options defined by whoever designed the object; those marked with * are required; and the gray help text below each field comes from the object's own design in the Studio.

The screen became the standard list: search, filters, saved views, columns, export and trash with Undo. Click the record (or New) to open the form, with the detail tabs when there are any.

Save stores without leaving the form (Ctrl+S); Save and close returns to the list; the header arrows move from one record to the next. Delete sends the record to the list’s trash, from where Undo brings it back.

A missing field, a wrong label or a requirement that makes no sense are solved in the builder (Settings ▸ Object builder), never here. This screen obeys the definition — changed there, changed here instantly, including for records already entered (old data is not lost; the new field appears empty).

Records created here belong to the company in use and obey the same profile permissions as the other screens. A custom object is not a shortcut out of governance: whoever cannot see, does not see.

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.

The object is born hidden until it is published in the builder — that is where you decide which module it goes into and who sees it. If it has already been published and still does not appear, check the profile: the view permission is granted per profile, as on any screen.

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