1. Home
  2. Docs
  3. Isimio
  4. Data Model Configuration
  5. About Objects and Fields

About Objects and Fields

Isimio is a scheduling tool that allows you to view records, sorted by date and swimlanes. In order to correctly configure the application, you should first understand the different types of objects and fields, and the minimum required field configuration for an object.

Here is a brief overview of the different scheduling elements:


There are several types of objects:

Scheduled objects are the ones shown inside the scheduler – the ones you want to interact with. These will be cases, opportunities, tasks, etc.

Row objects determine the available swimlanes. For example, if you wish to show cases according to their owning user, you will need to have the User object configured as Row.

Scheduled/Row are objects that serve as both scheduled and row objects. This means you can use them as both a record that shows inside the schedule, as well as a swimlane.

None can be used for objects that you need to load for whatever reason (such as plugins), but should not appear as either scheduled records or swimlane rows.

Field Types

There are also several types of fields:

Start fields represent the date or date/time in which the record is placed. A record’s start date determines the column in which it appears. A single start field is required for every object, and you cannot have multiple start fields for any one object.

End fields represent the date or date/time in which the record finishes. If none is set, it is assumed the record ends at the end of the same calendar date. A single end date field is required for every object, and you cannot have multiple end fields for any one object.

If you do not record end dates in your object, please set your start field to Start/End. This will denote that the same field is to be used as both the start and end date.

Field Attributes

In addition to their type, fields can be tagged with several attributes that determine how the application utilizes them:

Visible fields appear in the box that represents a scheduled record. Although there is no hard limit on the number of visible fields per object, for readability purposes these should be limited to the most important ones.

When a relational field (lookup or master-detail) is marked as Visible, and the swimlanes are set to be the same as the field, the value will not be shown on the record. This is because the value is already shown in the row header.

The start and end date fields are always shown. Marking them as visible will show the value of the field a second time.

Editable fields appear in the edit form when a user double-clicks a record. Note that some field types may not be fully supported for editing, such as Geolocation and Multi-select picklists.

Attribute fields will have the field name and value set as an HTML attribute of the node that represents the record. This can be used to develop CSS rules or Javascript functionality for advanced UI customization.

Show as Tag marks a field to be shown as a circle at the bottom-right corner of the record, next to the warning icons.

Show Label displays the field label before the value. This only works for fields that are marked as Visible.

Was this article helpful to you? Yes No

How can we help?