Technical actions of the todo4teams instance can be triggered in the control center. Again, only experienced administrators should work here. For example, the creation of the full-text index can take several days for installations with several million tickets.

The control center is divided into the two tabs "Messages and Actions" and "User events":

Messages and Actions

This tab is divided into the following areas:

1. Message

1. Server actions

1. Anonymize Ticket

1. Refresh cache

These are briefly described here:

Messages
With this function, messages can be sent to all todo4teams users. This can be helpful, for example, before a shutdown for maintenance work, etc.

Server actions
Various actions can be triggered directly on the server here:

1. Send User Report: The standard todo4teams report, which is usually triggered at the beginning of the month, can be triggered manually here.

1. Backup Scripts: The customer's scripts and forms are backed up separately

1. Log out all users: All todo4teams users are logged out

1. Clean memory: The garbage collection of the Java runtime environment is triggered

1. Rebuild fulltext index: The todo4teams full-text index is recreated. (Warning: This takes a very long time depending on the number of tickets!)

1. Reload CustomJars: The customer-specific extensions are reloaded at runtime

Anonymize Ticket
By entering the ticket ID, all data of the ticket, including attachments and forms, can be deleted here. Warning: The data is then irretrievably lost.

Update cache
The most important business objects of todo4teams are kept in specially optimized caches. These can be updated by loading the data from the database, for example if authorized administrators have made changes to the database directly.

User events

Events stored by the system can be analyzed for debugging purposes.