Details
The Details component is the side panel that surfaces information about whatever the planner has selected on the board: the jobJobA high-level container, comparable to a project, that bundles related tasks together with common information such as customer, billing, and address. behind it, the taskTaskA unit of work that belongs to a job. It appears in the open task list until it is scheduled to a resource., the appointmentAppointmentA task scheduled to a resource for a specific period - the scheduled instance you see on the planning board., all in one place. It is the "tell me everything about this record" panel - and what counts as "everything" depends on the customer.
This page is where you decide that. Different tenants need different things visible on click: a service company wants the customer's address front and center, a manufacturer cares about the BOM, a logistics outfit wants the next stop. The pane layoutPane layoutThe configuration of the fields and groups shown in the details component, maintained on the Pane Layouts settings page. lets you cherry-pick which fields appear, group them into sections, and order them however the planner's eye works fastest.
How the page is laid out
The view has two trees side by side. The fields tree on the left is the catalog: every field available on the job, task, and appointment entities, grouped by which entity they belong to. The details tree on the right is your current layout - the groups and fields that will actually render in the details component.
The output is what the planner sees in the details panel:
Arranging fields and groups
Everything is drag-and-drop:
- Drag a field from the fields tree onto any group in the details tree to add it.
- Drag a field inside the details tree to reorder it within its group, or to move it to another group.
- Drag a group to reorder groups.
- Select a field and click delete to remove it. Selecting a group and clicking delete removes the group along with every field inside it.
Group and field labels
The labels users actually see come from the translations setup. When you rename a group or a field's captionCaptionThe label shown for a field or entity in the interface, translatable per language. A tenant that calls jobs "projects" changes the caption, not the data model. in this layout, you are renaming it everywhere it appears - manage those captions in one place to keep terminology consistent across the application.