(Last update of this topic: 12-02-2021)
As of version 6.5 a completely revised database cache for database entries has been implemented.
As a result, various storage and performance problems have been solved.
This cache is maintained via the runtime of the steadyPRINT Center and repeatedly compared with the database during read processes.
The administrator also has the option to perform an update of the database cache and to force a restart of the environment tree via the button "Update tree view" in the ribbon.
Similar scenarios can occur when working with several instances in the steadyPRINT Center.
Example:
Administrator A deletes a printer from the steadyPRINT Center.
Shortly afterwards, administrator B creates an assignment to the same printer as the printer is still available in his user interface.
Administrator B will now receive a message informing him to update his interface or to restart the steadyPRINT Center as the database cache is obsolete.