# Jobs **The menu item *Jobs* allows you to manage the actions (cron jobs) that JaniWeb automatically executes in the background at certain intervals.** [![Screenshot 27.11.2024 at 16:37:14 PM.png](https://manual.drakos.de/uploads/images/gallery/2024-11/scaled-1680-/screenshot-27-11-2024-um-16-37-14-pm.png)](https://manual.drakos.de/uploads/images/gallery/2024-11/screenshot-27-11-2024-um-16-37-14-pm.png) ## Tab *Definition* The list contains all the jobs that have already been created. Double-click on an entry to change the definition of the job. ### Button *New Job* Press *New Job* to create a new job. Enter the function to be called in the field *Class*. Enter when the task is to be executed in the field *Timing*. For details, see the section [*Time format*](https://manual.drakos.de/link/259#bkmrk-zeitsteuerung-richti) below. ### Button *Start Scheduler* After you have changed an existing job or created a new one, you must restart the scheduler. To do this, press *Start Scheduler*. ## Tab *Protocol* Here you can display a list of the jobs that have been executed. 1. Enter a start time. 2. (Optional) Enter an end time (*To*). 3. (Optional) Select a status to narrow the list. 4. Press *Show executed jobs*. ## Overview of the jobs
**Job****Description**
de.drakos.dbimport.scheduler.SAPRefreshJobImport master data
de.drakos.dbimport.scheduler.AutomaticReportJobSend automated reports
de.drakos.dbimport.scheduler.LicenseUsageCheckerJobCheck license usage
de.drakos.dbimport.scheduler.InactivePersonFinderJobCheck inactive personnel records
de.drakos.dbimport.scheduler.PersonConsolidationJobConsolidate personnel master data import
de.drakos.dbimport.scheduler.BaseSupplyJobMaster data calculation for basic supply
de.drakos.dbimport.scheduler.LicenseHeartbeatJobHeartbeat for pay-per-use license
de.drakos.dbimport.scheduler.FTPMasterRecordJobDormakaba master data distribution
de.drakos.dbimport.scheduler.PegasysAccessRightsCheckerJobCheck Pegasys authorizations
de.drakos.dbimport.scheduler.BookingFileJobExport booking data
de.drakos.dbimport.scheduler.SessionInactivityCheckJobCheck session
de.drakos.dbimport.scheduler.DeletedBookingsFileJobExport deleted bookings
de.drakos.dbimport.scheduler.AbsenceMailReminderJobReminder of absences in workflow
de.drakos.dbimport.scheduler.DeleteOldCEEJobRecordsJobCleanup CCEEJobExecutionProtocol
de.drakos.dbimport.scheduler.QualificationJobCheck permissions based on qualifications
de.drakos.dbimport.scheduler.DBBackupJobBackup database
de.drakos.dbimport.scheduler.ChronBookingJobArchive booking data
de.drakos.dbimport.scheduler.NEDAPBookingsJobNEDAP bookings
de.drakos.dbimport.scheduler.DataProtectionLogicJobData protection audit
## Time format JaniWeb uses the Quartz Cron syntax to define complex job timings. This extended version of the classic Cron syntax consists of six or seven fields: #### Quartz Cron syntax structure ```plaintext S M H DoM MoY DoW [Y] ``` 1. **Second (S)**: `0-59` 2. **Minute (M)**: `0-59` 3. **Hour (H)**: `0-23` 4. **Day of month (DoM)**: `1-31` 5. **Month of year (MoY)**: `1-12` or abbreviations like `JAN, FEB` 6. **Day of week (DoW)**: `1-7` (or `SUN, MON, ...`) 7. **Year (Y)** (optional): `1970-2099` #### Special characters - **`*`: Any value** - ****`,`: List of values (e.g. `MON,WED,FRI`)**** - ******`-`: Area (e.g. `1-5`)****** - ********`/`: Increment (e.g. `0/5` for all 5 units)******** - **********`?`: Any value, which is ignored in fields of conflict (only for `DoM` and `DoW`).******** #### Examples 1. **Every day at midnight**: ```plaintext 0 0 0 * * ? ``` 2. **Every Monday at 9:00 a.m**: ```plaintext 0 0 9 ? * MON ``` 3. **Every 5 minutes**: ```plaintext 0 0/5 * * * ? ``` 4. **On the first day of each month at 12:30 p.m.**: ```plaintext 0 30 12 1 * ? ``` #### Important differences to the classic Cron format - The field **second** is additionally available. - **`?`** replaces **`*`** in fields with conflicts between `DoM` and `DoW`. - Supports more detailed timings by combining steps and lists.