Overall Satisfaction with ActiveBatch
ActiveBatch usage in the company has expended extensively from its v4 days when it hosted just 6 jobs. Now, with over two thousand jobs and dozens of workflows, it touches and does processes for just about every department within the company; claims, sales, I.T., finance, H.R., and now the mainframe. It allowed us to set standards for how users write jobs and security of the systems. With the addition of the web server component, end-users can access the system via the web GUI instead of providing them server console access. In training the users, we set forth policies for how to write/use code/elements of the system so that others, not familiar with the system, can quickly identify where issues are and target their efforts in those jobs. After our security audit, use of the ActiveBatch increased since it hooks into our encryption software....well, it hooks into a lot of applications specific to our needs. With any workflow, comes a different set of requirements, and ActiveBatch has allowed us to meet or exceed every one of them.
- Interaction with other third party software. Interacts with encryption software, various 'partner designated' sftp software, file manipulation software, etc.
- Variety of options for users based on experience in accomplishing the same things as 'coders'. Someone like me wouldn't need to use the Jobs Library too much but users who are not comfortable with code can accomplish the same tasks using the drag/drop functionality of the pre-built jobs library.
- Security. Allows the admins to secure every single element of the system; plans, jobs, accounts, etc.
- Easy to use by the end-users.
- Lack of continued development for the non-jobs step library items.
- Updates sometimes 'break' previously working functionality; the email trigger comes to mind.
- Lack of development of what can trigger jobs/processes.
- Less errors since taking humans out of the processes.
- Security tightened on the servers.
- Standards set.
I found it suited for just about anything. Currently ActiveBatch sits on a Windows environment, but it can hit the Linux servers by calling WinSCP or Putty to perform actions on the Linux servers.