Technical Lead - Database Administrator at SMART ENERGY SYSTEMS LLC
Real User
Top 10
2023-01-26T15:49:42Z
Jan 26, 2023
VisualCron needs a community forum. To use VisualCron, you need to understand various use cases, so it would be helpful if they had an active user community where we could post questions and get answers.
I want to improve the UI in VisualCron, as it's not as user-friendly, particularly when setting up the task scheduler. If you're familiar with the tool, then no problem, but if not, you'll have a problem typing text because sometimes, the cursor points to other places, so there's an issue with text box alignment in VisualCron. That was painful for me when I was just a VisualCron novice, but when you become used to it, there won't be a problem. An additional feature I'd like VisualCron to have in its next release is CI/CD support, though my organization uses GitHub for it. It'll be a plus point for VisualCron if it can support CI/CD and have GitHub features for DevOps that it currently doesn't have.
IT Application Project Manager at a non-profit with 1,001-5,000 employees
Real User
2022-10-06T08:41:07Z
Oct 6, 2022
An area for improvement in VisualCron is its cluttered interface. It isn't always easy to find all functionalities, so what VisualCron needs is a user interface expert who can improve the interface. There's a learning curve in terms of finding what you need from the interface of VisualCron. The technical support for VisualCron also needs improvement in terms of response time. Currently, there's no live support or hotline you can call to get quick answers, so this is what I'd like to see in the next version of VisualCron. A less cluttered and more streamlined interface, where you don't need to hunt for some of the features, is also what I'd like to see in the next VisualCron update.
The only problem I face when I use the tool is that it doesn't contain much documentation or it doesn't have many video tutorials on its features. That means I have to explore it by looking into the tool. I find all the features by myself, as there is not much good documentation to help me. I have to explore everything from a scratch. It's not that easy to set up.
Director of IT at a recruiting/HR firm with 51-200 employees
Real User
2020-06-04T17:19:00Z
Jun 4, 2020
VisualCron seems to operate like an efficient machine when it comes to improvements and enhancements and new features. I always appreciate the quick response I get when bringing up an issue or coming up with suggestions. I've mentioned before that it would be great to see a move away from SQLCE and XML configuration files. VisualCron support was lightning quick starting a response to this suggestion by allowing configuration of the location of log data, so I'm sure a move to persist everything to any version of SQL Server is close.
Sr. IT ERP Specialist at a pharma/biotech company with 1,001-5,000 employees
Real User
2020-05-28T16:11:00Z
May 28, 2020
I would like for VisualCron to expand audit log to show who changed job variables that are initialized per job run. Add additional security to control visibility and/or modification of jobs to different roles or persons. This would allow the shared use of a common server while avoiding accidental changes to jobs by persons who shouldn't be able to maintain them.
There are some conditions in the mail trigger, but you can only use them as an "AND" condition, not as an "OR" condition. This is an improvement that could be useful. For example, some people put "invoice" in the subject and others put "invoice" in the body. If I want to make a trigger for everybody whose sending invoices, I have to make two jobs for this now.
Product Owner Insight & Analytics Platform at Otto (GmbH & Co KG)
Real User
2020-05-13T15:31:00Z
May 13, 2020
The guys work very hard and that amazes us with every major release. Our suggestion to make it better and more manageable in terms of GDPR: Implement it in a very partnership way.
The error timeout and info could be better. When making web request calls, it will time out sometimes and we won't get any useful info out of the error response.
VisualCron automates tasks like file encryption, scheduling SQL jobs, system integration, data workflow management, and application triggering, making it ideal for handling nightly syncs, FTP server file replacements, job scheduling, and invoice processing.
VisualCron provides an efficient automation solution with features like error and status reporting, API connections, PGP key generation, encryption file creation, and bulk SQL script execution. It simplifies task automation through...
The documentation is a bit weak. The tool must provide a better set of documentation.
VisualCron's command console is a little bit difficult to understand and needs to improve.
VisualCron needs a community forum. To use VisualCron, you need to understand various use cases, so it would be helpful if they had an active user community where we could post questions and get answers.
I want to improve the UI in VisualCron, as it's not as user-friendly, particularly when setting up the task scheduler. If you're familiar with the tool, then no problem, but if not, you'll have a problem typing text because sometimes, the cursor points to other places, so there's an issue with text box alignment in VisualCron. That was painful for me when I was just a VisualCron novice, but when you become used to it, there won't be a problem. An additional feature I'd like VisualCron to have in its next release is CI/CD support, though my organization uses GitHub for it. It'll be a plus point for VisualCron if it can support CI/CD and have GitHub features for DevOps that it currently doesn't have.
An area for improvement in VisualCron is its cluttered interface. It isn't always easy to find all functionalities, so what VisualCron needs is a user interface expert who can improve the interface. There's a learning curve in terms of finding what you need from the interface of VisualCron. The technical support for VisualCron also needs improvement in terms of response time. Currently, there's no live support or hotline you can call to get quick answers, so this is what I'd like to see in the next version of VisualCron. A less cluttered and more streamlined interface, where you don't need to hunt for some of the features, is also what I'd like to see in the next VisualCron update.
The only problem I face when I use the tool is that it doesn't contain much documentation or it doesn't have many video tutorials on its features. That means I have to explore it by looking into the tool. I find all the features by myself, as there is not much good documentation to help me. I have to explore everything from a scratch. It's not that easy to set up.
VisualCron seems to operate like an efficient machine when it comes to improvements and enhancements and new features. I always appreciate the quick response I get when bringing up an issue or coming up with suggestions. I've mentioned before that it would be great to see a move away from SQLCE and XML configuration files. VisualCron support was lightning quick starting a response to this suggestion by allowing configuration of the location of log data, so I'm sure a move to persist everything to any version of SQL Server is close.
I would like for VisualCron to expand audit log to show who changed job variables that are initialized per job run. Add additional security to control visibility and/or modification of jobs to different roles or persons. This would allow the shared use of a common server while avoiding accidental changes to jobs by persons who shouldn't be able to maintain them.
There are some conditions in the mail trigger, but you can only use them as an "AND" condition, not as an "OR" condition. This is an improvement that could be useful. For example, some people put "invoice" in the subject and others put "invoice" in the body. If I want to make a trigger for everybody whose sending invoices, I have to make two jobs for this now.
The guys work very hard and that amazes us with every major release. Our suggestion to make it better and more manageable in terms of GDPR: Implement it in a very partnership way.
The error timeout and info could be better. When making web request calls, it will time out sometimes and we won't get any useful info out of the error response.