OpenText Process Automation Reviews

Positive

We primarily use OpenText AppWorks for financial workflows, syncing between customer data, and workflow management related to financial tasks and batch updates.

OpenText provides valuable business process management notation models and is a lightweight application. Its customer support is reliable and easy to approach. Each application can work in isolation which is a very good feature.

OpenText needs improvements in its integration model to align with newer integration types. The BPMN 2.0 model does not function as designed, and there are challenges with application performance and the BERT files. Overall, the product needs significant improvements.

I've been working with AppWorks for two years.

Stability requires frequent restarts, and I rate it a six out of ten.

Scalability is complex, with five out of ten rating, especially horizontally. OpenText cannot easily be put into a microservice model.

OpenText provides very good support, which I would rate a nine out of ten.

Positive

Previously, we used IBM Business Automation Workflow but moved away due to cost issues.

The initial setup process is very complex.

The upgrade process was complex and managed by the OpenText vendor itself.

OpenText AppWorks is somewhere mid-tier in terms of pricing compared to other products like Pega and IBM. It is not as costly. However, you need good negotiation with the vendor for the best pricing.

The main competitors for OpenText AppWorks are Pega, Camunda, and IBM.

I recommend that potential users clearly understand their needs and perform a use case analysis to see how their needs align with the solution.

I'd rate the solution six out of ten.

The product's use cases vary across industries. In banking, we utilize it for cash management services, while in manufacturing, we've developed supply chain solutions and warehouse management systems. Additionally, we've built quality management systems and integration projects connecting with various systems like SAP and Salesforce.

We've automated several processes, including purchase requisition to purchase orders, RFQ processes, vendor onboarding, project budgeting, and business case creation. The recent versions of OpenText AppWorks, especially those incorporating low-code functionalities, have had a significant positive impact. In some cases, we've observed a remarkable reduction in development time, ranging from 50 to 75 percent. The MTP model and life cycle have facilitated rapid development cycles. 

OpenText AppWork's low-code capabilities can be enhanced by integrating them with AI offerings like Aviator.

I have been using the product since 2010. 

The tool is pretty stable. I have been working with banks using it for the last eight years without any issues. I rate the tool's stability a nine out of ten.

I rate the product's scalability a ten out of ten due to seamless integration with other OpenText products. Features like high availability and load balancing further ensure smooth operation, even under heavy usage. This high scalability is demonstrated by its successful implementation in large organizations like the largest private sector bank, which processes substantial volumes of data without any issues. My company has 15 customers. 

The tool's tech support is pretty good. 

The setup process is relatively straightforward, typically taking around four to five hours for installation. While setting up high availability and multiple nodes may require additional time, the standard installation process is simple and can usually be completed within three to four hours.Deployment can be straightforward, especially with the addition of CL/CD capabilities in recent versions, leveraging Docker and Kubernetes. Even before these enhancements, the standard process of creating and installing packages with dependencies was relatively uncomplicated. Maintenance typically requires only one or two resources per customer, with more significant landscapes potentially requiring two or three resources. I rate the product's ease of integrating with existing infrastructure a nine out of ten. 

Despite the comprehensive guide, I highly recommend engaging consulting services for the setup. Numerous critical factors must be considered, and ensuring everything is configured correctly from the outset can help prevent issues.

The licensing cost varies based on several factors, such as the size of the customer and the domain URL. There isn't a fixed cost, and it's determined after sharing relevant details with the OpenText team. They will provide a customized quote based on the customer's size and domain. The licensing cost typically involves a one-time payment for the perpetual license. Additionally, there is an AMC renewal fee, usually around 20-22 percent of the license cost. The AMC renewal fee may increase annually by approximately 0.5 percent. I rate the tool's pricing a seven point five out of ten. 

I rate OpenText AppWorks a nine out of ten. 

The monitoring aspect is highly valuable, as it offers an exceptional capability to track every minute of action performed by a business user in the global context.

The crucial missing element is the archival function. When you have numerous processes in your system, generating instances on a daily basis, your database naturally grows larger over time, and without proper archival capabilities, there is a risk of losing valuable data.

I have total of four years experience working with it.

We encountered performance problems that stemmed from a sizable metadata database storing process data and machine metadata. As it continued to grow, we had to remove older instances to enhance performance.

It allows you to scale as needed, but the primary concern is archiving. As your database grows, it can lead to performance degradation. This can be particularly critical, especially in financial system development where comprehensive tracking is essential.

There were two major instances when we contacted customer support. In one of them, they provided a prompt solution with excellent support. However, in the second instance, there was no existing solution, and I had to come up with my workarounds. I would rate it eight out of ten.

Positive

I've had experience with Oracle BPM, which has some similarities to AppWorks. The switch was a business decision driven by the fact that our customer had an existing agreement with OpenText, so we needed to use the tool in line with our testing requirements.

The initial setup isn't overly complicated, but it requires careful attention to detail. To get started, it's essential to thoroughly review the complete manual before proceeding.

The deployment process takes a few minutes.

I would strongly recommend planning to upgrade to the latest version as soon as possible and before embarking on any development work. For instance, if you're aiming to go live by the end of the year, ensure that you allocate a period of two weeks to a month for the upgrade to the latest version and thorough system testing before proceeding with the system's launch. Overall, I would rate it eight out of ten.

Our focus is on delivering business products to our customers, which encompass various functionalities such as managing business processes, orchestrating workflows, and handling document management. Our offerings include tailored solutions that streamline work processes and efficiently manage documents, enhancing overall business productivity.

From a business perspective, the most valuable aspect lies in the optimization of processes. Managing paper documents can be challenging, but with the implementation of OCR technology, efficiency is greatly enhanced, saving both time and costs. This solution allows for significant time savings, reducing the reliance on traditional paper-based workflows and ultimately leading to substantial cost savings. Additionally, the centralized nature of OpenText provides a strategic advantage. By integrating various tools such as CRM, ERP, and sales systems, OpenText serves as a comprehensive solution, streamlining and unifying the entire system for enhanced efficiency and management within the company.

There is room for improvement in the pricing structure.

I have been working with it for a year now.

The stability of the system is exceptionally high, and we have never encountered any issues with it. I would rate it nine out of ten.

Our client base primarily consists of enterprise-level businesses. It provides robust scalability that meets our requirements effectively.

I have experience with Web.com. Drawing a comparison, my experience with OpenText highlights its significant advantage in terms of capacity. It stands out for its ability to handle much larger volumes of data and more extensive databases, leading to improved efficiency. Also, the incorporation of AI solutions represents a substantial transformation, and in this regard, OpenText stands as a robust product. It's particularly well-suited for enterprise clients, offering advanced features and capabilities that cater to the diverse needs of larger organizations.

The initial setup was fairly straightforward. I would rate it seven out of ten. It's a ready-to-use solution that eliminates the need for advanced programming skills. While we collaborate with partners to implement the product, there's a period where our customers can independently create their own workflows. This allows them to develop business applications tailored to their unique needs effortlessly.

The deployment time for initial functionality is estimated to be around three to four months before the first business cases become operational.

The price is on the higher side. When compared with companies in Poland, particularly our competitors, they often offer more budget-friendly solutions. However, it's worth noting that while OpenText provides a broader range of functionalities and features compared to these competitors, some customers prioritize cost over features. In certain cases, the pricing, especially in the public market, could be enhanced to better align with customer expectations and market dynamics. I would rate it seven out of ten.

Overall, I would rate it seven out of ten.

We use OpenText AppWorks primarily for automation in the insurance, banking, and manufacturing industries. We use the solution for process automation.

OpenText AppWorks has standard features such as system-to-system and human-to-human integrations, but what I find most valuable in the solution is its monitoring feature that tells you more about your processes, how to restart and how to stop each process, etc.

A room for improvement in OpenText AppWorks is its user interface. It should have mobile compatibility because right now, you still have to make two applications with a user interface for Android and a user interface for iOS, so if OpenText AppWorks can provide one UI that can be used across all devices, that would make the solution better.

An additional feature I'd like to see in the next release of OpenText AppWorks is a better UI in terms of the look and feel. Another feature I'd like to see in the next version of the solution is mobile compatibility because, at the moment, you have to make your application mobile-ready or compatible with mobile devices because there's no provision for it in OpenText AppWorks.

I've been working with OpenText AppWorks for more than ten years now. The name of the solution recently changed, but it's what my company has been implementing for customers in the last ten years.

OpenText AppWorks is a stable product.

OpenText AppWorks is a product that's very much scalable.

The technical support for OpenText AppWorks is fine, but it's not one hundred percent, so if I were to rate support, I'd give it seven out of ten.

The team is quick to respond, but should have more expertise, be more knowledgeable about OpenText AppWorks, and should do a better analysis.

Neutral

The initial setup for OpenText AppWorks has medium complexity, so it's not so easy and it's not so complex. How long the setup takes would depend on the type of application, its complexity, and your knowledge of it. You need to have the right experience.

Pricing for OpenText AppWorks, specifically in the Indian market, is reasonable, but I'm not aware if it's still reasonable outside of India. The licensing cost is based on the number of licenses and the number of users. OpenText AppWorks has different licensing options.

We're also working with another solution, Appian, apart from working with OpenText AppWorks.

My company works with OpenText AppWorks which is the primary OpenText platform, in particular, a business process management platform.

My company serves enterprise customers. The number of people using OpenText AppWorks depends on the client. Some clients have a few thousand users, while some have close to one thousand users of the solution.

My advice to others looking into implementing OpenText AppWorks is that it's a very good BPM platform and it has a lot of BPM capabilities, but its UI needs improvement. Just recently, the OpenText AppWorks team came up with a low-code platform focused on entity modeling, but that had a lot of limitations and only works for a few, small processes, and not that much for complex processes. The UI for the solution is complex, and it would be better to go for Openpath and Angular or use another BPM engine.

My rating for OpenText AppWorks is seven out of ten.

My company is a partner of OpenText AppWorks that provides support and implements the solution for customers.

I primarily use AppWorks for invoice process automation, accounts payable, order-to-cash, report-to-report, vendor collaboration, and to build turnkey processes for different verticals.

AppWorks is a very quick development platform with low-coding capability and strong integration with third-party systems. It also has a very scalable workflow or dynamic case management.

AppWorks could be improved by including BPM simulation.

I've been using OpenText AppWorks for nine years.

AppWorks is stable.

AppWorks is scalable.

The initial setup is medium complex - it's not highly complex, but you need to have skilled people to do it. 

We used an in-house team.

AppWorks is pretty expensive.

Anybody who's going to adopt AppWorks should first have a clear strategy for how they want to implement BPM for their organization. Once they add that, this tool can bring quick results. I would rate AppWorks as nine out of ten.

For our customers, we have multiple use cases. It is mostly used for integration-specific solutions, as well as workflow-centric solutions. Wherever this combination is required, where there is an integration, or a workflow, or both, we use this platform.

We are not providing specific solutions. We are doing customizations and providing tailor-made solutions for the customer. We have around 12 customers in India.

The solution can be deployed on-premises or on the cloud.

Integration could be improved. There could be some improvements with the low code design part. It could be more customizable and more user friendly.

We are consultants and have been providing this solution since 2014. I have been working with this solution since 2010.

It's very stable. We have worked with customers for the past eight years, and it has been very stable. They are happy with the solution provider. We have been providing after-deployment support services as well.

In terms of the scalability and the handling of complexity, the customers are satisfied, and we also have confidence in the solution to achieve whatever implementations are required.

It's fine. We get regular updates, and there is a portal where any case can be logged, and we get proper support from there.

It depends. Basically, for the low code features that have been introduced, setup doesn't take very long for a normal application/midsize application. It should take around one and a half months and not more than that. If there are more customizations, for example, then of course it takes more time because then you have to write code and put in some of the logics. But otherwise, for a midsize application, it shouldn't take longer than a month and a half to set up.

There is a user-based perpetual license.

I would rate this solution 8 out of 10.

I would recommend this solution for those who want to start using it.

We use OpenText AppWorks online applications for social grants.

One of the most useful features is the code is customizable, we can make it our own.

The integration could improve.

I have been using OpenText AppWorks for approximately six months.

The stability could improve, we have had a few errors.

The solution is scalable.

We needed some assistance from technical support and the response was satisfactory.

The initial setup was straightforward.

I did the implementation of the solution myself.

We have evaluated Oracle.

I would recommend this solution to others.

I rate OpenText AppWorks a seven out of ten.

Generally, we use the solution for automating business processes. 

For our organization, the low-code environment has been the most useful aspect of the solution for us. We'd like to see more capabilities in the future. They really could grow it out quite a bit. If they enhance it further, it would make the solution more user-friendly and easier for their customer base.

We really appreciate the process automation and how can you create human tasks as one of your processes.

The stability has been quite good over the years.

The solution can scale if a company needs it to.

The solution needs to continue to enhance the low-coding feature within the product itself. It could be better. They could continue to expand on its capabilities. It would improve the product in the long run.

We have been using the solution here for about three or four years. 

The stability has been perfect over the years. There are no bugs or glitches. It doesn't crash or freeze. It's reliable. The performance is good.

We have 400 to 500 users who take advantage of the solution at our organization.

The product is very easy to scale. If a company needs to expand it outwards, it can do so with ease.

I've never been in touch with technical support. I can't speak to how helpful or responsive they are due to the fact that I've never personally used them.

We did not previously use a different solution prior to implementing this product.

I didn't handle the initial setup of the product. I wasn't a part of that team. Therefore, I can't effectively speak to how easy or hard it was to set up the solution.

We tend to handle the maintenance on our side, unless the issue is a bug or a defect, in which case, we would go directly to the vendor. We have two or three individuals that can handle any maintenance the product might need.

The deployment was completely handled in-house. The company did not require the help of outside consultants or integrators.

While I don't have the exact figures in terms of pricing, my understanding is that it is moderately priced. It falls somewhere in the middle. It's not overly expensive or very cheap.

I wouldn't be able to discuss if there are extra costs over and above the standard licensing or not. I don't have that kind of visibility.

We're just customers, however, we do have a very good relationship with Open Text.

I was leading the team who's working on it. I don't have hands-on in terms of technical, from a technical point of view. I was leading the team that was using it and developing business processes that were implemented using that technology.

We're doing the latest version of the solution. I don't recall the exact version number.

I'd recommend the solution overall. I would rate it at an eight out of ten. We're mostly quite happy with its capabilities so far.