New features in version 4.1

General improvements to the user interface

For ibaDatCoordinator v4.1, the user interface has been redesigned in several areas to simplify operation and make configuration more efficient.

Rearrangement of controls

The controls for starting and stopping jobs, as well as for applying and discarding configuration changes, have been standardized within the job view and moved to the top. As a result, these functions are consistently positioned regardless of the context and can be accessed more quickly.

Optimization of selection options

Configurations with a large number of options are now displayed as drop-down lists instead of radio buttons. This improves clarity and makes selection easier.

Before:

Now:

Organization of task settings

The order of the settings within the tasks has been revised. Settings that are rarely used or optional are collapsed by default and can be expanded as needed. This shifts the focus to the key configuration parameters, while additional options remain available.

Naming of jobs and tasks

To improve clarity, the names of jobs and tasks have been standardized in ibaDatCoordinator. You can now find the familiar jobs under the following names:

The tasks are named as follows:

New dialog for adding tasks

The process for adding tasks to a job has been optimized and aligned with the user experience of other iba products. You can now add tasks by clicking the "Add task" link below the job in the job tree. Adding from the job configuration view (by clicking the task icons) is no longer supported. A selection dialog shows the task types permitted for the job type, along with descriptions and licensing information.

For detailed information on the procedure, see Configuring a task.

New task and job types

To make it easier to configure and select the correct job or task type, the following changes have been made:

• The previous "scheduled job" has been split into the scheduled HD job for the cyclical processing of HD store data and the scheduled job for the cyclical processing of tasks that do not require measurement data.

• The former "extraction task" has been divided into the following tasks to accommodate different use cases:

  • Extract to file task: Extracting data into a supported file format

  • Extract to DB task: Extracting data into a supported database

  • Publish to DB task: Extracting only computed columns and info columns into a supported database

The individual job and task types display only the relevant settings in the configuration area.

For more information, see chapter Scheduled HD job and scheduled job, Extract to file task, and Extract to DB task and publish to DB task.

Central email configuration

Until now, email notifications had to be configured individually for each job. Starting with this version, you can configure email accounts centrally in the Settings of ibaDatCoordinator and select them in jobs. Accounts are configured in the same way you are accustomed to with other iba products.

See Settings – Email accounts and Configuring a job.

Additional validation when applying the configuration

To avoid problems caused by incorrect configurations, starting with version 4.1, ibaDatCoodinator performs various validity checks on jobs and tasks and, in addition, checks the following as soon as you save or apply the configuration:

• The analysis files used are available

• The source and target directories are accessible

• Source directories are not used by multiple DAT file jobs

A window displays the validation result:

Additional improvements

Resetting processing flags

If you want to reprocess DAT files that have already been processed, you must remove the markers using the button . Previously, this required specifying the exact folder path as the source path in the job, and the process had to be repeated multiple times if the DAT files were stored in different subdirectories. Starting with ibaDatCoordinator v4.1, the button opens a file browser where you can select one or more folders and files directly from your network.

Limiting the scanned subfolders

Starting with ibaDatCoordinator v4.1, you can limit the scanning of subfolders in the DAT file job. You have two options for this:

• By default, the system scans the last N subfolders to which data was most recently written.

• Alternatively, you can limit the scan to files with specific numerical values in their folder names.

  Example: The folders are organized by year/month/day, e.g., "YYYYMMDD" (flat structure) or "YYYY" – "MM" – "DD" (structure with subfolders). Folder names may only contain numerical values (integers).

  ibaDatCoordinator then treats folders with a higher numerical value as newer.

For detailed information on the settings, see DAT file job – settings.

New option for event jobs

For event jobs, you can now select a fourth option for the Time range: "Range between incoming events".

Other documentation
	For more information, see the ibaDatCoordinator documentation, chapter "Event job – settings".

See Event job – settings.

Visualization of unsaved changes

Starting with ibaDatCoordinator v4.0, changes are initially made only in a local copy of the configuration and are applied to the server only when clicking the button. To make it easier to identify changes to jobs and tasks that have not been applied or are pending, starting with this version, an orange icon will be displayed in the job tree on all affected nodes, extending all the way up to the job types.

Script tasks are disabled by default

For security reasons, the script task is now disabled by default and must be enabled in the settings of ibaDatCoordinator before it can be used for the first time.

See ....

If you have already configured script tasks and are updating to ibaDatCoordinator v4.1, the option is already enabled and you do not need to do anything else.

Optimized signal selection in the Kafka publish and S7 writer tasks

Until now, signals and expressions had to be added individually in the Kafka publish task. Starting with version 4.1, you can select multiple signals at once or adding them from the ibaAnalyzer signal tree using drag & drop.