2019.2

The more items that are present in the database, and the larger they are, the more time and
processing power (CPU) that will be required for cleaning them up. Thus a regular Clean-up of
the database (as often as possible)is recommended.
This is especially the case if items are not going to be retrieved from the database at a later
date. i.e. If the Connect job is not going to be re-run.
The clean-up can always be set to run outside of business hours (see the "Run according to the
cron schedule: Enter the interval at which the Clean-up service runs. To understand how to
write a cron job schedule, please refer to the Quartz Scheduler tutorial." below option below), to
reduce impact upon Production systems.
The values below define when the specified targets are to be set as being ready for deletion,
not when they are actually deleted. The actual deletion occurs only as per the cron job
scheduling; or when PrintShop Mail Connect is started (if Run at application start up is
selected); or when the Run Now button is pressed.
l
Enable clean-up service: Check to enable the Clean-up services. When checked, either
or both of the Database clean-up and File clean-up services can be set individually.
If the box is not checked, then no Clean-up will occur.
l
Run at application start up: Click to start the clean-up service when the Designer
module is opened.
l
Run according to the cron schedule: Enter the interval at which the Clean-up service
runs.
To understand how to write a cron job schedule, please refer to the Quartz Scheduler
tutorial.
Note
If the Product managing the service is set to Designer, then the Designer must be
running at the time that the cron job is scheduled, for the Clean-up to run.
l
Product managing the service: Select which of the applications will run the service.For
PrintShop Mail Connect the Designer is the only choice.
Page 357