Likelihood to Recommend Any large business or organisation that wants to manage their workload effectively and with the least amount of room for error might choose the ActiveBatch Automation tool. Being a consultant I feel that It aids in task automation and has the flexibility to change in response to varying company requirements. It helps to save huge time by doing all the repetitive tasks on daily basis. During the patching activity the schedulers can be stopped. It also help by alerting us if any system/job is down so that SLA can be saved. Overall ActiveBatch Automation stands as a dependable cornerstone for ensuring the seamless operation of our tasks.
Read full review Originally we used it as a guide for a workflow and it was amazing. As I stated earlier, we currently use it to decimate status based on tasks, great. We tried to use it as more of a Project Management platform and it wasn't really the best, but it isn't made for that either. Then again, using
Microsoft Project can be linked to it to communicate the milestones.
Read full review Pros Businesses can use ActiveBatch to plan tasks based on parameters like frequency, dependencies, and the time of day. By automating typical actions like backups and data transfers, businesses can make sure that crucial operations go off without a hitch. Multiple systems and apps can be used in complicated workflows that ActiveBatch can automate. For instance, it can automate a workflow for processing orders from beginning to end, from the customer order through inventory control and delivery through the processing of invoices and payments. Files can be sent between many platforms and systems safely with ActiveBatch. Transfers to cloud-based storage systems like Amazon S3 and Microsoft Azure are also included in this. SFTP and FTP transfers are also included. Read full review Ease of use for both end users and administrators Limitless workflow development to automate processes Flexibility to integrate with other software platforms Read full review Cons On RARE occasions, have seen scheduling properties changed that don't take effect. Simpler to understand/more robust reporting options would be nice to have. Maybe I'm missing something, but why doesn't the Instances view show completion time? Just execution time and duration. Read full review Reporting - If reporting is important, you may consider another platform like Tableau which can be fed from Agiloft Sorry, just reporting Read full review Usability We can easily add new plans/jobs in our batch schedules. Also, coordination with reporting and QA jobs is simple to do. Building schedules, restarting jobs, triggering dependencies is easy to understand. The system is very stable and allows us to easily see overall processing times.
Read full review As with our brains, we only use 10% of its capability. It can be as complex as you want it to be or as simple. The training requirements to use it have been minimal depending on the application. This is really a reflection as to how the workflow was configured
Read full review Support Rating My colleague contacted them directly, I only know hearsay on this but it was not good.
Read full review We have enlisted the help of Agiloft support on various occasions and it has been excellent. You work with an individual that understands your workflow and will help you figure out how to make corrections
Read full review Alternatives Considered The workload automation solution is based on the specific needs of an organization, as well as the features, capabilities, and costs of various solutions. A thorough evaluation process and consideration of these factors can help ensure the selection of a solution that aligns with overall business objectives and meets the specific needs of the organization.
Read full review We evaluated a couple of products and found that they were either unable to create the workflow that we needed and lacked support. But to be fair, we evaluated the previous generation of Intellect.
Read full review Return on Investment I have not run numbers to determine hard impact, but a quick estimate is that at least one job is running for a average of about 6 hours per day - that 6 hours, if done by hand, would equate to about 30 - 40 hours per day (and in some cases, could not be duplicated manually, as the job repeats faster than a person could accomplish one cycle.) Read full review Agiloft has streamlined the requisitioning process and eliminated manual effort and repetitive low-value tasks. We now have a single source of truth for our SOC audits. Read full review ScreenShots Agiloft Custom Workflow/BPM Screenshots