nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

D2 4.1 Lifecycle

MaxB

Hi All,

I know D2 has its own lifecycle management, different from the Documentum standard one (Not stored as dm_policy)

Q1) Ho can I verify the lifecycle attached to a document and in case, the current lifecycle state?

THis is very important during problem solving

Thanks,

Massimiliano

Find more posts tagged with

Comments

Lakshminarayanan

1. To know which attribute is used for managing lifecycle states you have to view the d2_lifecycle_config

you will know from Action type (setProperty) which property(ies) are used

2. AFAIK there is no direct way of saying which document (type) use which lifecycle.

If you know the document sets that qualify your type you can go to the matrix to see the applied lifecycle config (or)

use a something like this

DQL > select * from dm_dbo.d2_documentset_switch_r where config_name in (select object_name from d2_lifecycle_config )

[Added]

Oh how can i forget - For problem solving, place the focus on the document which you want to troubleshoot .

Press CTRL + ALT + D : This beings up the dump of the object. Then right click on the dump screen and switch widget.

This will give you all context information the document is qualified for.From here you can learn the D2 configuration applicable for the document and it is easier to go ahead with your troublehooting!!

Hope it helps!!

MaxB

Hi Lakshminarayanan,

Thanks for pointing me to the 'd2_lifecycle_config' object.

My use case is a little different.

USE CASE1:

Suppose the developers complete the D2 configuration.

Suppose at runt-time a document instance (configured 'correctly' in D2 config) does not enable to move to the next 'configured' lifecycle state.

In this case, in order to analize the problem my starting point is the document r_object_id and using this I would identify if the lifecycle has been attached correctly (as per design), and in which state the lifecycle is now.

This could be also more complicated scenario, in case there is a workflow that invoke a promote and the lifecycle is not identified/ in the correct state in order to suddisfy the worflow action.

Hope my use case is clear,

Thanks in advance,

Massimiliano

Lakshminarayanan

Hi -

I am not sure I understood it completely,

If you are concerned troubleshooting issues when you have workflow and life-cycle working hand-in-hand in D2.

One easy way to troubleshoot such issues is to :

- Ensure you have enabled "Display Task in Workflow Manager" for every task in D2-Configuration. this way we may know the status of a workflow visually from Workflows Tab of D2

- Audit all events related to D2 workflow/lifecycle actions

(d2_workflow_started, d2_change_state, d2_acquired_task, d2_workflow_aborted...... etc)

This way when you have a running workflow, you will know at runtime, where the workflow is stuck and by going through the Audits , you will be able to gather more information on what went wrong.

MaxB

Hi,

Yes very important points for troubleshooting.

Suppose this use case:

I expected that a document istance 'DI1' moved from Lifecycle 'LC1' StateA to StateB as visible in design-time (D2 Config) but at run-time 'D1I' is not in that state (i.e the a_status is not as expected) so,

How can I check which Lifecycle is attached to 'DI1' and its current state?

Thanks,
Massimiliano

Lakshminarayanan

Hello -

Ok. With example it is clear

There is NO r_policy_id -> r_current_state when it comes to D2.

1. So you will never know from an attribute WHAT lifecycle is attached to DI1

2. The only way you know your status is from the attribute You configured to represent status (eg: a_status)

If it is empty, then there has been no lifecycle config applied on the document.

Having said that. Here are the explanations to your questions in detail with your use case example above

- How can I check which Lifecycle is attached to 'DI1' ?

As i told you before, there is no r_policy_id which helps you determine which lifecycle is ATTACHED to DI1.

We can only find out what are the lifecycle modules that DI1 qualifies for using Configuration information obtained

through "CTRl + ALT + D (and then click SWITCH)". If the DI1 does not qualify for any lifecycle,, you wil see the lifecycle related information is EMPTY.

You will see something like this.

- and its current state?

As in your example "a_status" attribute is what will indicate in what state the DI1 is in,

If a_status is empty:

Check if the configuration dump shows up with information on lifecycle modules applicable to DI1.

if it is empty then, the lifecycle config has not been applied to the proper document sets (configuration issue) -

If it is non empty then, the action failed at runtime for some reason.

if a_status is in State1 (and it is expected to be in State2)

Fix

If you want to fix the state of the document DI1, just upate a_status to "State2" and then run D2CoreMethod on the document.

This will ensure all necessary relinking ; ACL updates related to "State2" configuration is applied on the object.

Hope this answers your question

MaxB

Hi,

Thanks for Your time and description. It's very well described.

Unfortunatly, I supposed we had any documented attributes/relations showing the information I asked for...

But at least with the description You provided, expecially the 'fix' we can manage it.

Do we have a documentation related to the D2-Methods? In order to identify related parameters and expected results?

Thanks again

Lakshminarayanan

Glad that it helped.

Yes, some documentation is available on EMC Community.

https://support.emc.com/products/24306_Documentum-D2/Documentation/

Document: Documentum D2 4.1 Administration Guide

This is an excerpt from this guide.You can use this job to treat the ocument by D2CoreMethod.

Please note: If you find this answers your questions or other replies help you. Please mark the posts in the thread appropriately so that it may help others as well.

Name: D2JobCore

Description: Re-apply configurations to existing objects.

Frequency: Once per day

Default state: Inactive

Parameters

•

dql_filter select r_object_id from dm_document: Set a DQL filter to select objects related to the job.

•

create: By default, does not apply the job to content during creation. Set true to apply during creation.

•

naming: If create is true, by default apply naming during creation. Set false to avoid applying naming.

•

autolink: By default, applies autolink for property regeneration. Set false to avoid property regeneration.

•

security: By default, applies security to the job. Set false to avoid applying security.

•

apply_for_vd: By default, does not apply the job to child content. Set true to apply to child content

Good Luck!!

Lakshminarayanan Rengarajan

MaxB

Thanks for Your time