Calendars are useful in many different processes. For example:
- Resource scheduling—Using dashboard calendars to assign qualified resources, such as employees or machines, to events that need to be completed within a scheduled timeframe, such as projects or work orders. Learn more in the Resource scheduling configuration overview topic.
- Available and unavailable time—Using calendars set up with work hours and holidays to help estimate things like bank transfers. This time can lapse days, for example from 10:00pm—4:00am.
- Scheduling conflict resolution—Using logic blocks to help with scheduling conflicts, such as find free time slot or aggregate time slots. Logic blocks can help find free time slots across multiple calendars or can aggregate busy time slots if there are multiple meetings or events scheduled in a row.
You can also associate logic blocks to trigger upon event creation, deletion, or updates. Learn more in the Calendar configuration topic.
Events for calendars can be created from the Calendar Definitions application, the Calendar Event Definitions application, or on the calendar itself if it isn't set to Read Only. Read Only calendars are rendered with a icon in the calendar name. These events can be configured to send out reminder emails, have records attached to them, or to recur at different intervals. Learn more in the Calendar Event Definition application topic.
Calendar configuration
Configure calendars using the Calendar Definitions application, Data Item Definitions application, and the applications you want the calendar to show in.
Calendar Definitions
In the Calendar Definitions application, create your calendar. There are many optional configurations, such as:
- On the Settings page, you can:
- Subscribe your calendar to other calendars. This allows the calendar to see events from multiple calendars in one location.
- Reference a table which holds auxiliary event data for events in the calendar.
- In the Triggers section, associate logic blocks to activate upon event creation, deletion, or update.
Data Item Definitions
In the Data Item Definitions application, you must create a Calendar type data item. This data item holds the calendar once data mappings, application settings, logic blocks, or Field Dependencies in the application tell the Calendar data item which calendar to display.
On the Settings page, select the display options for your calendar.
Table Definitions
In the Table Definitions application, add your Calendar data item to the table your application is built over.
Application Builder
In the Application Builder, add your Calendar data item where you want the calendar placed in the application.
Optionally, in the Field Dependencies section of the Configuration panel, you can change default data item settings like the calendar start date, or select which calendar you want shown in the Calendar data item. To select the calendar you want displayed with field dependencies, you must:
- Select the name of the calendar definition or a table lookup on the calendar definition in the Controlling Field.
- Select the
Calendardata item in the Dependent Field. This populate the user interface for the calendar. This data item must be created before you can show the calendar in an application.
Optionally, in the Events Action section of the Configuration panel, you can configure an even action to update the application's business records when calendar events are changed. Learn more in Attach logic to calendar event changes.
Events
You can add events to your calendar in multiple ways, such as:
- In the Calendar Event Definitions application, create a new record.
- In the Calendar Definitions application, on the Viewer page.
- In the application, on the calendar.
Learn more in the Calendars topic and Calendar Event Definition application topic.
Attach logic to calendar event changes
Use logic blocks and events actions in the Application Builder to update business records when changes are made to calendar events.
Prerequisites
You must already have a Calendar data item created and added to your application, and the data item must point to your calendar definition. Learn more in Calendar configuration.
Logic Block Builder
In the Logic Block Builder, configure a logic block with your required business logic.
If the event action you configure in the Application Builder is a calendar event, the logic block must be built over the CalendarEventDefinitions table.
If the event action is any other type of event, such as a Field Value Changed, the logic block must be built over the table your application is built over.
Application Builder
In the Application Builder, in the Configuration panel, in the Event Actions section, you must:
- Create an event action. The type of event you select determines what data source is passed to your logic block, such as:
- Calendar events—Your logic block is initiated by user interaction with the calendar, and can review specific details of the event. For example, the data source for a
Calendar Event Updatedevent would be a calendar event record which holds information such as the time slot, event name, and description. - Other events—Your logic block is initiated by user interaction with the business record, including with the calendar, but does not contain details of the calendar event. For example, the data source for a
Field Value Changedevent would be the business record which doesn't hold any information about the calendar events.
- Calendar events—Your logic block is initiated by user interaction with the calendar, and can review specific details of the event. For example, the data source for a
- In the Field Name field, enter the name of your
Calendardata item. - In the Action field, enter the name of your logic block.
Learn more in Logic blocks and event actions.
Calendar Definitions application
Use the Calendar Definitions application to create, modify, and view calendars, or to access the calendar view to schedule events.
Calendars may be configured and associated with any application in Nextworld, or integrated with outside applications.
Learn more in the Calendar configuration topic and the Calendars topic.
General page
You must define your product module and family. You can also include specification information about the purpose of the calendar.
Settings
On the Settings page, you can:
- Define calendars you want your calendar to subscribe to. Calendars which subscribe to other calendars show all events created on those calendars in addition to their own events.
- Reference auxiliary event data.
- Define triggers for calendars. These logic blocks can be set up to activate upon an event creation, deletion, or update. There are several uses for this, such as:
- Alerts—Logic blocks can send out emails to recipients.
- Integration with external applications—Logic blocks can make external callouts to outside applications, like Outlook, to sync those calendars with Nextworld calendars.
- Linking other data—Logic blocks can create records associated with the event. For example, if an event is created on a work order calendar, a work order record can be automatically created and associated with the event.
Viewer page
Use to preview the calendar and events. This can also be done in the Calendars application.
Calendar Event Definition application
Use the Calendar Event Definition application to create and modify events for calendars.
There are multiple types of events, such as:
To-Do—Schedules an event on the specified day without a time slot designated.Event—Schedules an event on the specified day with a time slot designated.Available Time—Schedules a time block where events can be placed. These time blocks can lapse days, for example from 10pm-4am. They can also recur.Unavailable Time—Schedules an unavailable time slot where events can't be placed. Unavailable time also automatically fills in areas outside of available time slots for either the rest of the day, or until the next available time is scheduled.
Details page
Define details of the event, such as start date, time zone, or associated records. You can also select the Busy checkbox, notifying logic blocks and users not to schedule during that event time.
Recurrence page
Configure events to recur. There are a multitude of recurrence options available. For example, you could create a recurrent event on the third Tuesday of every second month, or could set an event to recur daily for twelve days.
Properties page
Define extended properties for the event, such as associating a data item for color.