OpenText acquired Documentum from Dell EMC in 2017, and now supports the enterprise content management (ECM) system. The vendor says users can build content-centric applications and solutions from collaborating on business documents to delivering case-based applications to managing highly precise processes in the most regulated business environments.
N/A
ServiceNow IT Service Management
Score 8.2 out of 10
N/A
Built on the ServiceNow Now Platform, the IT Service Management bundle provides an agent workspace with knowledge management, and modules supporting issue tracking and problem resolution, change, release and configuration management.
N/A
Pricing
OpenText Documentum
ServiceNow IT Service Management
Editions & Modules
No answers on this topic
ITSM Standard
Custom Quote
ITSM Pro
Custom Quote
ITSM Enterprise
Custom Quote
Offerings
Pricing Offerings
OpenText Documentum
ServiceNow IT Service Management
Free Trial
No
No
Free/Freemium Version
No
No
Premium Consulting/Integration Services
Yes
No
Entry-level Setup Fee
Optional
No setup fee
Additional Details
—
ITSM Pro and ITSM Enterprise also are available with optional "Plus" add-ons. These include AI Agents, an AI Agent Studio, and other features that augment the capabilities of the platform using AI Virtual Agents to automate tasks.
More Pricing Information
Community Pulse
OpenText Documentum
ServiceNow IT Service Management
Considered Both Products
OpenText Documentum
No answer on this topic
ServiceNow IT Service Management
Verified User
Team Lead
Chose ServiceNow IT Service Management
ServiceNow is very easy to understand, use, automate, and integrate. It provides various other exceptional features.
Features
OpenText Documentum
ServiceNow IT Service Management
Enterprise Content Management
Comparison of Enterprise Content Management features of Product A and Product B
OpenText Documentum
9.2
7 Ratings
13% above category average
ServiceNow IT Service Management
-
Ratings
Content capture & imaging
10.07 Ratings
00 Ratings
File sync, storage & archiving
9.07 Ratings
00 Ratings
Document management
9.07 Ratings
00 Ratings
Records management
9.07 Ratings
00 Ratings
Content search & retrieval
9.07 Ratings
00 Ratings
Enterprise content collaboration
9.07 Ratings
00 Ratings
Content publishing & creation
9.07 Ratings
00 Ratings
Security, risk management & information governance
10.07 Ratings
00 Ratings
Contract lifecycle management
9.07 Ratings
00 Ratings
Automated workflows
9.03 Ratings
00 Ratings
Artificial intelligence
9.03 Ratings
00 Ratings
Mobile support
9.03 Ratings
00 Ratings
Integration
10.03 Ratings
00 Ratings
Incident and problem management
Comparison of Incident and problem management features of Product A and Product B
OpenText Documentum
-
Ratings
ServiceNow IT Service Management
8.5
79 Ratings
3% above category average
Organize and prioritize service tickets
00 Ratings
9.178 Ratings
Expert directory
00 Ratings
8.161 Ratings
Service restoration
00 Ratings
8.364 Ratings
Self-service tools
00 Ratings
8.476 Ratings
Subscription-based notifications
00 Ratings
8.573 Ratings
ITSM collaboration and documentation
00 Ratings
8.370 Ratings
ITSM reports and dashboards
00 Ratings
8.373 Ratings
ITSM asset management
Comparison of ITSM asset management features of Product A and Product B
OpenText Documentum
-
Ratings
ServiceNow IT Service Management
8.2
71 Ratings
1% below category average
Configuration mangement
00 Ratings
8.170 Ratings
Asset management dashboard
00 Ratings
8.269 Ratings
Policy and contract enforcement
00 Ratings
8.261 Ratings
Change management
Comparison of Change management features of Product A and Product B
Documentum is best used in medium to large institutions that can afford it, have alternate solutions for web publishing, and who have either in-house developers or can hire good Documentum developers (not the ones who know Java but do not understand ECM). It is, in my opinion, the best heavy duty ECM solution out there, assuming OT is not gutting it as we speak. That is my only hesitation to not giving it a 10, OpenText is an unknown quantity in this and I worry that they will only support Documentum until they have figured out how to fill the gap between Documentum and OT and then offer a migration path to OT with a Documentum sunsetting as an incentive.
It is well suited for medium to large companies that require a tool to allow users to create IT requests, have a self-service portal, track the completion of such requests and have access to KPIs to understand the satisaction level of the requestors. It is not the best tool if you want to have a heavy personalized IT Service Management tool to cater to all your needs or when you want to have an easy way to search for past tickets using specific keywords.
Records management: Compared to other content management systems, this provides a efficient and scalable solution. It gives lot of flexibility in managing the content as Records or Legal holds.
Workflow system has external plugins to connect with FAX, Mail, Database and FTP servers etc. which gives an option to integrate with any system with documentum.
Creation of websites and maintenance is easy. Content authors can create the pages with effective mechanism.
WDK framework has been the biggest drawbacks from the application speed point of view, as well as client complexity and not so natural look and feel. Yes, with the latest releases much of these features are improved.
EMC is very expensive to buy, own and support, where some products require many dependent Docuemntum products to be installed to work at its best.
Finding requests that I opened and have since been completed by the assigned group/individual is very difficult to accomplish unless I've written down the request numbers somewhere.
Requests that I opened and are subsequently closed, often continue to appear in the list of "My Open Requests" giving the appearance that they were not completed when in fact they were.
It may exist, but if it does I haven't found it yet, which makes it less than intuitive, but I would like to see the ability to recall a request in ServiceNow.
I believe our firewall rule change request for is a custom form, but it has a serious drawback. If I submit such a request and need to make a correction to it before it is approved, there isn't anyway for me to do so. The request has to first be rejected with the creation of a sub-task in order to edit it before it is resubmitted for approval.
Stability is a key factor as well as its flexibility. Also, any organization that deploys Documentum will have made a significant investment in terms of time and money, so not renewing its commitment can come with a significant cost. That said, the decision to deploy Documentum initially should come only after extensive evaluation, knowing that once deployed it will likely remain the platform of choice.
To be completely honest setting up a new ticketing system can be a pain in the ass. Once you have it setup and customized the way you want it, you don't want to switch unless you're unhappy with the product. Unless future releases and updates really muck the system up, I wouldn't change.
It has helped us a lot, and after some training and getting to know the product, we are quite comfortable with it and feel much more capable of understanding what's going on in our IT environment. The only reason it doesn't get a perfect score from me is that there is a learning curve for both end users and IT admins using ServiceNow. Once you customize the UI and remove unnecessary fields. You are left with a very clean product that does what it needs to and does it well.
I would give it this rating because we have had no major issues with the support for ServiceNow after we implemented it at our organization. They seem to respond promptly and efficiently if we ever do need to open a support case with them about an issue we are having.
To type in what should be a text box, you have to click an empty cell, a tiny text box pop up opens with a check box and an X. You the. Type in the text box and have to click the check mark. If you have a bunch of fields to fill out, doing this is very annoying. Absolutely know thought went in to this. I'm sure somebody in marketing thought it was a good idea. It wasn't.
Without exception, every client I have worked with has been very happy with their resulting product. While this is partly due to my work, I must point out that the platform is the winning decision, not the implementer.
We used to use Jira to handle service tickets but it's way too robust for something this straightforward. Due to the nature of Jira, you needed to already have a lot of documentation and knowledge about who should be assigned the ticket, so the lift of creating a ticket was time consuming.
After this product, the client is able to manage content security and due to it, the client is able to use the business process, and this really reduces effort and increases the profit in business.
It provides integration with SAP easily which really helps the client to manage this effectively and with minimum effort system is ready to use.
Also searching, automated flows also create a bigger impact and reduce a lot manual effort.
We don't currently have a CMDB, so we are leveraging ServiceNow to build one using their ITSM and ITOM tools. This is a huge gap for us as a company and it will be a big win once this is in place.
The core help desk functions are comparable to most other tools on the market, but SN does a great job of integrating that data with other modules like Problem, Change and Event Management to provide a truly integrated solution.
The tool is expensive, so you will need to try to do as much as you can with the platform. We currently use other systems for HAM and SAM but will be including these in our ServiceNow instance in the future to help maximize our ROI.