ManageAbsenceHandler

start

Here, the starting date of the user's absence is given. Currently, the format is based on the datepicker. However, it can be customized to the datepattern. If you set value manually then value has to look like in the https://tim-doc.atlassian.net/wiki/spaces/eng/pages/228036827 .

${start}

end

Here, the ending date of the user's absence is given. Currently, the format is based on the datepicker. However, it can be customized to the datepattern. If you set value manually then value has to look like in the https://tim-doc.atlassian.net/wiki/spaces/eng/pages/228036827 .

${end}

user

This variable must contain the name or email of the absent user.

${user}

representative

This variable may contain the name or email address of the person who is substituting for the absent user. System then automatically sets this user as a substitute for every process definition, for which the user is responsible.

${representative}

action

If the value “action=remove" is given, system will search for an absence that matches the starting and ending times and then delete it.

takeOverExistingTasks

false

If “takeOverExistingTasks=true" is entered, all existing tasks from this absence will be transferred to the substitute. In order to do this, the HandleActualAbsences timer must be set and running.

datePattern

yyyy-MM-dd

The handler doesn't support date and time without specifying the timezone even though datePattern parameter has default format  yyyy-MM-dd. If the date selection is not made with the datepicker or does not match the https://tim-doc.atlassian.net/wiki/spaces/eng/pages/228036827, is may be adjusted here.

yyyy-MM-dd'T'H:m:sX

you can set to

yyyy-MM-dd'T'H:m:s[.SSS][xxx][xx][X] format specified in