Minimal configuration

...

When creating a context only the StartDate is required. The end date widget will automatically be set by the widget end date based on the current view.

...

Once you have placed the scheduler widget inside a page with the scheduler context you can start defining some views.

You must lin fill in the context StartDate and EndDate here and define at least one view.

...

You For now, you can choose one of the default views for now , or read up on how to define views in depth here. For now only Only a unique view id and a name for the view is are required, for now.

Adding resources

...

Resources are shown on the left of the widget and for each resource a new row is created. For now only Only a resource datasource data source and the resource id attribute (must be unique!) are required for now. Defining the content of your resources can be done with regular Mendix widgets.

...

Multiple event data sources are supported. This is convenient when you want to use different event entities or if you have vastly different requirements for your various events in the scheduler. For now, let’s just define a single event data source.

...

The required attributes are a data source, a resource id, and a start and end date , if the event is movable and if it’s resizable.

...

Finally, we want to define the actions to call when a user interacts with an event. For the double click action all actions are supported All actions are supported for double-click action, and the scheduler context and event will be passed as a an object parameter. There is however a little more to it for the on-change action.

Creating an on-change microflow

...

In the example above you can see a sample on of changed microflow. You can see that the SchedulerContext, as well as the Event objects, are input parameters. The Event is never changed by the scheduler but it can however be used to search for the event in the database like so:

...