The scheduler portlet allows the user to easily schedule, display and edit appointments or tasks. It can be in different time views; day, week, month, timeline or agenda and can be grouped horizontally and vertically.

The scheduler is based on three tables; Resource, Task and Assignment, where the Resource is the who or where the Task is the what and the Assignment is the connection of the Resource and Task. A resource can be a person who is to perform a specific task, or the resource can be a room in which a meeting (the task) is to take place.

The time standard expected by the scheduler depends on the setting in Time offset.


General data is required for all portlets.

General configuration

Advanced settings

  • Read only: Check this box if the scheduler should be read-only, ie it should not be possible to move or resize tasks.

  • Initialize load: Check if the portlet should be populated with data directly.

  • Views: Select which time views should be available to the end user

  • Default view: Select view to be the default to the end user

  • Slots count: sets the slots shown within each time interval

  • Interval (in minutes): Sets the time interval used in the scheduler

  • Start day of the week: Defines the start day of the week for the user. 0 = Sunday, 1 = Monday etc.

  • Work start: Defines the time work starts

  • Work end: Defines the time work ends

  • Resource column alignment: The resource column text can be configured to be left, center or right aligned


The portlet can listen to the following events:

  • On Filter

  • On Row Selection

  • On Refresh

The portlet can send the following events:

  • On Row Selection

  • On Refresh

Listeners configuration


The portlet data source configuration enables the portlet to execute specified queries towards the chosen database connector to fetch data, or fetch data from a workflow.

  • Database: uses a flow connector to retrieve data from a database

  • Workflow: runs a workflow to retrieve data

Data source configuration

Workflow source configuration


  • Task id: The id of the task

  • Title: The title of the task

  • Start date: The start date of the task

  • End date: The end date of the task

  • Task color:

Data source columns

Set the display name and type for all the columns. As default the variable name will be used and all columns will be visible.

Manage: the columns can also be configured in a grid view for a better overview.

Value in Presentation must be filled in before data source columns can be configured.

Click Execute in the data source section to fetch the columns. Each column can be configured with:

  • display name

  • column type

There are a number of column types to choose from. The default column type is text.

  • Text: use to display column as a text fields

  • Number: use for number fields where the number is an integer

  • Decimal: use for numbers with decimals

  • Date: will display the column as a date with no time

  • Date & Time: use to display date and time


  • Resource id: The id of the resource

  • Title: The name of the resource


  • Assignment id: The id of the assignment

  • Resource id: The id of the resource that is connected to the assignment

  • Task id: The id of the task connected to the assignment


Information about InputTable and action-specific input parameters used in the interaction workflows can be found here: Input Data.


Create workflow: Add the workflow which is to be executed when a new task is created.

Drag and drop

Drag and drop workflow: Add the workflow which is to be executed when a task is moved to a new time.

Double click

Double-click workflow: Add the workflow which is to be executed when the user double-clicks on a task.

Resize task

Resize task: Add the workflow which is to be executed when a task is resized, ie the task size is reduced or extended but not moved.

Custom buttons

See custom buttons.


Resource color

Click Add to configure specific colors rule conditions for the resources.

Task color rule

Click Add to configure color rule conditions for the tasks.

Limitations and recommendations

  • To keep performance as good as possible, it is advised not to display more than 50 resources and 1000 tasks.

Last updated