TA AbsenceEntryConnector

The TaAbsenceEntry connector transfers all absences that are stored in the absence file. This only applies to full-day absences and time corrections into the future.
In this way, information is provided on whether an employee booked a certain absence reason on a day.
The absence reasons can be configured individually, as can specific persons, groups, or clients.

The connector can be configured with the data flow direction Data source (export of absences from the Time & Attendance system, as described below) or Data sink (import of absences into the Time & Attendance system, see "Connector as a data sink"). If not specified, it is used as a data source.

Configuration Options

  • Time and attendance system: Interflex IF6020, Interflex IF6040, or Webdesk time evaluation. This determines which absence reasons are available for selection in the configuration.
  • Additional fields with user information (e.g., user ID, name, org unit, etc.)
  • Period: days into the future, days into the past
  • Approved / unapproved absences, etc. (if neither of the two options is set, only approved absences are delivered)
  • At least one entry per day: one record is delivered per day (toDate then remains empty). In addition, the options Also create entries for days without an absence entry and Number of booking intervals per day (provides the fields noOfBookingIntervals and hasBookings) can be set.
  • Transfer absences month by month: Absences extending beyond a month end are delivered in 2 records (e.g., 27.03. - 05.04. as 27.03. - 31.03. and 01.04. - 05.04.).
  • No open-ended absence reason for today
  • Absence reasons: Restriction to selected absence reasons
  • Persons, groups, clients

Fields Provided

Fields

Explanation

employeeId

Personnel number of the person whose absence record is delivered.

firstName

First name of the person

lastName

Last name of the person

orgUnit

Organizational unit
(orgService.getPersonsHierarchicalgroup().getShortName())

person

Person object. The complete PoPerson object is passed here, so that the individual properties of the object can then be accessed with JavaScript.

absenceCode

Absence reason code (ta_absencecode_fd_XXX)

absenceShortDescr

Absence reason abbreviation (e.g., U, DR...)

absenceBookingType

Absence reason type from TaCalendarTimeRangeEvent.bookingType

fromDate

from date as java.util.Date

toDate

to date as java.util.Date
(only if per day = false)

fromTime

Time from as java.util.Date
(empty if full-day!)

toTime

Time to as java.util.Date
(empty if full-day!)

approved

approved (1 = approved, 0 = not approved)

dateEmployeeId

An artificial 'unique' key composed of the day in the format ddMMyyyy and the personnel number of the person

noOfBookingIntervals

Number of booking intervals on the day
(only with "Number of booking intervals per day")

hasBookings

1 if booking intervals exist on the day, otherwise 0
(only with "Number of booking intervals per day")

Connector as a Data Sink

As a data sink, the connector enters absences from an external system into the selected Time & Attendance system or cancels them. Expected fields: employeeId (personnel number), absenceCode (absence abbreviation of the source), date or fromDate/toDate, optionally absenceReason (description) and cancel (cancellation).

  • One record per day: a record applies to one day (field date); otherwise it applies to a period from - to (both inclusive).
  • Use priority for conflict resolution: Absence reasons with lower priority are overwritten by absence reasons with higher priority (0 = highest priority).
  • Emails about unresolvable conflicts (default: on): in case of an unresolvable conflict, an email is sent to the employee; the subject, text, and headings of the email are configurable.
  • Allow repetition of entries: Entries that match an existing entry in absence reason and period are ignored.
  • Delete complete absences only: Cancellation entries are only accepted if they correspond exactly to an existing absence.
  • Comment to enter (default: Import): Comment that is entered for all imported absences.
  • Mapping of absence abbreviations to absence reasons: Absence abbreviation of the source, TA absence reason, and, if applicable, priority. Records with an unmapped abbreviation are ignored.
Kommentare (0)