Archive

Posts Tagged ‘Lifecycles’

Implementing Security in Documentum

November 17, 2010 Comments off

Alias sets provide a means resolving attribute values that specify user and group names. This is an extremely powerful feature of Documentum because it allows you to design s, Lifecycles, and Workflows that can be used in multiple contexts without modification. Aliases are place holders for user names, group names, or folder paths.

Using aliases lets you write applications or procedures that can be used and reused in many situations because important information such as the owner of a document, a workflow activity’s performer, or the user permissions in a document’s is no longer hard coded into the application. Instead, aliases are placeholders for these values. The aliases are resolved to real user names or group names or folder paths when the application executes.

Similarly we have Permission templates which are created in the system with specific business needs and it refers to alias set. The templates can be applied on the individual object or group of objects. If a template is not explicitly applied to the object then a default template which is internally created by Documentum will be applied to the objects. Each object in the system that is created such as folders, documents, Workflows, lifecycles can be applied with individual permission. The application becomes even more flexible if you assign a template to the document. When the template is assigned to an object, the server creates a copy of the, resolves the aliases in the copy to real user or group names, and assigns the copy to the document. So when the actual template is changed with some permission information the copy normally gets updated.

Note: In some cases the copy of the template which is automatically created will not get updated. Some objects may be referring to the original Template that needs to be dereference and then the same needs to be applied.

Will bring out the difference between Alias Set and Permission Set in my Next Post.

Handling LifeCycles in DCTM using DFC

April 27, 2010 Comments off

We know how Documentum helps attach a LifeCycle to a document and How to handle its states viz.How to Promote & Demote a Lifecycle state .Let’s try to bring in the same using DFC Concepts.

Attach a LifeCycle to a document in docbase:

public void attachLifeCycle() throws Exception{
IDfSysObject sysObj = (IDfSysObject) idfSession.
getObjectByQualification(“dm_document where
object_name= ‘UniqueDocName’ “);
IDfSysObject procObj = (IDfSysObject)
idfSession.getObjectByQualification(“dm_policy where object_name=
‘LifeCycle Name’ “);
sysObj.attachPolicy(procObj.getObjectId(), “Author”,””);
}

Promote a LifeCycle state of a document inside a docbase:

public void promoteLifeCycle (String State) throws Exception {
IDfSysObject sysObj = (IDfSysObject) idfSession.
getObjectByQualification(“dm_document where
object_name = ‘UniqueDocName’ “);
sysObj.promote(State,false,false);
}

Demote a LifeCycle state of a document inside a docbase:

public void demoteLifeCycle(String state) throws Exception {
IDfSysObject sysObj = (IDfSysObject) idfSession.
getObjectByQualification(“dm_document where
object_name = ‘UniqueDocName’ “);
sysObj.demote(state,false);
}

How to suspend or resume a LifeCycle of a document in Documentum ?

Expire a LifeCycle state of a document in a docbase:

public void expireLifeCycle (String state) throws Exception {
IDfSysObject sysObj = (IDfSysObject) idfSession.
getObjectByQualification(“dm_document where
object_name=’UniqueDocName’ “);
sysObj.suspend(state,false,false);
}

Resume a LifeCycle state of a document inside docbase:

public void resumeLifeCycle (String state) throws Exception {
IDfSysObject sysObj = (IDfSysObject) idfSession.
getObjectByQualification(“dm_document where
object_name=’UniqueDocName’ “);
sysObj.resume(state,false,false,false);
}

Your valuable comments matters , i will work on the same if any tuning to the above piece of snippets is required.

Thank You

Documentum Process Management Features

March 22, 2010 Comments off

Process Management in CMS

Workflows:

–          A workflow formalizes a business process such as an insurance claims process or an engineering development process. After the business process is formalized in a workflow definition, users can use the definition to repeatedly perform the business process.

–          Workflows can describe simple or complex business processes. A workflow can be serial, with activities occurring one after another and only one activity in progress at a time. A workflow can be parallel i.e. consist of two or more activities, all happening concurrently. Or, a workflow can combine serial and concurrent activity sequences.

–          You can also create a cyclical workflow in which the completion of an activity restarts a previously completed activity. For example, SOW documents which require re-validation over a period of time.

Life Cycle:

–          A lifecycle is a set of states that define the stages in an object’s life. The states are connected linearly.

–          An object attached to a lifecycle progresses through the states as it moves through its lifetime. A change from one state to another is governed by business rules. The rules are implemented as requirements that the object must meet to enter a state, actions to be performed on entering a state, and actions to be performed after entering a state.

–          You cannot attach a lifecycle definition to a lifecycle i.e. one life cycle can not use another life cycle in its definition.

%d bloggers like this: