...
With each import run several changes could be made to the dateset that is imported. Those changes can lead to subsequent changes with the CoreOne Suite Meta Directory. As an example we can take a changes changed last name. The change to the Core Identity should probably be reflected in all connected target systems. To do so certain tasks need to calculate those changes and then provision them. How and if those task tasks should run is defined by the import modes. This page describes the different available modes.
...
Every data record is written to the database immediately (and by its own). The according fast-track tasks are started by the task handler in the Synchronous mode, which means, that the task is not set put into the queue but gets is executed immediately.
| Code Block |
|---|
<TaskMode xmlns="http://schemas.datacontract.org/2004/07/iTsense.Moving.Backend.Common.TaskScheduler">Synchronous</TaskMode> |
...
Standard mode. All imported data records get are written to the database as soon as they are processed by the import (each on its own). There are no fast-track tasks setup, so the changes (for instance resource or role assignments for the newly imported data) will be applied by the according regular tasks.
...
All imported data records get are written to the database as soon as they are processed by the import (each on its own). The according fast-track tasks are collected in bulks of up to bulks of 20 records and are set as bulk-fast-track tasks to the queue by the task-handler.
...
| Code Block |
|---|
iTsense.Moving.Backend.Common.TaskScheduler.TaskMode, iTsense.Moving.Backend.Common |
For that this entry you can set the appropriate mode:
...