AgilePoint NX Reviews & Product Details

Low-code platform: AgilePoint NX provides a visual interface for creating and deploying applications, making it easier for non-technical users to get involved in the development process. Integration: AgilePoint NX can be easily integrated with other systems, such as CRM, ERP and legacy systems, providing a seamless flow of information across the organization.

Like any technology, AgilePoint NX also has some limitations and potential drawbacks, including: Steep Learning Curve: The platform has many features and capabilities, and it can take some time for users to understand and utilize all of its capabilities thoroughly. High Cost: AgilePoint NX can be more expensive than other low-code platforms, making it less accessible for smaller organizations or businesses with limited budgets.

Complex Business Processes: AgilePoint NX helps organizations automate complex business processes, reducing manual labor and improving efficiency. This enables organizations to streamline their operations and reduce the time and effort required to complete tasks.

AgilePoint NX is extraordinarily intuitive to use with a low learning curve compared to the other BMP solutions I have used in the past while simultaneously enabling flexibility, allowing you the process to address both common and complex use case scenarios.

Outside of your employer giving you access to AgilePoint NX or requesting a limited trial, it can be challenging for a single business power user or citizen developer to gain access to maintain, hone or expand their learning for an extended period. It would be great if AgilePoint provided a no-cost developer environment or a reasonably priced one for single developer users. Long term, I can only see an upside to this as such citizen developers would take this with them throughout their careers.

While an employee at Honeywell, I used AgilePoint NX as an enabler to automate many Direct and Indirect Procurement processes. Most use cases were centric on exceptions processes that were not accounted for within either our ERP systems or other IT-managed platforms, which necessitated the rapid development of tools that could fill these critical gaps. Some of these were: - Payment Term Exceptions: A process that enabled a hierarchical approval process with embedded business logic to realize deviations to payment term business objectives with 3rd party suppliers. - Waivers of Competitive Bids: A process that enabled exceptions to Honeywell's competitive bid policy. Likewise, this process supported a hierarchical approval process with embedded business logic and an SAP R/3 BAPI, allowing the process via web service API to only allow purchase requisition processing into a purchase order within the ERP after gaining proper business approvals within the process.

Some of the features our teams reported liking the best have been: - AgilePoint provides automation when we were told automation was not available - Friendly collaboration across sites - Ease of use - Excellent customer and project support - Plug and play low code solutions

There is not a whole lot I dislike about the application. Would like to move to a newer version soon!

Some problems we are solving with AgilePoint is the ability to simplify workflows and eliminate manual activity. This sounds like a no-brainer, however the benefits are allowing users to better allocate their time to more projects that add value.

easy to integrate other systems by using WebAPI

The eForm wizard cannot meet the complexity needs of the enterprise

as a flow engine on our new e-form system

The low-code/no-code model allows you to create workflows as quickly as you need to, but there enough connectors and activities to allow for more complex models as well. I really like the Management console that allows insight and control over all active workflows and tasks.

Some of the more advanced workflow activities are not as intuitive as they could be and the documentation does not always offer a good example of how they could be used, but the support team is always very helpful in sorting out questions.

We have created electronic versions of multiple approval processes that supplement our ERP system, both decreasing time to approval and eliminating the paper trail. We have also improved KPI reporting through simple metric-collection forms tied to a short approval.

Web-based, easy integration and management

Windows-based conditions for setting up.

Overall process and business management

Easy to use user interface to allow our personnel to focus on solving problems rather than learning how to use it. Using AgilePoint, we are able to digitalize and automate our daily processes without hiring software developers to build custom solutions. It even supports mobile user interface. This minimized knowledge gaps, reduced turnaround time which translates to better productivity.

AgilePoint is straightforward for simple workflows, however it lacks community support for custom development on AgilePoint. I wish there are better community support for software developers to use AgilePoint

Process automation - to reduce paper forms and centralize our processes to avoid content silos. It reduced average process turnaround from 2 business days to 6 hours.

Flexible eForm and ready functions for SharePoint or O365 integration. Document and video tutorial accessible easily.

Not discovered yet. The system is up to our expectation.

Capital Expenditure Requisition.

Easy to configure, low code, not difficult to build complex workflow

Nothing, because almost all of our clients' needs can be solved

Complex Workflow can be set up easily with AgilePoint NX configuration

We've used AgilePoint to build forms and workflows across many departments in my organization. The tool is perfectly capable of making simple conversions from paper to digital but, with a little outside the box thinking, also flexible enough to handle more complex workflows as well.

The tool is meant to handle workflows that are completed within a relatively quick amount of time. If you have a workflow item that must sit idle for a period of time, things can get complicated. We've often had to break these workflows up into two separate forms: the first creates the task and closes it (where it can idle), the second will retrieve and 'pick-up' the idle task to complete the next part of the workflow when appropriate.

We've converted many paper-based forms to digital ones with approval workflows. We've also used new forms and workflows to engage users in ways previously not possible, such as through their mobile devices.