Control-M vs Nintex Process Platform

• Control-M Advanced File Transfer is a very useful add-on, allowing for a wide variety of file transfers to be configured "out of the box" and then used as part of the standard batch flow. This module is not included in the base price but is available at a relatively small additional cost.
• Using Control-M's GUI (the Enterprise Manager) allows for efficient management of the enterprise and can tie up a lot of "loose ends". Often the first point of tracking problems is to check with the Control-M guys!
• BMC is definitely moving the product forward, the new module "Application Integrator" is very helpful in building and deploying your own bespoke Control-M jobs and allows for closer and more secure integration.
• Although Control-M does open up the enterprise in an operational sense, the security settings (should you choose to implement them) are robust.

Read full review

• Branching logic in forms - This allows for a single form to cover related processes depending on choices made in the form.
• Seamless integration with Office 365, allowing us to drive actions in the workflow based on item changes in SharePoint Online
• The fact that it uses a separate service to offload the processing power instead of having to provide it as part of our organization.

Read full review

• Single Major Action per job: this statement needs to be clarified. There are ways to do more than one action per job, and there are pre and post job commands available in most templates. Also some templates like FTP can have many instructions built in, like deleting source files after transfer (these are part of the positives). But basically you can only do one major action, like call one web service, or call one stored procedure per job. I believe this limitation is due to their licensing model, to ensure you will run as many jobs as possible.
• The only other negative is a necessary corollary of a having a powerful product. The learning curve is not simple due to the power of the product. I would recommend dedicate training for the primary operators and users of the product.

Read full review

• Updating Nintex to fix bugs in a production environment can be challenging at times and requires thorough testing in a QA environment first as it doesn't always go smooth.
• Separating Nintex content databases and moving site collections with large workflows can be a daunting task.
• Nintex workflow timer jobs can use a lot of server resources at times and application server load balancing should be implemented instead of running on a single server.

Read full review

• Troubleshooting has improved with multiple groups as they are easily able to determine if data loss/job failure is the reason for a data issue.
• Conversion took significantly longer than was originally estimated by BMC so we had to run two platforms for almost 9 months. This definitely slowed down efficiency as many users did not know which tool to utilize for data load trouble shooting for close to a year.
• Being able to communicate with users across the globe in a universal language and time reference has vastly decreased data issues and greatly improved proficiency in getting new jobs implemented quickly and without problems.

Read full review

• Nintex offers process automation that simplifies business solutions. Learning how to use all of the actions is not as time consuming as other WorkFlows I have configured before.
• The learning curve on creating, maintaining and troubleshooting Nintex WorkFlows heightens productivity. Plus, I can appreciate the online courses offered on their Nintex community site along with live support assistance if and when the occasion rises.
• I have noticed less WorkFlow bottlenecks; This improves efficiency, controls expenditure of time, money, resources and drives process improvements.

Read full review