I love VisualCron because we previously spent a lot of time writing Power switches to connect to SQL Server. VisualCron makes it easier to execute services or connect to FileZilla by only adding the credentials to the master credentials stored in the solution. 

The most valuable feature of VisualCron is its ability to schedule interactive jobs so that you can have interdependencies within the job and interdependencies of a job on another job, and so on. VisualCron also has the ability to run PowerShell commands through the jobs.

What I like about VisualCron is that like its name, it's a very visual tool. In my previous company, there were a lot of scripts for all kinds of services, and through VisualCron, you get to group all flows and get a nice visual overview. VisualCron also has an alerting feature, so you receive alerts from it.  VisualCron makes everything clearer and easier to maintain.

Every other solution that I was looking for almost always needed a programmer, but with VisualCron, you can do what you need to do without programming skills, so this is another valuable feature of the tool.

This tool actually is meant for scheduling purposes. If I have to execute a task that needs to be executed on a daily basis at night, at 10:00 PM, for example, it can perform some tasks at a specific time based on our configuration.

If I want to send some files to a specific location, to some specific client, and then, after, if I want to send an email to that client that I have uploaded the file to their particular location, just to notify them, I can do that using this product. We can do some configuration in the VisualCron tool. We can create a job and in the job, we can define some tasks, for example, task one, task two, and task three, and they will follow some order and process. Based on that order and process, we can configure when the job should be executed, whether it's at night, at 10:00 PM every day or after five minutes every day, or whatever we require.

There are lots of options for configuration.

The application itself has many features.

It supports a lot of plugins. 

We don't have to do any coding. We just plug and play and it works.

Simplicity is the most valuable feature. You just use the tool. Some preferences and permissions are not quite self-explanatory, but those are rather advanced features. Our internal customers are able to perform their tasks without our assistance.

What I found most beneficial from VisualCron is that you can directly connect it with different databases, user accounts, and credentials. You can run queries from one machine to another using the credentials, unlike  PowerShell, that's run by the machine itself. With VisualCron, you can directly ask other machines and run requests through user credentials.

Suppose you have an AWS or Azure environment. In that case, you can maintain the connection between on-premises and cloud-based machines, which is the type of setup in the organization I'm working for. You can directly call some of the services via VisualCron on your local on-premises machine, and I found that an excellent feature of the tool.

• Post-sales support: I've only had a few cases where I've had to request support in the past 12 years of use, but the support response time and resolution were was extremely quick.
  
  
• Ability to use job variables within a job. This allows us to make reusable job templates for similar activities and just update the job variables associated with the new instance.
  
  
• Branching logic and conditional execution of tasks within a job.

• Logging and ability to send error alerts on job failure to appropriate IT and/or business contacts.

The Database, Process and File tasks are probably the most used task types for our operation. A lot of these powerful tasks are used in a single job, taking on a workflow that formerly required multiple systems, third party components, and/or software programs to assemble a complete process. VisualCronv is currently handling so many different critical processes for our company, it's become a key factor in our livelihood and success. This tool has also sparked a lot of innovation from our analysts and developers.

Mail trigger: When a mail is delivered into a specific inbox, you can fire off your task depending on this.

Event trigger: When a file is placed in a certain folder, you fire off your task depending on this.

There are a lot of tasks that you can use for all kinds of stuff. 

It's very useful to use variables which help you to specify some jobs.

The forum is very useful.

Nightly sync tasks.