Jobs in the Travel Module

Jobs serve as periodically running utility programs for the synchronization and processing of data.
They can be used in many ways and make it possible, for example, to create groups based on certain criteria, to synchronize department and person data from the time management system or to synchronize calendar data from the groupware system.
In addition, certain jobs can be used to filter defined irregularities in the time management system, whereupon certain requests are generated automatically and forwarded to the employees for processing.

Jobs in the Travel module:

• Migrate WD2 Travels
  This job imports travel data from Webdesk2
• Import Euro FXExchange Rates From ECB
  This job imports the euro exchange rates defined by the European Central Bank.
• Import Exchange Rates Via YQL
  This job makes it possible to import various euro exchange rates using Yahoo Query Language.

Other jobs

• Job autoCreateTravelFolders
  Creates travel folders for the current month for selected persons and starts the travel workflow.
• Job TmCleanupRecordAttachmentDraftsJob
  Deletes temporary record special attachment drafts older than 24 hours.
• Job TmShrinkImagesAttachedToTravelsJob
  Reduces the size of images in travel attachments.
• Job importExchangeRates
  Imports exchange rates via configured providers.

The jobs can be started automatically with the help of a so-called trigger. The trigger creates a schedule so that the jobs can be started as desired (hourly, daily, weekly or monthly, ...). The setting can be configured down to the exact day, hour and minute.
If needed, the jobs can also be started manually at any time.
In addition, jobs can have an active or inactive status. With an active status, the jobs are started according to the configured trigger. If they are inactive, however, they can only be started manually. The status can be changed at any time.

Jobs can be monitored via the "Active jobs" view, where all active jobs can be seen at a glance. In addition, with appropriate configuration, the history of the job can be traced using the log entries. Based on the configured log level (defined status during the job run, such as error, warning, ...), it becomes apparent whether a job ran without problems or whether certain problems occurred.
If needed, email delivery can also be configured here. The email is sent to a defined person if a log entry with a specified level exists.