The xCelerated Composition Platform version 2 is nearly a new development. There are so many changes between the first and the second version. Some features are not compatible to the old version. The following table displays the major changes including a small description.
Structured Data Types
* Business Objects replaced SDT
* BO are flexible, have relationships, events and are persist after the process completes
TBOs will still supported but unnecessary
* old WDK will be unsupported
* new ExtJS interface
* RESTful Service interaction
* Browser independent, becasue GUI based on HTML 5 (best performance with google Chrome)
* Adaptors from the FormsBuilder are not longer supported
* Data Services will be used
they are more flexible (realtime, historical/ external) Queries
* Taskspace not longer GUI of xCP
* Native xCP viewer
* Zero footprint technology on all Browsers and Devices
* Big Data Services with Greenplum
* Syncplicity (data synchronization between many devices and the repository with permission sets for each object)
* easy connection to additional EMC Products (Captiva 7, xPression , etc)
The ProcessBuilder Debugger the will not be included in the 2.0 release. Dan said on the Momentum this year that the Debugger must be completely rewritten and this will take some time. But the deployment on the test environment is very fast and should not be a big obstacle.
Personal impressions of EMC’s hands-on LAB in Vienna.
The second lab session called “Advanced” on wednesday, 7th November 2012 was a deep preview of the new xCP user interface.
The new interface of the xCP Designer
The xCP Designer is the new unified tool to build applications on top of the Documentum 7 environment.
The xCP Navigator
The Application Settings includes Model, Role, Parameters, Endpoints, Permission Sets, Email Templates and (general) settings. This folder has the functionality of the TaskSpace Configuration-Page and Documentum Composer.
Very helpful is the new “Endpoints” functionality where all connection parameter to external system or repositories are stored. In xCP2.0 exists only one central page to administrate all login and connection data.
The Object Models and Processes represents the ProcessBuilder and Composer features.
The Object Models area includes the Business Objects, Content, Folders, Picklist and Relationship function.
The User Interface and Data Services replaces the FormsBuilder and the awful Adaports from xCP 1.x.
The User Interface section includes the functionality to create and manage a default Master page and runtime Application UI, Business Object UI, Content UI, Folder UI or Process UI. The Master UI has the same functionality like the master page in Microsoft’s Power Point.
Data Services is a collection of queries to create data-based widgest. It’s possible to gather objects from the repository (realtime), historical data, indexed content and tasks.
Personal impressions of EMC’s hands-on LaB in Vienna
The first lab session called “Beginner” on Tuesday, 6th November 2012 allowed us a 2h preview of the new xCP2.0 Runtime (which is replacing TaskSpace) and the great xCP Designer. xCP Designer is the new unified tool and replaces the Process Builder, Forms Builder, Composer, Process Reporting Services and the TaskSpace configuration functions.
Business Objects represent the contentless objects in Documentum and are inherit from the dm_sysobject. IT’s comparable to the creation of object types in Composer with general attributes like label, value type and default value.
The expression language (SpEL) auto-completes contextual object-oriented phrases in dot-syntax. It is very easy to create complex expressions, because the auto-complete functionality allows only to use data in the correct relation.
Dan Ciruli told us that custom functions allow nearly endless flexibility and power.
Forms Adaptors have been completely replaced by Data Services. This Data Service includes Real Time, Historical, Full-Text or Task-List Queries. Real Time Queries are based on stateless objects and define GUI-driven a DQL query (you did not see any DQL in the wizard !). Second step is to create a results list and connect the output with the previously created data service instance.
A helpful functionality is to refresh the result set in realtime, the function is called “when an input value change”. So every time a customer types into the field the result area changed. Also available: refresh on page load.
Relationships are a very powerful function to bring data in a special context/relation to each other. Example: Country:City is a One to Many (1:n) relationship. Also available One to One (1:1), Many to One (n:1) and Many to Many (n:n) relationship.