TA Daily Absence Connector

With this connector, it is possible to export daily absences for a defined selection of persons over a specific period.

Use Cases

  • Export of daily absences to an export file
  • Automatic creation of project time bookings (unproductive project times) based on absences in the time system

Configuring the Connector

  • Parent connector
  • Name
  • Data flow direction:
    Data source
  • Description
  • Time and attendance system:
    Interflex IF6020, Interflex IF6040, or Webdesk time evaluation. This determines which absence reasons are available for selection; when it is changed, the list of absence reasons is cleared.
  • Do not export 0.0 values:
    Only persons and days where at least one account has a value other than 0.0 are exported.
  • One absence reason per page:
    If multiple absence reasons are defined, only one absence reason is shown per person and date in the result. If, for example, 4 absence reasons are defined, there are 4 pages per person and date in the result!
  • Absence reasons
    • Absence reason
    • Column name (prefilled with the name of the absence reason when it is selected)
    • Up and down arrow
    • Delete
  • Persons
  • Groups
  • Clients

Period

The period is specified via the restriction (constraint) of the connector query with the variable referenceDate and date values in the format yyyyMMdd, e.g., referenceDate = '20160119', referenceDate >= '20160101' and referenceDate <= '20160119' or referenceDate between '20160101' and '20160119'. Without a restriction, the values of the previous day are exported. Persons without a taId are ignored.

Fields Provided

  • date, firstName, lastName, taId, employeeId, person, orgUnit
  • total (sum of the hours of all configured absence reasons on the day) and total_duration
  • for each configured absence reason, a field with the specified column name (hours) and a field column name + "_duration" (duration object),
  • or, with One absence reason per page, the fields absenceCode, absenceTimeValue (hours), and absenceTimeValue_duration
Kommentare (0)