OpenText 360 for SharePoint Reviews

I have 5 years of experience in the Microsoft ecosystem, which includes IBM Cognos and ClickView dashboards.

In my organization, I typically use OpenText 360 for SharePoint with Office 365 where the sales and R&D teams use SharePoint to share their data as it serves as a central repository. Across different regions, it acts as a central repository where data is entered, and my dashboard pulls the datasets from SharePoint. I am also using Power Automate and Power Apps to pull the SharePoint list. A simple example is the approval mechanism where if an invoice exists, it will go through Power Automate for the approval process and is stored in the SharePoint list.

I use the SharePoint list as the consumer layer for Power BI, making it a complete Power Platform process. I own the whole Power Platform, and that is how I position myself in my ecosystem.

From my perspective, the advantages of OpenText 360 for SharePoint include being able to see the SharePoint list because once we enter the SharePoint list, we can get all the metadata related to information. For example, when using Office 365, I can see the list of licensed users who are actually consuming Office 365, along with profile pictures and contact information. All the metadata can be retrieved from the SharePoint list, and those libraries and metadata serve as a very effective way that I am utilizing SharePoint, apart from just storing documents.

We have our own repositories where we conduct company announcements, organizational announcements, and schedule sessions on the calendar, which is very helpful for our organizations. The benefits that OpenText 360 for SharePoint has brought to my company include improved turnaround time. Rather than circulating content over email, the turnaround time for the business has significantly improved with the help of SharePoint.

The area of improvement with OpenText 360 for SharePoint is that sometimes there are unexpected service outages. Though these situations are rare, I want to highlight that in case of any outage in the services, because everything is located in SharePoint, there is a chance that reports start failing or dashboards fail, or the system behaves differently.

In future updates, I would want to see widgets available in OpenText 360 for SharePoint to interact with third-party tools. For example, when creating a dashboard, having the ability to embed these directly into SharePoint would be beneficial. Currently, I have to use hyperlinks to access other tools such as Tableau or ClickView. If it were possible to merge everything and bring all information from multiple teams (Cognos, ClickView, AWS) into SharePoint as a centralized place, it would be really helpful. That is what I envision for the integrator part.

I am not very familiar with SharePoint, and the initial deployment was not straightforward for me. The data I am consuming is from SharePoint for the dashboards. People create the lists, forms, Excel files, and other documents which are hosted in SharePoint, and I am at the end layer where I consume items from SharePoint. I do not have much knowledge about the different teams who actually own SharePoint, as I am primarily a consumer.

My solution is always focused on dashboard deployment. The time for deployment of this product depends on whether it is simple, medium, or complex. Based on that solution, I handle the deployment, which for me means dashboard or report development and deployment.

SharePoint is a stable product for me, though I am not the most qualified person to discuss SharePoint extensively.

It is scalable.

I would rate their customer support as nine out of ten.

The return on investment provided by OpenText 360 for SharePoint is excellent, and that is why we are continuing this team for the past 3 years. The customer is not ready to move away from this solution. The return on investment is really good, and we keep getting more people involved. There are 48 servers, and we continue to grow.

Regarding the licensing setup cost and price overall, the licensing costs are reasonable. As an enterprise organization, we have enterprise service level agreements with customers and Microsoft partners, where organizations receive yearly discounts. I do not have much knowledge about the financial and costing aspects as we are solution providers focused primarily on the solution aspect rather than the commercial part.

I have not utilized the advanced document management feature of OpenText 360 for SharePoint.

I use the configurability of OpenText 360 for SharePoint to create automated processes through the Power Automate flow and Automate desktop, but not in SharePoint itself. For that, I used Power Automate as a different solution.

I would assess the impact of SharePoint's intuitive user experience on team adoption and engagement with the platform as definitely deserving a rating of nine out of ten from a user experience perspective.

Regarding the integration of OpenText 360 for SharePoint with additional OpenText solutions for analytics and engagement processes, we use ready analytics. We have a separate team for Power BI and ClickView, and we have not configured anything on SharePoint. We moved everything to Power BI for access and permissions management. When discussing analytics, it falls under Power BI.

I am part of a team of 10 members focused on visualization, narrative, and storytelling.

I rate OpenText 360 for SharePoint 8 out of 10.

I use OpenText 360 for SharePoint integrated with Microsoft Teams, allowing me to check projects and handle task issues not only on a laptop but also using mobile devices.

OpenText 360 for SharePoint integrates seamlessly with Microsoft Teams, allowing me to monitor and manage projects and task issues using mobile devices. Additionally, it offers automation capabilities with Power Automate, enabling automation of invoicing with API support from SAP, providing convenience to our customers.

In the future, I would like to see new features in SharePoint for improved project tracking processes. Specifically, integration with a feature like Planner could assist in assigning tasks to specific individuals for follow-up.

I have been using OpenText 360 for SharePoint for five years.

From a scale of one to ten, I rate the stability of OpenText 360 for SharePoint as ten.

I rate the scalability of OpenText 360 for SharePoint as eight.

I rate the technical support for OpenText 360 for SharePoint as eight.

Positive

I have always used SharePoint and did not switch from any other solutions due to its convenience and long-term usage by my company. I do not wish to change platforms to avoid risks.

Our Info team, consisting of ten engineers, helped with the implementation of OpenText 360 for SharePoint.

In terms of pricing, OpenText 360 for SharePoint is more expensive than Microsoft. On a scale of one to ten, I rate its price as six.

Overall, I would rate OpenText 360 for SharePoint as ten. I would recommend this solution to others. My role focuses on research and development and customization, but I do not maintain the system.

Neutral

My project manager must be using the search capabilities of OpenText 360 for SharePoint, though I am not certain.

The overall benefit I get from using this solution is developing in a more secure environment with distributed architecture and even distribution of work across resources where full control on the code and repository is required.

The integration capability is good. The supportability of file extensions compatibility is also valuable.

For SharePoint, the user-friendliness needs to be improved. It is not as simple to use as GitHub, which has a very straightforward interface. I would prefer it to become more minimalistic like GitHub. All CI/CD pipelines need to be managed properly. Additionally, the pricing needs more flexibility and better support from Microsoft. If someone is creating an Azure virtual machine, even after their license expires, there should be some kind of backup with the Microsoft team so that it can be revived.

I have been implementing OpenText 360 for SharePoint for close to two years.

I would rate the stability as moderate. I do not give it a full rating due to its moderate performance.

On a scale from one to ten, I would rate technical support as five. Many things need to be checked from the forum, and they are very rigid on their policies and terms.

Positive

There are two persons involved in the deployment of OpenText 360 for SharePoint.

Since we are a software company, we do not need SAP to use in-house. We use Odoo. Sometimes we use SharePoint for our client projects and the Office suite.

I cannot adequately answer some of these questions as they are quite technical, and I oversee business development rather than technical implementation. My overall rating for this solution is seven out of ten.

OpenText 360 for SharePoint helps us with work and document management. We have all the functions and files of private equity firms stored according to particular investment portfolios. It handles all the document workflows and logging activities.

The product has a strong and easy integration with Teams.

The platform's workflows could be more intuitive and easier to use. They could enhance the integration with Power BI and make it seamless, similar to Teams.

I have used OpenText 360 for SharePoint for over six or seven years. At present, I use the latest version.

The product is very stable. I rate the stability an eight out of ten.

We have 26 OpenText 360 for SharePoint users in our organization. We can easily scale it for 100 users, but I am unsure if it could scale beyond that. I rate the scalability a five out of ten; it could be improved for larger enterprises.

When we reach out to the technical support team, they respond quickly.

We have used some local internet-based solutions before.

We do not have to maintain the product. It gets updated automatically.

We take vendor's assistance for deployment.

OpenText 360 for SharePoint offers subscription-based licensing. It has a reasonable price. I rate the pricing a seven out of ten.

We have explored Google. However, OpenText 360 for SharePoint works fine as of now.

I recommend OpenText 360 for SharePoint to others and rate it a seven out of ten.

OpenText implements SharePoint in the legal industry in the way case documentation is organized. This connects various tools used for case management, including email correspondence, virtual meeting documentation, and other resources. These resources seamlessly integrate with SharePoint, automatically organizing information within its structure.

It enables the creation of sharing processes with clients and relevant stakeholders involved in a particular case. Administrators can establish specific sections within SharePoint, controlling access to confidential documents stored within 360. It set up approval rules for document updates and configured notifications for document storage activities.

We concentrate on the legal industry, such as legal libraries. It's the most structured solution we have used and implemented for five years.

The graphical user interface had to be more user-friendly. It's not as intuitive.

I have been using OpenText 360 for SharePoint as a solution provider for five to six years. We are providing the latest version of the solution.

The product is stable, depending on the internet access.

The solution’s scalability is high. 200-400 users are using this solution simultaneously.

I rate the solution’s scalability a ten out of ten.

Technical support is not very good. The tools provided are very complex. It's usually a phone number they have that is not always working. The 360 technical support in the chat is minimal. They have scaled up all the time because we don't use the support for general questions. We are very specific and have very high technical questions. Usually, we need to start from the low level, and they have to scale up, which generally takes time.

Neutral

The initial setup is straightforward. Generally, deployment takes one to three months, depending on the volume of the documents and the complexity of the organization. To deploy, start with a background analysis of the process so you can begin to create the work plan for the structure, and you have to represent the basic workflow process. Then, the process of migration is going to take time. It depends on the 360 data, but it takes time. You have to validate that the data was 360 graded 100% accurately as you're trying to implement some manual workflows into systematic and automatic and computerize them, processing them using SharePoint. For example, you must work on a plan to integrate the whole staff, segment by segment. You will not be doing this 100% for the first time.

Four to five people are required for the solution's deployment.

I rate the initial setup an eight out of ten, where one is difficult and ten is easy.

Deployment was done in-house.

360 is very nice. We have 100% ROI.

The price is not cheap but entirely reasonable.

The solution is a very capable platform. You can do a lot of things to integrate it. It's open to integrating with another product, such as encrypted backups. 

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

Our company uses the solution as a document management system for enterprise customers in the utility industry. Companies upload all asset details and provide mini documents within the environment. 

The solution effectively handles all record management.

The collaborative environment for long-term archival or record management is great. 

The user interface could definitely be improved. 

Requirements for policy management could be improved.

For many use cases, the solution cannot do all the things that SharePoint can do. 

The solution needs a stronger integration with Office 365 because most customers use Office but the integration is complex. 

I have been using the solution for over ten years. 

Stability could use improvement because there are many acquired products and the integrations are always problematic. If one component goes down, then the system stability is impacted. 

Stability is rated a seven out of ten. 

The solution is a market leader and has acquired many companies. Scalability is good because you can integrate with a lot more products. The only issue is the complexity of integrations. 

Scalability is rated an eight out of ten. 

The support is good in some areas and needs improvement in other areas. Support depends on the product.

For the core OpenText product, we get good support with a good skill set. For some other products, it is difficult to get support. 

Our involvement with the utility industry began six years ago and the solution was already in place. 

The setup is complex because there are many components and add-on modules. 

We implement the solution for customers in partnership with OpenText. We set it up and then a combination team of five or six people takes over for upgrades and implementations. Implementations take eight to ten months because they are complex. 

The on-premises version definitely has a lot of ROI for customers because it is used as a management system for long durations and particular environments. 

We have not used the cloud version so cannot speak to its ROI. 

The solution has a very complex pricing model. We don't get involved with pricing or licensing but note the complexity when comparing to other vendors or when hearing things from customers. 

Pricing is rated a six out of ten. 

I recommend use of the solution. They are coming up with a lot of cloud options so it is important to explore and choose the best deployment model for your environment. 

I rate the solution a nine out of ten. 

We used OpenText 360 for SharePoint on the intranet in different departments. Also, we use it on the intranet to post information. It was used for training and data management.

The fact that it allows for the internal sharing of information is very good. So, it helps us to always understand the plans of other business units while being able to post all of the updates we need to know within our organization. Also, people are able to work on single attachments.

Integration is an area where the solution lacks. So, integration is very important. We also want other things to be in place, like contract management, checking of invoices, and content management.

In a future release of the product, I would like it to have better integration, content, and contract management.

I have been using OpenText 360 for SharePoint for a long time across many organizations. It has been more than six years. My company is an end-user of the solution.

Stability-wise, I rate the solution a ten out of ten.

We have about 600 users using the solution in my company.

Scalability-wise, I rate the solution a nine out of ten.

I rate the support a nine out of ten.

Positive

I wasn't involved in the installation process. Honestly, I've been managing the ICTs. So, I didn't have any challenges really in terms of because we also have Oracle in place, and I know that they were also trying to integrate a few things with NetSuite and so on. There were no challenges with the installation process.

Only one person who is an engineer and specialist looks after the maintenance of the solution.

Pricing is a part of the enterprise agreement that we have.

I would definitely recommend the solution to those planning to use it.

I rate the overall product a nine out of ten.

I mainly use OpenText 360 to archive and index enterprise documents.

OpenText 360's best features are platform independence and its performance when searching large numbers of documents.

OpenText 360's performance could be improved. In the next release, OpenText 360 should include in-built connectors for plugins.

I've been using OpenText 360 for SharePoint since 2014.

OpenText 360 is generally stable, though there are sometimes issues with document size or format.

Open Text's technical support has a lot of skills for troubleshooting and resolving issues.

The initial setup is easy for those with experience but may be a little difficult for newcomers.

We've seen a good ROI from OpenText 360.

OpenText 360's price varies depending on how long you've been a customer, how many licenses you have, and which products you use. Professional services are available at additional cost.

I would rate OpenText 360 seven out of ten.

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.