System

Various system parameters are used to shape many of the basic settings in Webdesk. These are parameters that have a direct effect on the functioning and appearance of the different Webdesk modules: Workflow, Groupware, Business Trip, etc. (such as determining the authentication method for users, a path to the welcome logo, determining the first action to be displayed after logging in to Webdesk, etc.)

For monitoring purposes, the log settings can be configured as needed to output specific actions, specific users, or log levels for specific functions. The log levels can be defined in different gradations as needed, such as info, warning, or error message, etc. The logging depth affects performance, as it is quite memory-intensive.
Further monitoring tools are the display of logged-in users, active jobs, or the log entries, which document which jobs ran when and with what success.

To import data into (or export data from) Webdesk, connectors are used. They provide the infrastructure for importing and exporting data. In this way, not only can data from the Time & Attendance system be synchronized, but databases can also be addressed and text files (CSV files) created. This enables interfaces to other systems, and the data from Webdesk can be processed or formatted.

To automate the processing and synchronization of mass data, different jobs are used. They serve as periodically running auxiliary programs for synchronizing department and person data from the Time & Attendance system. Jobs also enable the synchronization of calendar data from the groupware system. Defined irregularities in the Time & Attendance system can be filtered, whereupon certain requests are automatically generated and forwarded to the employees for processing.

To optimize performance and ensure fast access to Webdesk functionality, caches are used as intermediate storage. Reasons for using a cache are (relatively) slow access to a background medium or the relatively high effort of regenerating frequently needed data. The different data can thus be cached in separate caches and are immediately available. Among others, there are caches for user data, temporary access permissions, process definitions, process details, etc.