What is a record in Rose Rocket? One order, one page

What it is

A record is one real thing your business tracks: one order, one customer, one invoice, one driver.

Take an order, for example ORD-28 on the Orders board. It is one flatbed load for Midwest Steel Supply Co, Gary to Dallas, now marked Paid. On the board it is one row. Open it and it is one page, the record page, with every detail of that load filled in. The row and the page are one record seen two ways.

Fields on a record

A record is a filled-in copy of its object’s fields. On an order’s record page, for example ORD-28, the Order Summary tab opens a General section of fields such as Customer, Status, First Pickup and Line Haul Rate, each filled for that one load. A field’s type decides how it is filled: Status picks from a list, First Pickup is a date and time, Line Haul Rate is money. The board shows a few fields as columns; the record page shows all of them. Every order carries the same fields because they are defined once, on the Order object, in Object Builder.

Connections between records

The Customer field on an order reads a company name, for example Midwest Steel Supply Co on ORD-28, but nobody typed that name. The field holds the customer record itself. That is why the name is a link at the top of the record page: click it and you are on the customer record, with its contacts and orders. Change a phone number there and every order pointing at that customer shows it. Origin and Destination point at location records the same way, and the Shipments widget lower on the page lists the shipments that point back at it (SHP-19 on ORD-28). Builders call a field that does this a connection field.

System fields you never typed

Some values on a record come from Rose Rocket, not a person. A record’s ID, for example ORD-28, was numbered when the record was created; no one chose it. Every record carries Created at, Created by, Updated at and Updated by, which update on every save. You never fill these in, but you can show them as columns where your organization has them switched on, and let workflows read them.

The Activity tab keeps the full history: every note, comment and field change, with who made it and when. Its Filters button narrows that history by type, Notes & comments or Record changes, and by person, so finding who changed a value is two picks, not a long scroll: Record changes, then the teammate’s name. The clip uses the same filters on an order, for example ORD-28, to keep one teammate’s note.

What changes a record

Three things change a record: someone edits a field on the record page, someone deletes it, or a workflow acts on it, such as the protect invoiced orders rule that refuses an edit once an order is invoiced. Everything else you do changes what you see, not the record: filter a board or the Activity log, hide a column or switch views, and each order, ORD-28 for example, is unchanged. Add a field to the Order object, as in customize the Order object, and every order gains it at once, blank until filled.

Builders say the Order object is the shape and each order, for example ORD-28, is a record of it: one object, as many records as loads.

Where you meet it in Rose Rocket

• Orders board (Operations › Orders) → one row per record, for example ORD-32 to ORD-28, under ID, Status, Customer, Origin and Destination → one record per row, one field per column.
• Record page (for example, ORD-28) → the detail view shows the full relevant contents of that one record, its Activity history included; what each role sees is set by detail view permissions.
• Customer field on a record (for example, Midwest Steel Supply Co on ORD-28) → the name is a link → a connection to the customer record, not a typed name.

Go deeper

• Platform basics: objects, records, boards, workflows
• Object Builder: the fields records carry
• Board views: boards list records
• Detail view permissions: the record page by role
• Customize the Order object: a field added to every order
• Protect invoiced orders: a workflow on a record