The jobs library is awesome. It provides a great variety of low-code automation steps. Being able to mix and match job steps from different library modules is really powerful. For example, we use the Active Directory, File System and Flow Control job...
My main issue with Active Batch is when you get to the point of writing complicated scripts touching multiple systems it becomes impossible to read in there "drag and drop" system. We tend to write our scripts in power shell and just execute them from...
I like the swiftness in transferring the files to customer being automated which can be customized into success, failure etc.
Restarting jobs or processes from the software itself can be confusing
The jobs library is awesome. It provides a great variety of low-code automation steps. Being able to mix and match job steps from different library modules is really powerful. For example, we use the Active Directory, File System and Flow Control job...
I like the swiftness in transferring the files to customer being automated which can be customized into success, failure etc.
My main issue with Active Batch is when you get to the point of writing complicated scripts touching multiple systems it becomes impossible to read in there "drag and drop" system. We tend to write our scripts in power shell and just execute them from...
Restarting jobs or processes from the software itself can be confusing