Lifecycle attachment on new version of document

Hello All,

I'm using TBO to attach lifecycle to by custom object type and it works fine.

But there is a condition, when my document is in Valid state and needs revision and editor only has version permission and creates new version, how can I attach lifecyle from start on this new version.

Find more posts tagged with

Documentum

Note:

If there are Accepted Answers, those will be shown by default. You can switch to 'All Replies' by selecting the tab below.

Accepted answers

DCTM_Guru

Like I said, there is a configuration option on the lifecycle object that return the state back to draft upon checkin of new version.

All comments

DCTM_Guru

IMHO, if a document needs revision, then it really should be demoted to previous lifecycle state where user has permissions to edit document (ie it shouldnt be VALID state any more).

As for the lifecycle, I believe there is an option in the lifecycle configuration that allow you to associate lifecycle with CURRENT version of the document. This will allow you create newer versions of document and not worry about always attaching lifecycle to newer version.

Prashant_Kasbe_C

Thank for quick reply, however the my need is explained better below:

LifeCycle is like this:

Draft ->Pending Verification -> Verified -> Pending Aprroval -> Approved --> Valid.

When document attains Valid and state, its published. And after few months / years when the document needs revision new version will be created and new version should then have same lifecycle with Draft state as the new version will again be in workflow.

DCTM_Guru

Like I said, there is a configuration option on the lifecycle object that return the state back to draft upon checkin of new version.