We have posted recently about a variety of email solutions including leveraging IMAP as well as issues with drag and drop functionality leveraging MyDocumentum for Outlook or Webtop. This post will review the use of the “forward” button to provide an email client neutral approach for ingesting emails into Documentum.
Continue reading ‘Documentum Email Integration – A Simple Approach’
Archive for the 'OpenInterchange' Category
Documentum Email Integration – A Simple Approach
Published August 9, 2012 Documentum , Migrations , MyDocumentum , OpenInterchange , OpenMigrate 5 CommentsTags: mobile
Documentum, Mobile and IMAP – A standard and open source approach for email archiving and mobile access
Published May 31, 2012 D6.5 , D6.7 , Documentum , Documentum Client for Outlook , IMAP , MyDocumentum , OpenInterchange , OpenMigrate , Webtop 1 CommentTSG has started initial research and development on an alternative approach for email archiving and mobile access with Documentum, based on a client project that utilized Alfresco IMAP. In prepping for our client briefing next week, we thought we would share our initial thoughts on an IMAP and Documentum approach. Continue reading ‘Documentum, Mobile and IMAP – A standard and open source approach for email archiving and mobile access’
Documentum Client for Outlook (DCO) – A cautionary tale in regards to message formats and object types – comment if you have experience to share.
Published January 31, 2012 D6.5 , D6.7 , Documentum , OpenInterchange 10 CommentsWe have two clients that are struggling with the combination of email formatting as well as the Documentum Client for Outlook (DCO) regarding format and different releases. TSG doesn’t see a ton of DCO or email implementations so we thought we would share our client’s experiences here. Please comment if you have any DCO experience to share.
Enterprise Content Management Strategy and Service Orientated Architectures
Published December 2, 2010 Alfresco , Documentum , ECM Landscape , OpenContent , OpenInterchange 1 CommentI had a good conversation with an active TSG Blog reader this morning that I thought was worth sharing. The topic was on how best to leverage an ECM strategy for a life sciences company that is moving away from their first ECM platform and trying to map out the strategy going forward.
Continue reading ‘Enterprise Content Management Strategy and Service Orientated Architectures’
Documentum, Alfresco and Email Integration for ECM
Published April 7, 2010 Alfresco , Documentum , HPI , OpenInterchange 1 CommentTwo current clients are adding significant inbound and outbound email capabilities for their Document Management systems. To start with, this is not an email archiving solution where they want to capture all emails for later retrieval. One, a Documentum insurance customer, is looking to add the ability when looking at a document to easily email the document out of the system, and capture the email and audit trail activity in the related claims or policy folder. The other customer, an Alfreso manufacturing customer, is looking for similar functionality associated with project folders. For this post, we will share some of the details as well as preview functionality in the upcoming release of HPI and OpenInterchange.
Email and Intelligent Folder Processing
One common characteristic of both clients is the desire to work “at the folder level”. For most Documentum Webtop customers, this is difficult as users can create ad-hoc folders and customizing Webtop to add intelligence to certain folders can be complex. HPI, originally built for an insurance client, was designed with folder processing in mind. For example, when a user is viewing a document and selects “email document”, the application will:
- Append specific attributes to the Subject or Body of the email (ex: Policy, Claim, Project #)
- Store the email in the folder along with a link to the document
- Store an Audit Trial entry in the folder audit trail that an email was sent
The application also allows for an email to be sent without any document attachments from the folder with the same email storage and audit trail entry.
Why not just use Outlook?
Both clients spent some time considering through the option of “just using Outlook”. A couple of common issues with Outlook included:
Continue reading ‘Documentum, Alfresco and Email Integration for ECM’
Documentum Client for Outlook, Notes Connector, iPhone and other thoughts on Content Management and Email
Published December 4, 2009 Alfresco , D6 , D6.5 , Documentum , ECM Landscape , HPI , Open Source , OpenInterchange , Tech Tip 2 CommentsTags: Alfresco, Documentum, Documentum 6.5, Webtop
One of TSG’s manufacturing clients is currently evaluating Alfresco for control and management of project related documentation. (Proposals, CAD, Specs….). In working with the client on proof of concept efforts this week, we came across a typical requirement for storing email and attachments easily within Alfresco. In the Documentum world, many of our clients typically choose the Documentum Client for Outlook, Notes or some other 3rd party product that integrate within the email client. For the manufacturing client, the requirements and approach was slightly different.
What about my iPhone?
Blackberry, Palm, Web-based Email, Gmail and iPhone, along with all kinds of other connectivity offerings for this global company, are all part of the equation. It wasn’t really an option to pick one email client and offer integration from only that platform. Also, from an IT perspective, integration into a desktop application like the Documentum Client for Outlook requires additional desktop support (not a positive).
‘Email Mode’ versus ‘Index Mode’
Another point consistent with the different email platforms was that a person in “email mode” was just looking to work through all their emails (first thing in the morning or after lunch) and didn’t really want to stop and index items into Documentum or Alfresco. Notes and Outlook connectors, even with swanky drag and drop, can still require specific attributes (Client) and detail about files (what is that attachment?).
Consistent Indexing
One last point is in regards to the logic/screens behind indexing. Does it make sense to have one indexing applications for emails, another for regular documents and perhaps a third for fax or scanning? This is particularly true when custom lookups (client, job number) might require logic to look up and insure indexing is correct.
Easy Solution – How about the Forward button?
An elegant solution for the client was to leverage the Forward button from whatever email tool (iPhone…) to forward on the email to alfresco@client.com. This way, we could technically say that email integration was available from any email device and kept the user in “Email Mode” rather than jumping into index screens. A back-end process would monitor the email box and, based on the user id, place it in his (or another group/individual) workflow inbox for later indexing. The client also liked the idea of blind copying (BCC) the alfresco@client.com to save content and email threads going out as well.
OpenInterchange was built as an open source tool email tool for Documentum with this approach in mind. By leveraging HPI for consistent indexing and some slight tweaks for Alfresco, the client was able to:
- extend email ingestion to a any email device or platform
- stay in “Email Mode” and save indexing for later
- Avoid desktop integration
- Have one index application
- Save $$$ by leveraging Open Source
If you have any questions – please contact us a http://www.tsgrp.com/forms/contact-us.jsp
