| Features |
| |
| |
| VisualCron - automation tool ans task scheduler |
| VisualCron is a
Task scheduler and automation tool for Windows. VisualCron has been around since
2004 and has thousands of customers all over the world. |
|
 |
no programming or scripting skills are needed |
 |
built-in Tasks for all needs which lets you automate everything in one
application |
 |
intuitive interface for designing Jobs and Tasks |
 |
automate tedious and repetitive Tasks |
 |
eliminate human errors |
 |
handle, react and notify on system problems, data error etc. |
|
|
|
|
| |
| |
| Client/Server architecture |
 |
| VisualCron
uses a client/server architecture. The architecture of VisualCron components are designed to create a fast and
secure connection between each instance. You are able to use the API in your own
applications to exchange information with VisualCron. |
|
 |
the
VisualCron Client is used for configuring the VisualCron Server |
 |
the
VisualCron Tray Client notifies you in the desktop when Jobs start/stop. It also
acts as an agent for Foreground execution mode. |
 | the
VisualCron Client and VisualCron Tray Client are both utilizing the
VisualCron
API. The API provides a way for the clients to configure and control the
VisualCron Server. The API itself can be used with your own applications to read
and execute against the VisualCron Server. |
 |
the
VisualCron Server performs the actual Execution of Jobs and Tasks.
The Server runs in the background as a Windows service - no need to login to
desktop. |
 |
connect unlimited clients at once to a Server |
 |
control VisualCron securely locally or across
Internet |
|
|
|
| |
| |
| Jobs - placeholder of Tasks |
| A Job
is a container or placeholder for one or more Tasks. In the
Job you set Triggers - which control when the
Job should be started. |
|
 |
a Job can contains one or more Tasks which can be set to run in order or in
parallel |
 |
the Job can be set to run once, randomly or if missed - run once at start |
 |
it is possible to export/import Jobs across Servers, by file or drag'n drop |
 |
Jobs are updated in real-time in the VisualCron Client interface |
 |
a timeout can be set on a Job to stop it after a
certain time |
 |
control if Job should start even though it is
running or not |
|
|
|
|
| |
| |
| Tasks - gets the work done |
 |
| Tasks are created in Jobs. A Task performs a specific action in the
local or remote system. These could be related to file operations, encryption,
transfer, printing and all other actions that you may want to automate in your
system. |
|
 |
130+ Tasks - see this page for all
Tasks |
 |
the
VisualCron Tray Client notifies you in the desktop when Jobs start/stop. It also
acts as an agent for Foreground execution mode. |
 | the
VisualCron Client and VisualCron Tray Client are both utilizing the
VisualCron
API. The API provides a way for the clients to configure and control the
VisualCron Server. The API itself can be used with your own applications to read
and execute against the VisualCron Server. |
 |
the
VisualCron Server performs the actual Execution of Jobs and Tasks.
The Server runs in the background as a Windows service - no need to login to
desktop. |
 |
connect unlimited clients at once to a Server |
 |
control VisualCron securely locally or across
Internet |
|
|
|
|