EMC Momentum Vienna 2012: Documentum D2 and Mobile Roadmap

David Le Strat answering questions during Q&A

They started by defining what the New User really means:

”Clean, modern UI, access to info everywhere, on any devices, and wirh diversity of content types”

The move to D2 was because a realization of a more agile process away from traditional coding practices and towards easy instant configuration. As in Vegas people pointed out that it is not just about configuring the user experience but also a rules engine for content. One reason EMC acquired D2 was a realization that customers didn’t fit in the previous product boxes like knowledge worker, rich media, process etc. David also introduced an explanation  of the difference between D2 and xCP which I think is the best yet:

xCP is configuration for ”design-time” while D2 is config for ”run-time”

The message was also that the usability that we all strive for comes when the UI is easy to use but also very easy to configure to different user’s needs. Today version 3.1 of D2 is consider the Power User tool but the plan is to move all these features gradually to 4.x releases of D2.


Rich Media viewer aligned with xCP is planned (showed video preview with collection objects in a lower bar) as well as some Centerstage features.

Ver 4.1 is planned for Q2 2013 and include the following features:

  • Advanced search with facets
  • Virtual document editing
  • Native annotation (just basic – still a place for 3rd party tools)
  • Syncplicty and mobile integration
  • Extended widget integration
  • Rich text comments
  • Advanced property inheritance
  • IRM integration
  • Custom menus
  • Administration widget
  • Public API for integration into external zoos
  • Distributed administration

When it comes to partner integrations things like the Brava viewer is supported in 4.1 and I think both an Active-X and HTML version of it.

Integration of the Euroscript reporting tool was also highlighted which of course make one wonder what the status is for Crystal Reports in the future. Earlier we saw a demo of Euroscript which featured reports in widgets that changed when interacting with other widgets in the UI.

Future D2 releases:

  • Personalized home page
  • Ability to package components in xCP as widgets for D2
  • Data tables

When it comes to mobile in the short term:

  • iOS 6 platform support
  • Support for iPhone 5 (form factor adjustments)
  • D2 Workflow config in order to support electronic signature signoffs and adding notes and comments to a workflow task.

In the longer perspective they see mobile clients both leverage D2 and xCP configuration. Clients based on HTML 5 for multi-platform support. The ambition is to have mobile clients fully integrated with information management and governance.




EMC Momentum Vienna 2012: Public Sector

Tuesday at the conference was divided into three industry tracks: public sector, energy & engineering and healthcare. In addition to that a developer tracks and two unnamed ones. I choose to attend the public sector track for the first and last session of the day.

The day kicked of with Ronnen Ronnen who is the Vertical Solutions Director for Public Sector in EMEA. His session ”Public Sector trends and vision” was an overview of the issues and trends in our area. The main features of his speech were:

  • eGov Mission Statement
  • Public Sector Challenges
  • IIG Strategy
  • Moving to Solutions

The main keywords for public sector seemed to be: services, processes, streamline, efficiency, simplification and re-engineering gov processes. Shrinking public sector budgets and needs to cut costs in IT seemed to be an important rationale. Depending on how you interpret things it seemed to be an IT perspective – minimize costs but what about deliver new capabilities rather than cheaper existing ones? Priorities for the public sector from this IT perspective was stated to be:

  • Data protection
  • Organisational restructuring
  • Administration change
  • Improving services delivery
  • Handling economic constraints
  • Regulatory compliance

To me it seem important to distinguish WHAT measure you take from the underlying reasons WHY you them. From an IT perspective there is a risk of just focusing on delivering what we do know or at least they way we work now in a more cost effective way. I wonder for how long it will be enough not improving what the business do while doing it more efficiently. It boils down to how big of a picture you want or can take. Is it just IT meaning boxes and software or  is it a more strategic take on how the organization does its business?

However, somethings need to be focused on the IT-perspective and relates to the actual ability to support the business with new IT-support, the time to market aspect is crucial not only to save money but also to make it in a reasonable time frame from the business perspetive. Ronnen summarized it like this:

”Sometimes the time to market is so long that when you deliver the people initiating it are no longer there”

That means a requirement to move to a more agile development process and of course the way Doumentum xCP is heading reflects that. They claim 5-10 times faster development cycles which really addresses these challenges. Other trends that adresses the challenges are:

  • Cost optimization
  • Alternative delivery models (cloud)
  • Shared services
  • Outsourcing
  • Joint private/public
  • Mobility
The afternoon session was labeled a roundtable session but unfortunately quite few people showed up in a fairly large room. That meant that some of the intensity of a big crowd was lost. We got an introduction from Ronnen followed by two customers talking about their experiences. Hong Kong Civil Service efficiency unit was interesting. He shared with us the current situation in Hong Kong where they have not been able to hire new civil service workers for the past 10 years. That means that the age structure is critical with around 50% of the workforce being over 45. In Hong Kong people can retire between 45 and 60 which means that a lot of experienced people will have to be replaced with young people with little or no experience. Preserving knowledge and best practice then becomes a key thing to do. They have chose to use EMC Documentum Centerstage to store all these SOPs and best practices and declare them as formal records from there. The idea is to move from a situation where these documents are spread on local computers and file shares into a centralised but sharable architecture. After all the goal is to support all these youngsters with information they need to continue to provide civil services to Hong Kong citizens. ”Put information at work” was a term he liked to use.
Finally I like to mention a slide that Ronnen showed which was a pie chart outlining that 94% of the costs (that can be saved) are found in the processes rather than IT and software. So optimizing the way we work is the real way to save money and of course at the same time do more or better work.


EMC Momentum Vienna 2012: D2 + solutions exhibition

Documentum D2 4.0 Tutorial

Documentum D2

Monday afternoon was spent on a tutorial around Documentum D2 and the new 4.0 version. The new UI is very nice and would make it much easier to demo Documentum without excuses around its UI. As usual it is very impressive to see so many things being able to control from its configuration interface, hit save and it is available to users without a restart of anything let alone the whole server. Since we are running and R&D-activity this will it possible for us to try new concepts and settings out much much faster. However, today I discovered a few limitations in the current release. One is that the structure (layout) of a workspace need to be configured using a plain old XML-file. Sure it is far better than compiling and editing XML is not that difficult but still it will slow down development slightly. Fortunately a graphical interfaces is under development. That workspace structure file is then imported in the workspace configuration interface. Another limitations is that external widgets has only one-way communication which for instance mean that you can use coordinates in document metadata to position a map but not use the map as a search criteria. Support for two-way widgets is also under development and planned for the next release.

I look forward to see support for virtual documents and more collaboration widgets from Centerstage in the next release. As of now I at least spotted a widget called ”CenterstageCommentWidget” in a drop down menu. I also like that nice large dynamic document previews are built with an option to go full screen just as Centerstage (and Alfresco Share). Another nice feature is that all lists for documents or audit events can be exported as Excel files.

fme Migration Center

Also had a chance to look further in fme Migration Center which is a really powerful enterprise tool that I see can solve several business problems for us. The most obvious one is of course supporting migrations between systems and during upgrades. However, it can also be used to support large imports of content from file shares, USB-drives etc. It includes powerful regex features to set filenames, metadata and folder structures in the target system. The product requires an Oracle database to run but for smaller migrations up to about 500k they seemed to think the Express Edition could be a choice for those on a budget. Another powerful features is the ability to set up a migration path and then run it in simulated mode with no commits to the actual repository.


EMC Momentum 2012 Monday: Introduction to Intelligence Capture

Automated Document Classification

Monday at Europe’s Momentum conferences are devoted to a partner conference (which is closed for customers) and some Fundamentals sessions for us ”normals”. I choose to go to the Introduction to Intelligence Capture by Sean Bird mainly because enterprise capture is an area which is something I think I need to look into more. In our project we have focused on Documentum and ECM but leveraging Captive as weel seem to make sense. What strikes me is that paper is still around and that is something I see everyday at work as well. That way citing a 4 year old IDC report around issues with paper-based document management makes sense. Laurence (Word of Pie) reminded me last EMC World that we still produce digital content, print them just to scan them back into another system. Sean pointed out that scanners today is a proven technology but it actually took a while to get there.

EMC is a bit unusual as a company I think in they way it approaches other vendors and realizes the legacy IT environment. Some companies are almost religious in not mentioning other vendors at all and insist that their products are the only ones. Sure, EMC promotes their software portfolio and is getting much better in putting an effort into integrating their own products. Still they are very open to provide adaptors and plugins for other vendors which I think is great for us customers. It makes it somewhat easier to mix products based on our needs and have EMC supports us in that approach instead of constantly trying to promote their own stuff.

A thing that was new for me was that EMC owns the ISIS (Image and Scanner Interface Specification – ISIS) through Captiva. I also learned a new abbreviation this morning and that MFP (Multi-function Printer) and in plural MFPs of course.

This week in Vienna EMC will announce Captiva 7 which includes:

  • New integrated agile development tools
  • Improved intelligent extraction and classification technologies
  • An improved user interface.

Gearing up for EMC Momentum 2012 in Vienna

It is early Monday morning here in Vienna and I felt it was time to write a little summary post just on the brink of this years’ EMEA Momentum conference. This will be my third EMEA conference (attended Prague in 2008 and Berlin in 2011) but I have also been to five EMC World conferences, the last one in May this year. For me these conferences are something special since they are a unique opportunity to be around people caring and knowing about Enterprise Content Management. Customers with interesting problems but not the least people from EMC IIG Engineering who I have had so many great conversation with around ECM and Search. In my project we have some unusual requirements which are usually met with surprise or even skepticism by IT people, but usually not from EMC Engineering which is just great. EMC is not a perfect company but this provides a setting why I really like coming to Momentum every year, it is a vital place to recharge my innovations spirits. I have also been fortunate to share some experiences from our project as a speaker. So what do I expect from this years conference then?

First let me start with arriving in Vienna today. Just outside the entrance from baggage claim there was a nice booth welcoming us and providing us with guidance on how to get to our Momentum coaches. I think this is a nice touch that makes the trip more ”seamless” to use some Apple language. It is not something I am used to from EMC World but on the other hand those conferences have grown to 15 000 people nowadays. I snapped a photo of the Momentum crew in the arrival hall:

Momentum Staff in the arrival hall

Somehow it seems that the excitement this years is a bit higher than I am used to. Naturally I need to mention this blog post by Brilliant Leap that really gets the expectations flowing. Jed Spinks have even created an application in Documentum xCP to manage his Momentum information and let us access it. It seems that people expect that it will be a major launch during the event which of course that even CMS Wire will write something about Documentum 🙂

I agree that xCP version 2.0 will be in focus and rightfully so. It is way cooler than what most people (especially outside the IIG community) understands. I really look forward to see a stable version with all the major tools and interfaces integrated. Which brings me to the area I will cover most thoroughly, interfaces and end user features. I really, really hope to see good progress towards one unified user interface architecture and if they could merry D2 and xCP ExtJs-based interfaces would be great. However, I do hope that some Centerstage and some DAM/Media Workspace features finds its way to the new interface as well. As noted during EMC World I can’t get my head around why EMC IIG does not make that more of a priority. Documentum has the architecture to handle massive amounts of images and video and now when cameras and smart phones are everywhere there is an opportunity to provide ”Flickr for the Enterprise” and ”Youtube for the Enterprise” using Documentum. Make it fun and easy to manage rich media!

I also need to mention Next Generation Information Server (NGIS) as well. Jeroen’s thoughts around this is music to my ears but it would be nice to see some real progress in this area as well. At EMC World we got the message that NGIS was mainly focused on the cloud (OnDemand) side of IIG business while Documentum 7 would be the on premise way. However, mechanisms to easily move code from xCP in D7 to NGIS was a priority. I wonder if we could see some roadmaps on making NGIS the new unified architecture or maybe I am just dreaming? I really would like to run NGIS on premise on our project anyway.

Integration of other EMC software is another area of excitement and expectations from my side. First and foremost VMWare of course which seem to make the whole business of deploying and running Documentum something completely different than what we are used to. Not just virtualisation but also their custom tcFabric Tomcat application server is really interesting. RSA technology would be nice to see more and of course my favourite in the social area, Socialcast. I really want to see Socialcast being integrated both on the platform side as well as a the main way of providing activity streams inside xCP.

Well, that was some of my thoughts. See you at the conference and follow me on Twitter (Tweets posted here in my blog to the right).


Momentum 2012: Documentum xCP 2.0 – Learn from early adopters

The new thing this year is public and private cloud when it comes to Documentum and xCP. It took a while to release xCP 2.0 because they want to have a future-ready architecture.

Principles that have been used when designing xCP:

  • Open – ExtJS and Spring Java Framework
  • Performance – old Taskspace had some issues with performance
  • Unified tooling – support standard source control for team development
  • Cloud ready – embrace VMWare technologies
  • Future-ready so customers can move from on-premise to cloud tech later on.

Complete application debugging

Key innovations:

  • Stateless processes
  • Unified expressions and context data models
  • Oneclick application deployment from xCP Builder through xMS. Instructions is called a recipes. Driver information and connection string for the database is provide deployment time.
  • Easily extended GUI where you can inject HTML and Javascript directly into UI Builder

XForms could not be customized design time because of the Forms engine. Had to be redesigned.

The performance of the stateless engine is really good – can more or less act as a real-time data source. Useful when designing responsive UIs.

xCP generates .war .dar and config-files into an application package

Customer experiences from Streetworx Contract Lifecycle Mgmt:

3 weeks development time for the application.

Builder is quite different from xCP 1.x tools with many new concepts. Documentation is in progress and tools is in process.

Possible to create relationsships between an object representing a contract and an object like a milestone. Powerful abstractions.

They liked that xCP has Web/Enterprise 2.0-style GUI.

No more jumping between the tools which is nice.

One button deploy/test in one tool leads to rapid development.

Changes are propagated throughout the environment.

HTML in widgets is appreciated since it enables a finer control of the UI.

Stateless process:

– no more adaptors

Define input and output and map them to widgets on your page. You can do much more than a single DQL query without having to write a custom adaptor

Result lists are vastly more powerful than 1.x read-only tables

Tritek experiences

Said it was important to not look at xCP 2.0 as an incermental release – it is more major than that.


  • New Process Templates are unvoidable
  • Business Objects take the place from Structured Data Types
  • Old artefacts cannot be imported directly into xCP Builder

Leverage rich widget-based UI with ExtJS and the spring framework for agile solution delivery.

  • Future is case management, xCP UI is very, very good at case management use cases!

Big change was moving from structured data types to business objects

  • Business Objects are like packages, presistent objects that represent case data
  • Big advantages to persistent data
  • Simplified DQL relationships

Big challenge for custom apps: No DFC equivalent for BO to replace SDT access

Large long-running workflows do not take advantage of xCP 2.0 features.

GA for xCP 2.0 is Q3 2012 – the time as D7

In xCP 2.1 they will have an importing feature that will upgrade some of the artifacts

the degree of manual vs automatic migration is not yet decided.

There is a technology convergence between D2 and xCP user interface technology.

Will there be a developer edition? Not yet decided.

The purpose of xCP is a targeted application which is specific which is different from the existing horisontal mobile application such as Documentum Mobile.

The web application will work on web browsers in mobile. Took out flash, active-x etc which makes it possible.

Possible to generate a set of services and then hook that up to a mobile application which is purposebuilt using iOS or Android.

xCP requires Documentum 7.


EMC World 2012 General Session – Keynote with CEO Joe Tucci

A record setting 15000 people at EMC World this year meant that the keynote session was bigger than ever. Designed around a space/scifi theme by CMO Jeremy Burton it was really impressive to see. A giant continuous curved screen covered the whole front of the area.

CEO Joe Tucci talked about his view on the radical shift in computing we see right now. Moving into a cloud era which he think is a bigger shift than any previous.

Followed by Pat Gelsinger the focus was as usual around things that make noise – big boxes. Not a word about IIG and Documentum in the keynote basically. A bit sad because it is seem to be a general issue that ”traditional” IT-people only care about what is below the database. Unfortunately it is also the stuff that business people understand easily. Things that make a noise and you can touch. More abstract things like metadata, processes you find in enterprise content management seem to be harder to get and definitely harder to touch. Maybe not as sexy as big sic-fi looking boxes with huge hard drives either. A good show it was though.


Momentum 2012 Session: Documentum Architecture with Jeroen

The Documentum stack is huge so this will be an overview. This more slide-oriented whereas the innovation track will feature more demos.

The Big Picture

Walks us through the stack based around different repositories

Model of the metadata on top of data. On the side of the slide you see a stack of supporting components he calls the ”I/O Stack”.

  • Multichannel Publishing (DocScience) 2way
  • Unified Analytics Platform (Big Data with Greenplum) 2way
  • Capture Services (Captiva) 1way
  • E-discovery services (Kazeon) 1way

Move away from coding into configuration is the main goal.

Content Server focused on on-premise deployment (SOAP/REST) – single-tenant.

NGIS in the cloud where it is focused on REST – multi-tenant.

Second server architecture for the public cloud. Why? He sees different demands for public cloud.

The aim is to provide a multi-tenant solution where each added tenant cost as little as possible – preferably just another object.

For cloud D2 is first and xCP will be made available on the cloud later on.

Should be possible to design for the current stack – run it on the public cloud stack later on.

The mechanism for the transfer is XML – formalising the application model.

He has talks about a hybrid scenario – content supply chain – manage the extended enterprise with all suppliers as the use case.

D7 Performance Improvements

  • Talking again about improved context switch performance
  • Cache management has been improved -> Lower Memory Usage – Focused on Type Cache mainly
  • Improve the number of active sessions you can handle
  • Improve the response time
  • Reduced the number of sessions on Oracle database

Will affect the number of Content Servers needed as well as database deployment. Drasticly reducing the number of sessions needed to support a certain number of concurrent users as well as almost not affecting response times 0-500 users. Again shows impressive charts where the scalability of Documentum is much more linear than before.

REST Strategy

  • Big effort of implementing REST across the board
  • Pure REST approach (must support XML, JSON and Atompub)
  • Do not see it as an API but rather a design paradigm
  • REST as SOA Strategy
  • Discovery of services using resource linking
  • ns.emc.com for describing web concepts
  • Connecting resoursces accross products

The request service layer is an abstract layer.

New initiative called Linked Data Platform – Co-chair of the working group with IBM

REST and xCP – REST services provide access to xCP resources

xCP clients also use platform resoruces such as Folders, Documents and other Documentum types.

xCP clients consume xCP and platform serviecs.

Project Line of Sight

It is about Hyperic and the Documentum stack.

Immediate focus areas:

  • Enable monitoring Documentum products famialies
  • Linux and Windows
  • 6.7 SP2 onwards


  • -Captiva, DocSCI, Kazeon and other products
  • Provide data analytics and corrective actions enablement

Linked to the bigger initiative with xMS – a new approach to deploying Documentum.

Automated process to instantiate the complex deployments. Not only initial deployments but also upgrades and patches.

Each machine has an hyperic agent that connect to the Hyperic Server where the monitored data end up and can be consumed by he Hyperic Portal where you can:

  • Monitor
  • Discover
  • Alerts
  • Correct

Immediate targets:

  • Health and availability metrics
  • Diagnotics and logging info
  • Alertss and notifications


  • Documtum platform (CS, BOCS, ACS…)
  • XPlore and Webtop
  • Supports 6.7 SP2 and onwards

Reflection: What will become of Reveille’s Documentum products? Is there an overlap?

xPlore and Federate Search Services 2

  • xPlore 1.2 released Q4 2011
  • Customized Processing (post-linguistic analysis using UMIA customization)
  • Tokens are indexed based on different languages
  • Since xDB is a schemaless database means that you can modify the datastructure with any model changes.

Have phased out FAST – 1000 deployments with xPlore now.

Federated Search Services extend the reach for search. FSS does not index – it provides access to other indices.

D2, the power of configuration

The concept of D2 – The power of runtime configuration. The idea is to be able to combine a subset of users with a subset of content and apply a configuration to that intersection. That becomes the context. EMC has seen a lot of common patterns in Webtop customizations. Better UI if you can trim it down. Makes it possible to have a very targeting user configuration.


Rapid Application Composition (not configuration as D2)

Integrated set of tools to provide that. Actually means that there will be implications on all three types of users:

  • New User (D2 and Mobile for instance)
  • New Application Developer (Information, Process, External Systems, Analytics Modeling and the Composisiton)
  • New Administrator (xMS m.m.)

Defines a semantic model of the application. From that we generate an optimised runtime. Generates domain-specific REST Services.

xCP and the stateless BPM engine is mentioned as a big thing at this conference as well. More about that in the xCP session.

Big Data Analytics

Possible to integrate with Greeenplum in xCP 2.0 without any modifications. Works through JDBC Data Services configured in the xCP Builder that connects with Greenplum UAP.

The integration with DocSci is with Web Services.

Example of an insurance app where data is feed from a car devices monitoring driving behavior. Data is used to crunch large amounts of data into driver reports being output by DocSci and new insurance rates to be applied to the driver’s insurance.

The process defintion can be configured to interrogate the Greenplum Engine.


Always Impressed by the Scale of the EMC World Dining Hall

Impressive, no other word for it. A story to tell people back home in Sweden. Had a recent experiences at a party where it took 200 people over 45 min to get food from a buffe. Here at EMC World the Dining Hall is just amazingly large. I mean serving breakfast to over 10000 people in an hour. Do the coffee come in pipelines and food in endless lines of trucks outside. I don’t know but it is way cool.


Momentum 2012 Session: The New Documentum D2

Here we go, the first session at Momentum 2012 at EMC World 2012 in Las Vegas. After breakfast in the enormous Dining Hall we gathered in the Momentum area of the conference for the first session around newly acquired Documentum D2 client. Responsible for the session were Brian Roche and Boris Carbonelli. Peggy Ringhausen is also working with D2 and was present at the session.

The main goals for this project are:

  • Respond quickly
  • Deploy easily
  • Delight Users

The overall idea is to compress the time from inception to roll-out to end users, something Documentum users has not been used to especially from the WDK era. Sure WDK was a great (even price-winning) technology of its time but we grew accustomed that even small customizations of the user interface took many days of development and required recompiling the application or at least restarting the server. That has all changed now.

New in EMC Documentum D2 4.0

  • Cross-browser Support (all the major ones)
  • Workspaces
  • Themes
  • Widgets
  • Cross repository search
  • Open Simultaneous workspaces
  • View Centerstage Spaces

There is a set of fredefined workspaces  but you can also create your own with drag and drop widgets from the widget gallery.

Customers thought it was important with themes so that was included in this release. Very easy to change and modify themes without restart.

Interface is based on Googe Web Tool (GWT) which of course makes me wander about how the convergence with the ExtJS-based interfaces will look like.


D2 do not use UCF for content transfer instead there is either a D2 Applet or a D2 Branch Office Caching Services (BOCS) plugin that does the job. That of course also means that Java needs to be installed on client machines. D2 is also available in the EMC Ondemand solution.

Just as their CTO Jeroen Brian promised to do less slides and more demo so after a 15 minutes or so it was time to fire up the doing on a Macbook. The demo of the user was made in Safari whereas the admin and configuration stuff was run in a virtual machine inside VMWare on that Mac.

One thing that I enjoy with Documentum Centerstage is that it restore sessions and similarly D2 restores the interface just where you left it. It is a vital approach to lower the threshold for how users quickly can get back to work by picking it up where they left it.

Workspace Gallery include a set o predefined workspace which contains different widgets depending on the targeted user category. Things like:

– Consumer

– Contributor (full, preview, vertical)

– Web

Very fast browsing which is nice. Autohide of the menu and he could easily group documents by status. You can also go full screen directly from thumbnail to show slides or full pages. I wander what the default size of the renditions are set to. Need to be big enough to actually avoid firing up Powerpoint or Keynote.

It seemed very easy layout configuration of widgets, just drag them around to where you wanted them.

There is a new Centerstage Browser as a widget which is great I think. I think it is wrong when certain type of contextual information about an object can only be viewed in a certain client. Different presentation of course but not different information in different clients.

The also have a new web widget to show web pages inline in D2. Google Gadgets can be included which means that there already are a catalogue of things to start from. You can also interact between Google Gadgets and widgets in D2.

It is possible to configure what widgets made available to users not only available workspaces.

Did a demo where he apply watermark upon download of file to computer. Changed the setting for the watermark, hit saved and showed the same watermark again with no restart. Cool!

D2 Config is configured using a Matrix which to me looked a bit strange at first.

The horizontal Lines contain rules whereas the vertical Columns define in which context to apply each rule. Behind each rule for instance lies complete configuration options so the interface initially looks like you can’t do much but the configuration options are huge.

Show how easy it was to create a new tab and show a new field with an attribute with a drop down menu which can be populated through Dictionary and DQL

No server restart – no compilation required. Applies for visible metadata or style of water marks. Themes can be switched runtime.

Internal widgets are those coming with the product and external widgets (develop yourself or use from internet like Google Gadgets.

Demoed how to search for Gadget using the tools search, inserted the widget URL from the Gadget and used it in a workspace.

Also workflow information is available as widgets in D2:

  • Workflow
  • Browser
  • Task lists
  • Task Details
  • Attachment
  • Notes
  • Performers

No workflow map as of now.

Besides watermarks headers and footers can also be applied dynamically upon download

D2 4.0 is scheduled is Q3 and after that there will be a release every 6th months according to the current release schedule.

There is another product called O2 which is used to transfer MS document properties to and from the repository.