OpenText 360 for SharePoint Reviews

I'm the user of the SharePoint OpenText process 360 for SharePoint. Basically, we are using this for our internal knowledge management portal. We use the solution for all our accounts. It’s for major internal web pages or for internal work for SharePoint. We mainly use it internally.

It has a lot of flexibility, and Microsoft does come up with some new additions from time to time. In SharePoint, you do have the flexibility of uploading the documents, and then you can create the workflow, the workbench of curation and approvals. That’s for any content that is to be secured or to offer people to trust that their content is secure.

You have that all workflows can be built. The approval workflows can go from one person to another person. Since everything's virtual now and people are working from home, there are more security concerns in today's world. The most important thing at this point in time is for people to feel secure. I'm not in an office; I'm working virtually. I like creating content that is secure.

In that case, as a part of the knowledge management and content management, if the SharePoint can really help us in regard in terms of having a proper workbench in place, a workflow in place that can be built within that, where is what we can build the workflow and resolve things, however, that has the information rights management and those types of things to give the contributors of the content a trust that, the content is safe. I'm fine with sharing this content between the organization.

There are a lot of features.

If I have to really create an internal knowledge management portal, if I have to compare SharePoint and WordPress, WordPress is far, far better in regard to the SharePoint option. It has got a lot of added features into that. Both of them have pros and cons, and it would be OK to have SharePoint if you're not investing much into the WordPress side.

The solution is evolving. Microsoft really comes up with a lot of new products all the time. There’s Riva, which is their new thing, and then there’s Syntex, a new thing as well. They add a lot of things. We're exploring items for different areas that we are working on. Wherever we feel that "Yeah, that's really important, and that's really helpful for our KM, knowledge management area," we look into it and see how it works. Microsoft's been our partner for so long. They are there to really help us. In terms of the actual stability part, it's good. We haven’t had any issues.

My understanding is the solution is scalable. We haven’t had any issues with expanding. However, there are a lot of areas in this regard that we still have to explore.

We have 200,000 people using OpenText.

There are a lot of POCs, and things are going on. Of course, when things grow, the business grows, and usage will grow.

Our technical team mostly deals with support. I don’t deal with them directly. As for the contract and as for the consulting contract, those have been taken care of as part of the agreement in regard to the technical support that is required. Everything comes into what has been agreed upon between both parties.

I used that which was there internally when I onboarded into this company. It was there already, and it has been trusted within the organization.

It was easy to set up. We had our Microsoft partner's help. We have our internal IT teams and then our Microsoft teams' help. It was not so tough, actually. The good part is we have a product team, a Microsoft team, and everyone who helps as a consulting partner knows their stuff. We also try to test any new things that come up from Microsoft to see if they can be implemented in our environment.

We had assistance from vendors. We are premium partners for them.

I know the licensing costs involved as I'm doing the budgeting part. I cannot really talk about the licensing things that have been agreed upon between Microsoft and us. Our procurement and finance team have taken care of the cost and everything. That's about their guidelines and things that they have between our organization and Microsoft.

We have people who work on OpenText and Office 365. Our technical team works on it. Our portal and everything is on Office 365.

I'm not a technical person, basically. I do have a technical team who work along with me.

I’m not sure what the deployment model is and if it is on the cloud or on-premises.

When you start using the solution, there are many things you might have to connect with and want to connect to.

It is a good solution. It gives you a lot of flexibility in having a few items for basic knowledge management. It's scalable, and there are a lot of new things that can be added. The good part is, when the organization is all on SharePoint, having this really helps you to integrate better.

If your whole organization is into SharePoint, when you're creating a knowledge management platform along with this, it really helps you to integrate better. The search feature works better since everything is on SharePoint.

Overall, I would rate the solution eight out of ten.

OpenText Process 360 is modular and there is also an integration with OpenText Content Suite. It's all now on cloud subscription, so you can use all the features without worrying about making the system update patches. All of the issues are taken care of in the cloud version.

OpenText Process 360 has our systems up and running, at least going forward. It's modular and has more features than other products from a financial point of view.

They need better solutions for common functionalities, like every week related activities, and customer support. They need to come with more out of the box solutions, rather than depending on customers to develop them.

I like SharePoint where you have work bots, so I hope they come up with a similar concept. Add the reusability of whatever components we configure. I believe this will be an advantage in the future.

In the beginning, OpenText Process 360 was not doing well. At least some patches were applied to fix the issues. To be honest, my experience with OpenText is that usually, they are not doing too much on quality assurance with their product. 

They are launching new features into the market but based on the customer feedback, they;re still incomplete. They are reactive. This is one of the difficulties of their solution.

I believe it is easy to scale. We have a local administrator. There is also a technical administrator. Within each function, we have one administrator who is managing a business site, helping users, initiating requests, inserting workflows and processes. We are supporting about 500 users now. 

We are also evaluating OpenText Process 360 in the HR sector. Maybe we'll extend it to the administration of domains as well.

I believe we have this service agreement, and we are responsible for the contract with OpenText Process 360. We don't face any issues. There are different models they are offering. They are responsible for everything from A to Z. They are offering also another alternative where they have on-site support, plus a user model where they have normal support. 

What we have done is we are getting some professional service agreements with OpenText Process 360. They are inviting us officially. We are contacting tech support on a monthly basis. On top of this, they provide 24/7 support.

We were using SharePoint. There is another tool for the workflow on top of SharePoint. It's similar to Flex. It was okay, but we moved our enterprise content solution to OpenText.

We find it is efficient to have the same solution from the same company for the transactional beta workflow and business process management.

OpenText Process 360 is costly compared to SharePoint. There is a very costly investment required to license the product.

I don't want to spend a lot on user licenses. The integration with OpenText Process was very complicated on licensing. This product supports the definition of roles and responsibilities. We are making a lot of investment in infrastructure and hardware with all this support.

My advice to someone considering this solution is that before looking into the technology solution, understand what your business requirement is. Try to optimize the business process service before you go for automation and spending too much on this. 

You'll pay a license while you are developing your business process. Optimize it a while, checking the laws and responsibilities. It is more valuable to spend the most time on the business side before you go for a set cost.

I would give OpenText Process 360 an eight out of ten because nothing is perfect. There is a lot of room for improvement with the product.

We have been using it internally for a number of workflows for onboarding customers from our banking branches. 

Now, we need to replace it because the product is coming upon its end of life. This is why we are considering replacing it with another BPM tool. The current version should be at the end of life in one or two years.

We have manual processes, so the workflow enables us to automate a number of these processes.

Internally, when a customer comes into a bank, we can onboard him onto our internet banking platform to receive a debit card and a credit card. We also use Case 360 for:

• Access rights management
• Account-to-account transfer
• Bank guarantee code amendments
• Document capture
• Employee management
  
• Mail management
• Upward file transfers
• Process management
• Signature verification
• Pending orders, etc.

We have a very good time to market tool, and the development platform should be made user-friendly. Mostly, it's just support.

The support is being provided by the vendor whenever there are issues, it should be at a very high level. In a banking institution, it is fundamental that if you are using workflow automated processes that you receive the right level of support for implementation.

It is not so stable.

It is not scalable.

We had many manual processes and we needed to look for a tool to automate those processes. That is why we moved to using BPM tools.

We are currently comparing two other BPM tool: Appian and Camunda.

Up until now, it has served its purpose. As we moved in these times, the demand gets bigger, and we need faster things with quicker support and implementation.

Most important criteria when selecting a vendor:

• Product features
• Terms of implementation
• It usability
• Scalability
• Support.

I use most of the things that are available there. SharePoint is a very extensive platform. There are dashboards, groups discussion, knowledge management, and all sorts of things. I use most of the functionalities. It is software-as-a-service, and we have the latest version. 

The fact that you can see and create something that fits your business is the most valuable thing in this platform. It is a customizable product, so it fits your needs.

Its licensing needs to be simplified. Currently, its licensing is very complex. It contains a number of pieces, and you have to be an expert in reading all the conditions in the license. They should simplify the licensing and make it easier to understand. It would make a customer's life easier.

I have been using this solution for more than ten years.

It is very stable. I hardly remember when it was down. There were some glitches, but they are difficult to remember.

It is very scalable. We started with only a couple of people. Now, the whole company is using it. We have around 200 people. So, there are no issues with its scalability.

We haven't had any issues with the solution. For small things that have happened, wherever we called, they got in touch within the next 24 hours. Usually, in another 24 hours, they have a solution for you.

It is very easy to set up. Everything is already there. What takes time is for you to customize the product according to your needs, which is usually a pretty straightforward thing. It also depends on the complexity of what you are trying to customize. It can perhaps take a couple of days, but usually, it is very easy.

Its price is reasonable, but its licensing is very complex. This platform contains a number of pieces, and you have to be an expert in reading all the conditions in the license. They should simplify its licensing.

It is such a good solution. I would rate OpenText 360 for SharePoint a nine out of ten.

Our primary use case is for providing user profiles.

In terms of its most valuable features, this solution, in general, will provide all you need and it's very convenient to use. We can share our details with collaborative platforms. We can give access to users. It's pretty flexible.

We are an information solutions company. We need a platform where we can connect all the videos through SharePoints and input and export through that.

They are not going for any add-ons right now. It's the same version we are still using and there is no plan of upgrading and/or creating any add-ons at all.

I have been using OpenText 360 for three years. 

Before that, we were all on our main hub.

There are around 80-100 users using it in our company

My experience with support has been wonderful. With any technical issue you can get 24/7 Microsoft support, because after all it's a Microsoft product. So of course you will get very good support from them.

I would of course rate OpenText 360 a ten on a scale of one to ten because I really like it. It's very flexible for us. Before, we were using an in-house solution, and it was very difficult to manage the servers with so many issues around that and most of the issues had to be sorted out within our company. With SharePoint, there is mostly zero downtime. Nothing wrong with that. Because of this, it's a 10. The best.

I would recommend this product to others looking into implementing it.

We are able to create and manage workflows using the data stored within SharePoint.

This solution has good connection and we do not need to migrate everything in order to protect the repository.

I would like for there to be even more integrations in the next release and I believe that the price could go down a bit.

I have been using this solution for six to eight months.

This solution is stable.

This solution is absolutely scalable, we have about three hundred users.

Technical support was good.

The initial setup was straightforward and it is easy to integrate with other systems. We have about three guys maintaining the solution.

SharePoint uses a subscription model.

I would rate this a seven out of ten.