OpenText Documentum vs. Pega Platform

What are the document volume, the throughput - currently and expected in year, 3 years etc.? Is the company doing content management on international level, where access from multiple locations is needed - then Documentum can be good investment. What ECM system will be used for - document storage, document lifecycle or retention? Or all of the above? - Documentum works very well if all 3 items are combined, yet for storage there must be cheaper and more easily adaptable solutions available.

Pega [RPA] is good to address a specific business function requirement with not too many bots or automation processes. It takes time and effort to set it up. Though once done, it is very easy to configure and use. One should also run a POC to verify if this product meets the scalability requirements.

Incentivized

• It's good at integration with external systems through standard industry supported APIs, including but not limited to web services integration and file system integration.
• Good support from major up and downstream technologies such as image capturing and back end ERP, Database, and HR.
• Highly configurable.
• Very fast searching capabilities.
• Highly scalable.

Incentivized

• Reusability
• Pega’s Situational layer cake architecture is capable of organizing application to suit enterprise needs. An enterprise can have a complex organization structure located around the globe. Because of Situational layer cake architecture reusing common policies and procedures is easy while allowing for differences between products, regions, channels and customer segments.Whereas with some application development platforms, separate copies of the application should be created to suite different business context.
• Faster application delivery
• With Pega developers can reuse common policies and procedures, replicate functions and industry specific frameworks and utilize pega UI elements to develop applications. IT is easy to deploy.Therefore developers are capable of delivering application earlier compared to some application development platforms. Pega reduces time taken to deliver an outcome.
• Pega upgrades
• Pega platform is upddated to adapt and work with latest technologies.
• Proprietary users support and maintain Pega platform continuously. Pega customer support is always willing to enhance product support.

Incentivized

• Expense. If Documentum costs less it would penetrate more markets. This is often the reason a lighter weight solution is chosen.
• Web Publishing. Documentum is not a great solution for replacing CMSs like SiteCore or Drupal. Probably better as an archiving target for parallel publishing to both web and Documentum. Documentum is also not a web hosting solution like some other systems, it is possible to try and consume directly from the repository in real time but it is better to push web content out and consume from another platform.
• Development. The price of broad functionality is complexity. Arguably, Documentum drank the kool-aid and tried to become like other enterprise solutions by adapting Java, Windows, etc. in the late '90s and it made them slower, more complex in design, and less stable. They recovered from that but it still requires developers with a few years of experience in Documentum to safely develop in Documentum. The issue is not knowing Java but knowing what to do or not do in an ECM system. This is even more important in regulated ECM/RM systems.

Incentivized

• Reporting is not extensive in Pega. Because of this higher management is not able to get the reports which will give them insights into a different area. So Reporting functionality can be improved in Pega.
• Organizations that want to fully use all the features of the Pega 7 platform must follow Pega’s solution development methodology which may not be aligned fully with the organization objectives.
• During upgrades, some of the rules which are deprecated have to be changed to new available rules. This becomes a problem as one has to understand all the functionality and then change a lot of things.

Incentivized

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.

Incentivized

Pegasystems has continued to demonstrate a strong partnership with our organization and investment in their product that aligns with our overall vision and need. Pegasystems has engaged us at every level, with the assistance of minor defects to the overall roadmap planning and alignment of our goals

Pega Platform is enhancing its product and launching new features day by day which help to achieve customers needs. If I talk about the earlier version of Pega Platform (i.e. pega v5 and 6.3) there were many numbers of limitations in Pega Platform and if we need to do some customization then needed to write custom java and jave scripts to achieve the functionally. Now I can say Pega Platform is running with market trends and demand. Pega Platform is giving all the options which support the current technologies like decisioning capabilities, real time processing, mashup, process fabrics etc..

Incentivized

Support is better than with ECM, but could use some improvement.

Incentivized

It’s very slow sometimes, but that may be our servers. Also the Knowledge Library needs some work - again, not sure if it’s our setup or what- but I’m unable to search the body of an article for content, so I have to be very intentional with tagging, but it’s not ideal.

Incentivized

The online training is an excellent one, but still it is missing hands on development.

Implementation is totally depend up on the requirement

Incentivized

Subjective but here's how I see it: Heavy duty (in order of how much they can do and how much they can handle): 1)Documentum, 2)FileNet 3)OpenText Middle duty: 1)WCC-WebCenter Content, 2)Alfresco, 3)M-Files (3rd b/c it is Windows only), 4)Nuxeo (only b/c of its newish approach that may lead somewhere) Light duty: 1) BOX (not an ECM but it says it is), 2) EFSS (pick your poison, BOX is an enhanced EFSS), 3) CMSs (some have some ECM capability, none have much)

Incentivized

We did evaluate multiple products offerings with Pega Platform capabilities and observed that Pega PRPC rules engine and case management capabilities are better over so many BPM Tools. We also conducted a detailed study with developers to identify the best products out of Suite of BPM products. It's observed that Rules engines integration is very streamlined with forms in Pega whereas other tools multiple have powerful data model capabilities but lacks the ease of creating business rules.

Incentivized

• 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.

Incentivized

• Our company has boomed in the past few years because we of how we use Pega.
• We will get a project from a client and the turnaround will be so quick they will throw 3-4 more projects at us.
• Smaller developer teams means less complexity and less overhead.

Incentivized