Documentum Workflow

Concurrency issues in documentum workflow 

(usually we have seen error -dm_OBJ_MGR_E_SAVE_FAILED_UNAVAILABLE_TYPE ,DM_OBJ_MGR_E_VERSION_MISMATCH)

Content Server has a special setting to prevent tasks from the same workflow 

to be executed at the same time - to prevent concurrency issues.

To enable this , dm_docbase_config object needs to be modified and WF_SKIP_PARALLEL_TASK_EXECUTION=1 needs to be added as r_module_name and r_module_mode respectively:




If 3c01fffd80000103 is r_object_id of dm_docbase_config object, then:

API> append,c,3c01fffd80000103,r_module_name,,WF_SKIP_PARALLEL_TASK_EXECUTION
API> append,c,3c01fffd80000103,r_module_mode,,1
API> save,c,3c01fffd80000103

or

API> retrieve,c,dm_docbase_config
API> append,c,l,r_module_name
Value> WF_SKIP_PARALLEL_TASK_EXECUTION
API> append,c,l,r_module_mode
Value>1
API>save,c,l
API> reinit,c





documentum workflow dqls:



How to get running workflows

see below example..

QUERY_RUNNING_WORKFLOWS = "SELECT wf.r_start_date as wf_start_time,"
            + " D.object_name as foldername,
            + " P.title ,P.subject ,  P.log_entry ,P.object_name ,"
            + " wf.supervisor_name,wf.r_object_id as workflow_id"
            + "  FROM  dm_workflow wf, dm_document D ,dm_process P  where  wf.process_id=P.r_object_id"
            + "  and wf.process_id IN ($param1) and wf.r_start_date > DATE('$param2','dd/mm/yyyy HH:MM:SS')"
            + " and wf.r_start_date <= DATE('$param3','dd/mm/yyyy HH:MM:SS') and D.r_object_id  in (  select distinct r_component_id"
            + " from dmi_package dp  where dp.r_workflow_id =  wf.r_object_id )  and wf.r_object_id in (  select qi.router_id from dmi_queue_item qi"
            + "  where qi.router_id =  wf.r_object_id and qi.task_state<>'paused' ) "


For completed workflow you can dql ...



dmc_completed_workflow cw , dm_process P



cw.component_id = document.r_object_id and cw.complete_type=0 and P.r_object_id =cw.process_id

No comments:

Post a Comment