Skip to main content

Job PtmTaSynchronization

Purpose​

The active, configurable job synchronizes daily TA absence times that count as working time, and optionally attendance times, into the PTM time tracking PtmTimeEffort.

Configuration​

  • Days to synchronize into the past (daysBack): The period extends from today minus the configured number of days up to and including today. If the value is missing or negative, the code uses seven days.
  • Groups: If no groups are selected, the job processes all currently valid active persons. If groups are selected, only persons with a TA ID from the union of the selected groups are processed.
  • Also synchronize attendance (alsoSynchronizeAttendanceTime): In addition to mapped absences, the TA attendance is generated as a PTM time effort.
  • Mark as created by system (markAsCreatedBySystem): Marks the generated PTM time efforts as system-generated.
  • Effort mappings: For each TA absence reason or, optionally, the attendance code, the project, activity, customer, billability, and description are configured.

Behavior​

  • Without a TA connector, or if the TA service is not available, the job logs a warning and ends the run.
  • Unmapped absence reasons are not written to PTM. Mapped absence reasons generate approved daily PTM time efforts with the configured mapping.
  • System-generated absence efforts are replaced or removed when changes occur. Manually recorded efforts are retained and, if applicable, reduce the attendance effort to be newly generated.
  • Synchronization takes place per person in a separate transaction. Persons without a TA ID are skipped if they were selected via groups.
  • An empty mapping list generates no entries and ends the job with a warning.

Notes​

Before activating, check the absence reason/attendance mappings, the period, and the system flag. In the case of multiple TA employments, this job processes the TA reference of the respective Webdesk person according to the current TA service.

Last updated on