Not all configuration fits neatly into the available tools. If you want to make the most of your scheduler, you will want to know how to configure objects and fields manually to tweak the system to your liking.
Isimio’s schema configuration is kept in the object Schedule Object, and its child object Schedule Field. Records in these objects tell the scheduler what data to load and how different elements behave. A Schedule Object record tells Isimio to query a particular object from the database. This object can be used as rows, as scheduled records, or it can be loaded for a custom purpose – such as when building a plugin.
When creating a new Schedule Object, the Name field should correspond to the API Name of the object you want to load. This can be a standard Salesforce object like Account or Contact, a custom object like Appointments__c, or an object from a managed package, like kruvi_staff__Shift__c.
Filter contains a SOQL where clause, which will be used when querying data. See the selecting which records to display article for specific instructions and examples.
Load Order controls the order in which objects are queried in the system. The higher the number, the lower the object will be in the load order. While it should not have any effect in normal use, it allows a level of flexibility when developing custom plugins.
Scheduled Record indicates that records from this object should be shown inside the scheduling grid. Use this to mark which object or objects you are actively working with.
Row Record marks which objects can be used as swimlane rows. This object should be a parent object to the object being scheduled, using a lookup or master-detail relationship. For instance, if Task is the scheduled object, User might be the row object.
A single object can be both row and scheduled, although it is not very common.
Default affects scheduled and row objects differently: a default Row object will be shown by default when the scheduler first loads. If you have several row objects, use this checkbox to control what rows are shown to users by default. A default Scheduled object controls which kind of record is created when double-clicking on an empty grid cell, and the first option that appears in the context menu (right-click).
Color Code determines the default border color for all records of this object. This field accepts any CSS-compatible color code, such as “Blue” and “Green”, Hex codes such as #CCCCCC, or RGB codes.
Timezone Field should contain a Salesforce relational path that points to the field that contains the record’s time zone. This field may be on the same object, or on a related object that is also loaded into Isimio. For example, the following path is used to set the time zone from the related place record of a shift record:
This requires the Place object to be loaded into the scheduler, and for the Place__c field from the shift to be configured on the shift object. The Timezone__c field must contain a valid time zone code.
Filter Set allows for the creation of separate schedulers with differing configurations. See Multiple Schedules for details.
Bypass Sharing causes records to be loaded without respect for the org’s sharing model. This allows the schedule to display records the user may not have access to natively. Note that creating and making changes to records still requires the appropriate level of access.
Multinode affects how records are displayed when they span more than a single calendar date. When this option is selected, a new record box will be created under each day spanning the record times. If unselected, then this record will only show on the column representing the start date.
Show Formatted Date/Time controls whether or not the record’s time range is displayed in the record box. This is formatted as <Start Hour>:<Start Minute> – <End Hour>:<End Minute>. For example: 10:30 – 15:45.
Indexed Start/End Field can be used to increase the performance of loading records in the scheduler. Use this if you have a very large database of scheduled records, or if you would like to increase data loading performance. For details, see Indexed Dates.
Row Selectable defines the behavior when a row header is clicked with the mouse. By default, clicking an empty space in a row (outside the actual text) does not do anything – but when this is selected, the row will be visually marked as selected. This has no use in the out-of-box solution, but can be used by plugins to perform actions.
[Beta] Edit in Salesforce UI replaces the standard Isimio record editing form with a Salesforce-generated one. This form uses your existing page layouts and may have different controls for certain field types.