Many times, TSG will get involved with clients that have strong developers on staff that come from a database development background and are unfamiliar with the capabilities of Enterprise Content Management (ECM). As database systems expand from just the data to add related documents, the database paradigm approach will typically lead to database entries with […]
Many of our clients have improved the user experience for their document management systems by implementing our HPI (High Performance Interface) application. And while HPI’s first deployment used the Documentum implementation of OpenContent, its architecture also allows it to run on top of OpenContent for Alfresco.
Currently many clients import photos into their case management systems by transferring digital images via a USB connection to a computer and then uploading them through a traditional content management client application. This post will discuss how to enable clients to leverage smartphones for a better experience.
TSG has recently released a detailed whitepaper on Documentum and SharePoint Search Alternatives. The complete paper is available on our website in the downloads section. This post will share the summary conclusion.
We have recently completed a project to create a single search interface to retrieve both Documentum and SharePoint content. This post will present a high-level overview of other SharePoint search interface alternatives and why we chose the integration approach.
Recently we visited a client that wanted to add links to Documentum documents to SharePoint. While the first solution was mostly “out of the box”, the client had TSG build a pretty innovative solution. For this post we will discuss the problem, initial solution and long-term solution for adding links to Documentum documents in SharePoint.
TSG is currently in the process of creating a version of the Active Wizard that will work with our own OpenContent web services. Using OpenContent will allow Active Wizard to work with any Content Management System that OpenContent supports. This means that Active Wizard implementations will be supported on a number of repository types (ex: […]
Our next release of the Active Wizard will be 4.0, and it will mark the beginning of some big changes for the Active Wizard. Our overall architecture direction is to move to a web services model based on OpenContent. While this change is more of a back-end update that regular users won’t notice, it will […]