Planned Tasks
The planned tasks component is the planning, in grid form. Every appointmentAppointmentA task scheduled to a resource for a specific period - the scheduled instance you see on the planning board. the planner has scheduled, with the resourceResourceAn entity that can carry out work - a person, vehicle, tool, or room - that you schedule on the planning board. it's assigned to and all the metadata the back office sent along, listed as rows. Where the planning board is the calendar UI for making the plan, this is the query UI for interrogating it.
That distinction matters because a calendar view, however well-designed, cannot answer questions like "how many appointments do we have for customer X this week?", "show me everything tagged urgent across departments", "bulk-change the category on the 40 appointments for project P". The planning board has no group-by, no bulk-edit toolbar, no filter on arbitrary columns. The planned tasks grid does. As a side benefit, the grid can also push selections back to the planning board, which makes it just as useful for navigating the plan as for analyzing it.
Apart from the unique features below, the component behaves like every other grid in Dime.Scheduler.
Updating appointments in bulk
Once one or more rows are selected, a row of contextual action icons appears on the toolbar:
The first three are bulk updates. Each one opens a modal that applies a single value to every selected appointment 1:
- Importance for marking a batch of appointments more or less urgent.
- CategoryCategoryA visual indicator (a color) applied to appointments to classify or label them. for retagging.
- Time markerTime markerA visual indicator on an appointment, separate from its category, used to flag a status or condition at a point in time. for relabeling.
These are protected operations. The corresponding importance bulk update, category bulk update, or time marker bulk update user action must be assigned to one of the planner's user rolesUser roleA named bundle of user actions assigned to users and user groups. Permissions flow through roles, never directly to a user. for the icon to do anything.
Driving the planning board
The other two contextual icons are the planning board's side of this grid's purpose. Because every planned task points to a resource, selecting rows and clicking tells every planning board in the profile to show only the resources behind those selected appointments. The companion button clears the filter; it turns red while a filter is active so the state stays visible.
This is what makes "show me the planning of every resource on project P" a single gesture: group the grid by project, select the project's rows, hit filter, look at the resulting board.
The filter coexists with the standard resource filter and with the column filters in the planning board's resource grid. When more than one is in play they combine: a resource must satisfy every active filter to appear. That stacking is powerful, and confusing the first time you encounter it. The rule of thumb: if a planner expects to see resources and the board is empty, an unintended filter is usually the cause.
Navigating to an appointment
For one-off lookups, double-click a row to jump to its appointment on the planning board. The board adjusts its date range if the appointment falls outside the current window, and the appointment itself flashes yellow briefly so the eye can find it. Resources that sit on a different page of the resource grid are not pulled in automatically, so the planner may need to filter the resources or page through to find them.
Persistent highlighting
A double-click jumps once. Highlight marks a set of appointments persistently across the planning boards in the profile, the way the Gantt chart's critical path marks a chain of tasks. Select one or more planned tasks and two buttons appear in the top bar: to turn on the highlight, to clear it.
Highlighted appointments stay marked until the planner clears them, which makes them useful for following a thread of work across navigation: pick the appointments that share a customer, highlight them, then navigate the board freely; the highlighted ones stay easy to spot.
As with the resource filter, the resource may still sit on a different page; use the resource-filter button on this grid to bring the highlighted set together. The planning board's highlight features cover what else changes on the board when a highlight is active.
Scoping the data
The planned tasks grid does not apply a default date filter, so it shows every appointment by default. Filtering by date through the start/end columns works but is awkward when the planner wants to flip between weeks. The date picker component is the shortcut: set a range there and the grid scopes to it, alongside whatever column filters are also active.
Side actions
When a selected planned task is a project task (visible in the "Task Type" column), the row's context menu carries an Open project item that loads the project into the Gantt chart. Same gesture as in the open tasks and route sequence grids.
Reference
The grid is stateful: layouts (columns, filters, sorting, page size, the date scope) save and share like any other grid.