We just finished a new 6.6 Documentum install for a client and ran into something slightly unusual. During the installation, we were not able to install a workflow template from an existing archive, a routine install activity. In the past, we could always move workflow templates between repositories using Application Builder and Installer and create new templates with Workflow Manager. While Documentum Application Builder and Application Installer became unsupported with the release of Documentum 6.0, Composer was introduced as a replacement. Up until recently, Composer supported the archival and deployment of workflow templates. Most of our Documentum clients were surprised to learn that the 6.6 release of Composer does not allow workflow templates to be archived without having Process Engine, a component of the Business Process Manager (BPM) suite, installed in the repository. This post will discuss this issue, as well as our thoughts on possible future Documentum licensing around workflow tools.
The Documentum object model and the Alfresco content model have many similarities. Both software packages have the concept of library services (check in / check out), a data dictionary, and a hierarchical data model however implementations do differ.
In Documentum, administrators can create or alter custom object types with the use of Documentum Administrator, Composer, Application Builder, or DQL or API scripting. In Alfresco, there is one common way to create a custom type, including any constraint or pick list values. The configuration to create a custom object type includes creating a custom model Spring context file, a custom model definition file, and a custom web client configuration file. Continue reading
TSG is responsible (well, actually just Ellen and Bethany) for coordinating the Midwest Documentum User Group (MWDUG) (http://www.mwdug.com) meeting held on April 9th. In talking with some of the attendees, we all agreed that it was one of our best meetings with over 100 attendees. We even had a big group of 8 fly in from Atlanta for the meeting. Some of the traits that make for a successful MWDUG meeting:
- User Hosted – PWC hosted in a great classroom facility with well over 200 chairs with desks. (thanks for coordinating Laurie!!!!) In the past we have had BP, United, Takeda, Exelon, Pepsi and others host with similar facilities where users can spread out and take notes.
- User Presentations – The meeting is only as good as the presentations. We will typically have EMC present on one important topic but users love hearing about interesting things other users are doing. Many users volunteer and enjoy sharing and receiving input on their solutions and approaches.
- User Dialog – Ellen and Bethany have done a great job in the last two meetings presenting survey results and then present in more of a facilitation mode to get users talking and sharing. Introductions as well as a long lunch are typically scheduled to allow users a chance to mingle.
First released with Documentum 6, Documentum Composer is a “unified development platform for assembling, configuring, and deploying EMC Documentum applications.” Currently on version 6.5 SP3, Composer is meant to be a Documentum Application Builder replacement. Although Documentum is trying to move away from Application Builder and into Composer, Application Builder is still available for use with Content Server version 6.5 applications through the use of Application Builder 5.3 SP6.5.