Example 1: Search and load calendar

A common use for the 'Set calendar' action is to search for a calendar using a Suchverhalten. It is recommended that calendars are identified by their name, not by their ID, as this can vary from system to system (transfer forms from one system). For this purpose, a behaviour 'loadCalendar' is defined for a date field, which should be called when the form data is loaded. Additionally, the date field activates the option 'Working days only'.

In the search behaviour, the calendar with the static name 'Default calendar' is searched, which is then passed to the action 'Set calendar'.

Result:

Example 2: Dynamic addition of calendar exceptions

The date value Departure date planned of a shipment should be visually displayed in the calendar of the field Departure date actual, and declared as a selectable day independent of the stored calendar.

A calendar called 'Default calendar' already exists in the system and it defines basic holidays and working days.

To implement the example, the date range element Departure date planned is assigned the behaviour 'Changed'. This executes a Client workflow, which determines a calendar instance and passes it on to the Actions on 'true'.

The changed date range is passed to the Client workflow as a variable 'source' (1) (DateTime). The resulting calendar is then written to the variable 'calendar' (2) in the workflow.

As an Action on 'true', 'Set calendar' is executed on the date range element Departure date actual.

In the Client workflow (Rule: Statically true), the calendar with the name 'Default calendar' is searched for and written into the variable 'calendar'.

A new calendar exception is added via the triggering event List item (1). As a little trick, this new instance is immediately processed in an Execute with action to directly access its object fields (2).

The 'Set Value' actions are explained below.

(A) The date for the exception is set to the value of Departure date planned, which was passed to the client workflow as the variable 'source' (see above).

(B) 'Working day' is selected as the exception type, since this date should now be selectable independently of regular working days.

(C) The exception should be highlighted with a green color (decimal code 6487936.

(D) The label is specified as a 'Localized label' instance, through which a resource bundle (E) and name (F) can be defined.

(E) The language administration bundle of the label.

(F) The resource name of the label.

For the date field Departure date actual, the option 'Working days only' was activated, which shows Saturdays and Sundays as non-selectable days due to the default calendar. However, in the result screenshot at the beginning of this example, it becomes clear that the exception overrides this rule because the type of exception is a 'working day'.