Nintex Process Platform vs Oracle BPM Suite

• Process mapping and designing of models, which perfectly issues an outline for swift actions.
• Constant issuance of standard report, a formal way that improves the processes that enhance fruitful operations.
• Automation of several actions, more so those with routine requirements and daily commitments.

Read full review

• Oracle BPM [Suite] can support unlimited number of cases. No limitations in cases raised.
• Oracle Weblogic can handle multiple traffic. [It] can handle lots of heavy load[s].
• Oracle BPM has extensive integration with database[s]. Huge number[s] of customization can be created.

Read full review

• Nintex Process Platform is an overwhelming platform for staff unfamiliar with IT, for this reason only the IT team is in charge of using this tool.
• Cloud costs can be very high.
• Better training for users unfamiliar with IT can go a long way toward expanding the use of Nintex Process Platform.

Read full review

• Oracle BPM is left behind by other tools more modern in terms of user experience, usability and ability to integrate with everything else.
• To really harvest the potential of Oracle BPM you need to do it in JDeveloper and with ADF. This restricts its usage to very technical people.
• The administration of the Oracle BPM tools has really put a burden on our team. It is running on Weblogic and we experience issues very often either with performance or with a bad configuration of the system.
• As with all Oracle products, the price can be an issue for smaller shops.

Read full review

• Nintex has saved the department many hours of work by allowing us to use simple forms and workflows and taking us away from spreadsheets and outdated databases.
• Our audits used to take hours and our last audit took only 30 minutes, thanks to the tracking abilities we now have using Nintex forms.
• Once I learned the best practices for setting up the processes, I was able to create forms & workflows that other people could update going forward so changes happen easily as things occur. An administrator is not needed, after going live.

Read full review

• You'll most certainly need a deep dive and extensive training before your users can even think of using the product and they are very expensive.
• Lack of documentation makes it very difficult to manage the application if any error is encountered which will result in you ending up hiring a dedicated person to look into the application once it's deployed.
• For a very large org., if properly implemented and used, it can help identify the cost-intensive and inefficient processes.

Read full review