E20-120 Exam : Important Notes

E20-120 Content Management Foundations Exam ( Notes and Tips)

Documentum General

• The  Document Repository consists of two primary components
• A file system to store content and
• A database server to store properties
• A document can have MULTIPLE renditions
• The consistency checker job is an out-of-the-box job that detects and reports inconsistencies with regard to workflows among other things.
• DQL is a strict superset of ANSI SQL. That means an ANSI SQL statement is a valid DQL statement. However, in order for the SQL to execute correctly, the tables would need to exist and be registered and the permissions need to be appropriately set.
• A federation is set of repositories, created to keep global users, groups, and external ACLs synchronized among member repositories.

Documentum Add on's

• Object Replication : implementation of distributed content architecture provides for both content and metadata to be synchronized across multiple repositories.
• Application Integration Services does the Documentum repository use to transfer content from third-party applications that do not have plug-ins or connectors.
• Content Transformation Services Marketing has created a press release using Microsoft Word ad checked it into the repository. They want to distribute the press release as a PDF.
• Documentum Content Intelligence Services : Categorizing
• Content Storage Services enables the automated movement of content between tiers of storage.
• IRM  product is used to secure and control content once it leaves the content repository
• Record Manager : government regulation 
• Federated Repositories: To reduce the administration of managing multiple content repositories spread across geographical areas.
• Documentum Branch Office Caching Services A solution that was recently deployed for managing office documents was a success and you have now been asked to expand the solution to support remote sites and several of the sites have slow network connections.
• Netegrity SiteMinder : This is a plug-in module Documentum provides for supporting Web-based single sign-on authentication?
• Microsoft Office Integration for Documentum adds menus for directly interacting with Documentum repositories from within the Office applications.
• Collaborative Services provide these features - rooms, discussions, contextual folders, calendars, data tables, and notes.

Custom Type

• NULL Type is
• A custom object type without a supertype and
• You must have SUPER USER privilege to specify a NULL super type
• They can NOT seen from documentum desktop or webtop
• To create custom type, you must have either SUPER USER or  SYSADMIN or CREATE TYPE
• SUPER USER Privilege is only required when installing a custom type definition into a repository from composer
• SYSADMIN or CREATE TYPE are adequate for defining custom types in DA, TaskSpace OR through DQL
• A custom type can be dropped (removed) from the repository only if no objects of the type are present and no subtypes of this type are present in the repository.

ALIASES

• Alias Resolution during Activity and Workflow
• When an activity starts the alias resolution is performed by Content Server. 
• When a workflow starts, the user provides the missing values in the alias set.
• The DFC link/unlink methods have a folderSpec argument which can contain aliases. The algorithm for resolving these aliases is the same as that used for saving a sysobject.
• When aliases are resolved for an object without a lifecycle, the resolution process stops as soon as an alias name is found, even if no value is present for the alias in that alias set.
• When a workflow is started it gets its alias set from the workflow template. If it contains aliases without values, the values are provided by the user starting the workflow.
• Custom attributes can contain alias references but they are not resolved by the content server. It is the responsibility of the application or the customization to resolve these alias references.
• Even though r_alias_set_id in dm_sysobject is named starting with "r_", it can be set using an UPDATE DQL query.

TYPE

• Value assistance can be specified for a property of any data type other than boolean. A boolean property can only be true or false.
• It is possible to change the type of an object. However, the type can only be changed to a supertype or a subtype of the existing object type.
• Permission Set Templates (ACL templates) are created using Composer (or DAB before version 6.x). They cannot be created using DA or Webtop.
•  Content server makes no use of data dictionary and it is only for the use of client applications.
• Events are also inherited from supertypes, just the way properties are.

DOC APP

• When adding a virtual document to a docapp, its components are not added automatically. If so desired, each component of the virtual document needs to be added explicitly.
• When an alias is added to a docapp it becomes a part of the default alias set of the docapp.
• DocApps are stored in the repository as dm_application objects.
• DocApps are versioned in the repository but the DocApp archive on the filesystem does not contain version info. When the archive is installed, it may increment the version in the target repository.
• If a docapp contains objects of a custom type, the custom type needs to be  a part of the docapp for installing into another repository.

 GROUPS

• For creating a group (dm_group object) you must have Create Group privilege and System Administrator client capability when using Webtop.

 LIFCYCLE

• Entry criteria are not enforced for lifecycle owner and for any user with SUPERUSER privilege.
• Changing an object's lifecycle state requires at least WRITE permission and CHANGE STATE extended permission. (Contributed by: Praveena Kothakota)
• In a lifecycle, the entry criteria for all the states use the same language for procedures - Java or Docbasic.
• When an object is demoted in its lifecycle entry criteria are not checked. Entry criteria are checked for promote, suspend, and resume operations.
• If a lifecycle handles multiple types, the chosen object types must have the same supertype or one of the chosen types must be the supertype for the other included types.

PERMISSIONS

• Basic permissions grant the ability to access and manipulate an object's content/metadata and they are hierarchical.
• Folder security is an additional repository security mode that controls who can create, move, link, or delete objects in folders or cabinets.

OBJECTS

• Cabinets are top-level folders and cannot be created inside another folder.
•  Attaching an aspect to a type does not guarantee that all objects of that type will have that aspect attached. Object existing prior to the attachment of aspect to type may not have this aspect. Also, aspects can be detached from objects.
• dm_cabinet has no repeating properties of its own.
• dm_document tag is 09 in an object id. This means that all objects of type dm_document or one of its direct or indirect subtypes have object ids starting with 09.
• The "version numbers" for objects are implicit labels and are assigned by content server.
• Renditions cannot be edited or versioned.
• An object ID consists of 16 hex digits. The first two digits specify an object type. The next 6 digits identify the repository ID. The last 8 digits provide a unique identifier within the repository
• The persistent object type is special and it has three properties:
• r_object_id - unique object id
• i_vstamp - number of committed transactions on the object
• i_is_replica - whether the object is a replica of an object from a remote repository
• The allowed data types for properties are boolean, integer, string, double, time, and ID.
• While most of the properties with names starting with r_ are read-only to users and applications, r_version_label is not. It can accept user-defined values which are version labels.
• Different repeated properties for an object normally don't have any association with each other. Thus different columns in a record for a *_r table may not be related to each other. On the other hand, some properties may correspond within a record but that is not the default case.

SUBSCRIPTION

• A user can directly access objects through Subscriptions. It is also possible to subscribe to a document while checking it in. 

ANNOTATIONS

• VERSION permission is minimum permission needed to attach annotations to PDF document in repository.

SECURITY

• Client Capability determines the functionality available to a user in client application. It is optionally enforced by client applications.
• By default, the content server authenticates users against an operating system account.
• Each user's privileges and extended privileges determine the functionality available to the user. Privileges are enforced by the content server.

VIRTUAL DOCUMENTS

• A virtual document object (root of the hierarchy) can also contain content of its own just like a simple object.
• The components included in an unfrozen snapshot can be deleted or checked in as the existing versions. Freezing a snapshot prevents these changes.
•  A virtual document object is of type dm_sysobject or a subtype other than dm_folder and its subtypes. The same type constraints apply to the components of a virtual document.

PRESETS

• A preset cannot set object_name, a_content_type, or any attribute that is effectively read-only.
• When multiple presets could apply in a situation, they are follow the following precedence by default - location, user, role, and object type. The default precedence can be altered by customization.
• When a preset containing an attribute rule is modified, the changes apply only to the newly created objects.
• When a preset is applicable to a cabinet or a folder, it doesn't apply recursively to subfolders of that location.
• The preset editor doesn't enable aspect attributes to be set
• Presets can set the attributes of string, integer, and double types only.
• A navigation rule selects nodes to show and the default node to open on login. However, nodes tied to client capability and roles cannot be added to a navigation rule.
• Webtop presets are not used to provide security. They are used to focus user experience.
• Presets override WDK configuration files in memory. They do not change the configuration files.
• Administrators or member of dmc_wdk_presets_coordinator can create presets

WORKFLOW and ACTIVITY

• A workflow activity may specify its performers to be - a specific user, all users in a group, single user from a group, some users from a group. 
• An activity definition may be used for two or more activities in a workflow template but two activities cannot be placed in parallel if they use the same activity definition.
• A workflow activity can be triggered by any combination of prior tasks completing or by receiving an event.
• To view completed workflow reports auditing must be enabled on the corresponding workflow templates.
• Performers for a workflow activity can be determined at run-time in the following ways - the worflow initiator determines, the performer of the previous activity determines, or alias resolution determines the performer(s).
• Workflow activities can have these priorities - low, medium, high, and dynamic. Dynamic priority lets an application set the activity priority.
• In a workflow template, a package must be defined in every flow except the ending flow. Multiple packages can also be specified for one flow.
• A workflow template must be installed to be available to users to start a workflow instance from it. 
• Automatic activities are executed through Content Server workflow methods using the identity of the performer.
• Historical reporting (completed workflows) requires that auditing be turned on for the relevant workflow template.
• What you design is a workflow template and what you execute is a workflow. A wokflow template defines the process while a workflow instance is that process in action processing some content.

VERSION

• A version number cannot definitively indicate whether it is on a branch. Major versions are always of the form x.0 and can be on a branch. However, a version number of the form x.y.* is always on a branch.
• It is possible to check in a document as the same version. In this case the object starts using the new content file without changing the version. Underneath, the save method is used instead of the checkin method.
• Any version of a document can be the current version. Current version doesn't imply the latest version.
• A major version format is always of the form X.0 no matter where it occurs in the version tree - on the trunk or on a branch.
• The only property needed to create a rendition is FORMAT.
• A rendition is not an object, rather it is associated with an object as its primary format.
• Documentum supports any document format.  There are a large number of predefined formats and users can define additional formats.

WEBTOP

• Webtop also provides several user preferences option related to searching
• Display Columns
• Favorite repositories
• Default search location