Data Sources
General
Datasource Type:
Default: configure datasource via UI.
Custom: only use the Custom Datasource Type when you want to customize the data retrieval and storage, and when the default configuration via the UI does not meet your needs.
Datasource Name: Name of the tasks to be shown in the planning view
Choose Color of Datasource: this is the color that will be used for the datasource in the planning board. This can be useful if you have multiple datasources (e.g. multiple teams) within the same datasource, and you need a visual indicator of which resource (e.g. person) belongs to which datasource (e.g. team).
Settings
Event Scheduling
Event Read Only: Default: Unchecked. When checked, users cannot edit event details.
Event Resizable: Default: Checked. When unchecked, users cannot resize events by dragging at the edges of the event.
Event Draggable: Default Checked. When unchecked, users cannot drag events.
Event Manually Scheduled: Default unchecked. When checked, 24Planning will NOT take into account dependencies to automatically reschedule events.
Enable Auto Rescheduling
In addition, there are some settings that govern the 24Planning behaviour in case multiple events are scheduled in parallel. In some use cases, parallel events are not desirable and you can specify that 24Planning should auto-reschedule those parallel events and reschedule future and/or previous events in the planning window to accommodate the new event:
(Beta) Auto Reschedule Parallel Tasks: Check the box in case you would like 24Planning to auto-reschedule parallel events.
(Beta) Auto Reschedule Mode:
Forward: Schedules the event to start immediately after the preceding task is completed, without modifying the dates of earlier tasks.
Backward: Schedules the event to finish just before the next task begins, without altering the dates of following tasks.
Forward-Backward: Combines both approaches by keeping the event in its current position while adjusting the schedule of other tasks, both before and after.
(Beta) Auto Resch Allow Push Out View: This setting allows the scheduling system to automatically adjust tasks outside the currently visible planning view. When enabled, tasks can be pushed beyond the visible timeline to accommodate changes. Note: Enabling this option does not account for events outside the visible view, which may result in overlaps with those unseen tasks. Use with caution if managing tasks beyond the current view is critical.
Event Batch Processing
You can use batch classes in conjunction with 24Planning to enhance the functionality of 24Planning with your own code plugins. There is an example batch class described further on in this manual. This section describes the batch class sections within the Datasource configuration. If you are not using batch classes, you can leave these settings unalterned.
Batch class name: name of the batch class.
Batch class: Dropdown with the list of batch classes that are available to link to this datasource.
Split batch events in groups: avoid hitting the Salesforce Governor limits by splitting in batches. Because Apex runs in a multitenant environment, the Apex runtime engine strictly enforces limits so that runaway Apex code or processes don’t monopolize shared resources. If some Apex code exceeds a limit, the associated governor issues a runtime exception that can’t be handled. Please review the Salesforce documentation to learn more about Governor limits.
Run batch Class on load: automatically run batch upon loading of the Planning Board. If not checked, then the batch will only be run when invoked manually (bottom left button in planning view).
Batch SOQL Safety Group size: set to max. 100 in order to comply with Salesforce Governor limits.
Event Object
Object: Select a standard or custom object that you want to display in the planning board.
Display Name Reference: reference to the field whose value will be shown as the name of the event.
A number of parameters on the event object are related to the way 24Planning works with non-working time. Visit the section ‘Defining non-working time’ for more background information on the concepts.
Scheduling Mode: Set to either Duration or Start Date. In case it is set to ‘Duration’, the start and total duration reference are used to display the event on the scheduler. In case it is set to ‘End Date’ mode the start and end reference are used to visualize the event.
Start Date Reference: reference to the field whose value will be used as start date of the event. The Start Date Reference should be of the type Date/Time or Date.
End Date Reference: reference to the field whose value will be used as end date of the event. The End Date Reference should be of the type Date/Time or Date.
Duration Field Reference: An integer field indicating the duration of an event in minutes. Its application varies by mode: in 'Duration' mode, this value is crucial for computing the event's end date; In 'End Date' mode, it's used for scheduling unplanned events that do not have a pre-defined start or end date.
Total Duration Field Reference: This integer field stores the total duration of the event, in minutes, as displayed in the Planning view. This includes both the event's duration and any non-working hours from the defined work schedule that fall within its timeframe.
Background Color Field Reference: reference to the field whose value will be used to select the background color of the Event on the planning board. This should be a text or formula text field where a reference is made to a color defined in the custom metadata (see below).
Text Color Field Reference: reference to the field whose value will be used to select the text color of the event box on the planning board. This field is OBSOLETE as of 24Planning R3.3 where we switched to HSL color schemes in which the text color is determined automatically.
24Planning adopts a so-called HSL color scheme for events. HSL stands for hue, saturation, and lightness and is a cylindrical-coordinate representations of points in an RGB color model. The most common colors are defined as Custom MetaData Types > 24Planning Colors.
Predecessor Reference: lookup field to another record of the event object. The predecessor field allows you to show the relationship between events on the planning board.
Select Percentage Complete Field Reference: allows you define a % completion of an event in the Gantt chart which will be shown visually.
Select Sequence Field Reference: Reference to the field whose value will be used to display the sequence of the event in the Planning view. This should be a number field, representing the sequence of the event.
Select Event Read Only Field Reference: Reference to the field whose value will be used to determine if the event is read only in the Planning view. This should be a Boolean field, representing if the event is read only (applies both to resource planning and Gantt).
Select Event Resizable Field Reference: Reference to the field whose value will be used to determine if the event is resizable in the Planning view. This should be a Boolean field, representing if the event is resizable (applies both to resource planning and Gantt).
Select Event Draggable Field Reference: Reference to the field whose value will be used to determine if the event is draggable in the Planning view. This should be a Boolean field, representing if the event is draggable (applies both to resource planning and Gantt).
Select Event Manually Scheduled Field Reference: Reference to the field whose value will be used to determine if the event is manually scheduled in the Planning view. This should be a Boolean field, representing if the event is manually scheduled, meaning that no automation will apply (applies both to resource planning and Gantt).
Event Filter: The event filter allows you to define filters that hide certain events. Only the events that match the filter are shown on the planning board.
Resource
Resource Reference: list of related objects to the event object, select the appropriate one.
Resource Reference Display Name: defines which attribute of a resource record to show as a display name on the planning board.
Work Schedule Reference work schedule is an optional 24Planning custom object. The Work Schedule is used to define working hours and non-working hours to which the planning applies. Fill in the lookup field from the resource object to the work schedule object. More information on work schedules is available in ‘Step 5 - configure additional objects’.
Filter Resources: define one or more conditions that govern whether a particular resource is part of this datasource. As an example assume that have multiple teams and define a datasource for each team, then you can use the filter resources to only link certain employees to a particular datasource.