Locais do cliente

This is the first record of the field operation. A customer has a single record, with one address — but the maintenance company serves the same condominium in three towers, and each tower has elevators with their own history. The location is what separates "serving an address" from "maintaining an installed base".

The addresses where the equipment is installed: the building, the warehouse, the store. A customer usually has several, and it's the location that organizes the technician's daily route and groups the installed base. — this is the role of the "Customer locations" screen within the platform.

The location is the customer's physical address — the building, the warehouse, the store — and this record gathers what the field team needs: location name, owning customer, full address, who opens the door with the contact phone and the access instructions. The Equipment tab shows what is installed there, with the type and status of each item. It is the location that organizes the technician's route for the day, so the more complete the record, the fewer calls in the middle of the visit.

Select a location and use the "Location labels" button: a single PDF comes out, in 60×40 mm thermal format, with the label of every piece of equipment at that address that already has a QR generated. It's the way for someone who's going to stick labels thinking "the machine room of block B" — ticking equipment one by one in a grid is the easiest way to skip one and only notice at the inspection. Equipment without a QR isn't included in the batch; generate the QR on its record first.

Two fields in this record are worth gold in the field: "Site access" keeps the arrival and entry instructions — a front desk that requires ID, the time the machine room opens, where to park — and the technician reads this before leaving; "Contact phone" is the number of whoever opens the door, not the customer's sales line. A visit lost to a closed gate is almost always one of these two fields left empty. Fill them in thinking of someone who has never been to the address.

The technician's route orders visits by proximity. The coordinate is resolved automatically on saving, from the city and state — but if the address is incomplete it doesn't come out, and the location stops being included in the calculation without any error appearing. The Installed base and compliance panel lists how many ended up in that situation.

Access is governed by profile: whoever administers the account grants "view" (and the other verbs) on the Access screen. If someone on the team cannot find this screen in the menu, the path is to ask the administrator for the grant — absence from the menu is not a bug, it is permission.

Like every standard engine list, this one exports Excel, PDF and CSV of the entire set of locations, keeps saved views per user and has a trash — add ?excluidas=1 to the URL to see what was deleted. Search also works by URL (?q=text) and filtering by field with ?fd_=valor, using the screen's dictionary key — that's how links coming from other panels open the list already filtered, without depending on you redoing the filter.

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.

Deleting would take with it the address of equipment that still exists at the customer, and their history would start pointing nowhere. Whatever leaves operation becomes INACTIVE: it disappears from the combos, and the past stays standing.

The tab shows the assets installed at this location — identification, type and status — but that isn't where equipment is registered: the asset is born on its own screen (Installed assets), where it gets a contract, plan and QR. The tab exists as the visual answer to the question "why register the location?": it is what shows that address's installed base gathered together. If a piece of equipment appears at the wrong location, correct it on the asset's own record, changing the Location field.

In the record's activity panel, each note has "Turn into request". The click creates a ticket with the note's text, who wrote it and the link to this record — nothing is retyped. Use it when the note is a request for action ("someone needs to review this"); the note stays where it was. The button only appears once the record has been saved; a read-only session (demo) doesn't create one.

"Where is the equipment I maintain?" — when that question comes up, this is the screen where it gets answered.

Register one location per physical address, all pointing to the same customer — a condominium with three towers that have separate entrances usually yields three locations. It's the location, not the customer, that organizes the technician's daily route and groups the installed base in the panels; a "general location" with everything in it makes the route send the technician to a single point and hides where each piece of equipment really is. When in doubt, ask: does the technician arrive through the same gate? If not, they're different locations.

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

Because it is the data that avoids a wasted trip. The machine room is locked, the basement has access control, the store has opening hours. The name and phone of whoever receives the team are worth more to the operation's cost than half of the equipment's technical sheet.