Nintex Process Platform vs Oracle BPM Suite

• Nintex workflows provide a robust interface that's not only intuitive but easy to learn with little to no coding experience.
• Nintex forms are particularly powerful and provide a great alternative to InfoPath forms which is being deprecated.
• Upgrading between versions of Nintex is easy to do with their nwadmin tool and robust documentation provided on their support portal.
• The user adoption rate of their products is extremely high and doesn't require a selling point or an explanation of benefits in converting their existing workflows and forms.

Read full review

• Modeling business processes - it is providing an interface where users can drag and drop many kinds of shapes to build a business process.
• HumanTask - I consider this as being the key strength of Oracle BPM. It allows you to create approval flows in different ways and it manages the long-running processes (while waiting for people to interact with the flow).
• The user-interface for user tasks - it is one place where you can see all tasks and their progress. Admins can see and interact with other people's tasks.

Read full review

• Forms: Some functionality about validation, or buttons need to be implemented using JAVASCRIPT. It would be welcomed to include more functions in this area.
• Forms: The parent-child relationship is another area to improve. Repeating sections don't have the required performance to make a strong relationship between two or more tables (Sharepoint lists).
• Workflow: Using an on-premise environment, there is not a good system to manage workflows: versions, insights, purge, etc.

Read full review

• Again, it takes a decent amount of IT knowledge to realize the full potential of the Oracle BPM Suite
• It can tend to feel sluggish unless you slightly exceed the minimum system requirements
• There are so many features that it can be difficult to know which ones to use and which ones not to use in a given situation

Read full review

• Nintex has an ROI report that analysis all workflows in your environment and time spent on developing the workflows . We have paid off our investment in the first 12 months according to this report.
• Once you have implemented it, you should probably have more than one person or have plans in place to get more people because the requests will start streaming in.

Read full review

• Documenting a flow to a client allows communicating the intention of a development and thereby minimizing changes that could delay the calendar.
• Simulating macro processes allows you to visualize at an early stage the figures of a project in order to better manage resources.

Read full review