You delegate - tacoss.eTRADE carries out

Auf die Frage "Muss man hier alles selber machen?"  geben wir als Antwort ein klares "Nein". Auf den Ausspruch "Wenn man nicht alles selber macht!"  kontern wir: "Dann macht es tacoss.eTRADE sogar noch effizienter und effektiver."


Are you already using all the automation options that tacoss.eTRADE offers you?


We are continuously developing not only new, but also existing functions. We have currently completely revised the "Job Planner" module. This module helps you to repeat predefined tasks automatically or to work through them at a specific point in time. In this case, you are not delegating your tasks to an employee, but to your application so that you and your employees can concentrate on your core tasks.

1. The planning

Together we discuss what you would like to delegate. We then define an executable function package for you, the so-called "job". This job can have several configuration units, which we call job instances, and which can be executed cyclically.

2. Execution

Each execution of a job instance is stored in the database as a "job instance call". This call cannot be reused and shows the status of the job instance, such as the progress, the start and end time.

3. The supervision

The job monitor provides an overview of the job instance calls that have been carried out. It is a program window that shows all job instance calls. A number of functionalities support you to get a good overview:

Clear coloring

The colors show at first glance the status of the calls and where action may be required.

Logical filters

The sometimes numerous entries can be narrowed down using quick filters. For example, you can filter by job or status, but you can also limit the time.

Intuitive navigation

You can use a context menu to display the configurations of the respective data records.

Flexible update

You can call up a full update at any time by clicking the appropriate button. But intervals for an automatic update can also be defined.

Quick actions

You can carry out actions (e.g. cancel, unlock job instance, lock job) for several data records at the same time.

Individual blocking times

Define on your own at which times a job may not be executed.

Would you like to learn more?