The two interface types EMC Documentum really put their focus on are D2 and xCP.
In this blog I will give my first impression about the paradigm of xCP.
xCP relies on eclipse and uses a lot of the concepts that are well known in eclipse. (a Java development platform). The focus of the configuration is still the same as the old version: you create forms (pages) per action of objects that will be shown based on the step in the business process or independent actions performed by the user. New in this is the business object concept. In the old xCP you created containers (often folder) to store information about the items that are managed in the solution (like a contract or a client). Now the whole new xCP really has a business object that is defined as a object that does not have to be within the archiving structure. This really separates the business operational logic with the archiving structure.
An other important change is the concept of the interface. In TaskSpace the interface was standard and you could set some properties (if you want to avoid any WDK development) to show a different logo and color. In xCP2 you define an application master page just as you do in PowerPoint. Way more flexible.
Last but not least you see the use of relations between business objects. Already a basic Documentum functionality but never used in xCP.
My first impression is simply put VERY IMPRESSED. As my vision is that Documentum should be the repository for enterprise important documents that need to be controlled on an enterprise level, you need a tool that gives you the possibility to demand ease of use but structured and control. xCP 2.0 gives you just that.
Cannot wait to play with it on some serious projects.