...

Input and output parameters

In case you want to retrieve the list of the vacation days externally, a second function is present which has on additional paremter for setting these.

Limitations in use

This function iterates through each date in the future until it finds a date which is the correct number of working days distanced. This means that it takes longer to compute the further away the date is. As most use cases concern numbers <=20, this should not be a problem. We want to discourage the use above 100 days due to performance reasons.

Possibilities for customization or extensions

Working on these days of the week

You can set which days in the week count as working days. Each workday is defined as static instance. For example:

...

For the numbering of days, see: Date and Time functions#DAYOFWEEK

Setting holiday dates

You can also set which days count as holidays. For this the static instance DutchVacationDays can be edited (and/or renamed).

...

It is no problem to add dates which are also on a non-working week day. By default, all vacation days of the second half of 2018, and of complete 2019 are added, and you extend this to the future as far as needed.

Other extensions

You could theoretically extend this function to also take vacations of specific employees into account. You would then need to add a new parameter with a user ID, and then add an additional check to the CheckDateValid flow. You would need to connect to a system which stores vacation days, and then add a similar check on a new condition node.

...