Import supporting Documents from local filesystem in Create content page D2

Hi All,

I'm using D2 4.2. In the content creation page I need to attach some supporting documents from the local file system. After creating the content the supporting documents also should be imported to the repository. The problem is I could not able to bring this import operation of supporting documents in the content creation page. Need some pointers. This feature is vital for my project. Kindly help.

Thanks,

Regards,

Vijayavel Sekar

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

CláudioGil

Hi again,

I don't have examples using D2FS because, in our context, the quick and dirty way of doing it is advantageous (avoids having D2FS available in all contexts). You can take a look at the available documentation (). To use the Content API directly the sequence is something like:


// ensure that D2 modules are loaded
D2Session.initTBOEx(session, false)

// create and setup tracker (you must know the configuration name)
ID2cWorkflowTracker tracker = D2cWorkflowTracker.newObject(session, "a name");
tracker.setWorkflowConfigName(configName);
tracker.setWorkflowTemplate(process);
tracker.setBoolean(ID2cWorkflowTracker.ATTR_SEND_NOTIF_ON_START, false);
tracker.setBoolean(ID2cWorkflowTracker.ATTR_SEND_NOTIF_BEFORE_END, false);

tracker.addAttachment(mainDoc,     null, true /* master */);
tracker.addAttachment(supportDoc1, null, false);
tracker.addAttachment(supportDoc2, null, false);

tracker.save();
tracker.startWorkflow(note);

Regarding the lifecycle, if you have entry conditions for the start state then you can also use D2FS or, the internal API. In this case D2 provides a method, called "D2LifecycleChangeStateMethod", which simplifies things for us. You can invoke that method with the default method arguments (docbase_name, user_name, domain_name, password) and:

-id: The id of the document
-caller_login: the login name of the user
-caller_domain: the domain of the user
-transition_type: "start" to attach
-target_state: name of the entry state

Regards,

Cláudio

All comments

CláudioGil

This is not supported by D2 configuration. Extending a properties dialog is not possible, as far as I know it.

As an alternative, users could import the supporting documents and then create the main document and add relations with a "relator" widget. But this order many be illogical in your context.

If you want to extend D2 then you may go for an workspace dedicated to this operation and have a custom widget in a central area and a doclist (showing a particular folder for the user) in a side area. The user would be able to fill properties (in the central area) and import supporting documents by dragging them to the doclist. The problem would be in keeping the creating form configurable and reuse the templace choosing logic, for example.

vijaysince89

Hi Gil,

Thanks for the reply. You post is really helpful. Actually I've already created a custom page same like that you said but without Doclist widget. I'll upload the supporting documents in the custom widget itself. I've used DFC to create the content and upload the supporting documents. the problem now is, D2 is not supporting the Workflow triggered by DFC after creation of the content. My current requirement is after creation of content in DFC the file should be attached with D2 Lifecycle and Workflow. Should I have to use D2FS for supportability ? What am I missing here ?

Thanks,

CláudioGil

Hi,

If I understand correctly you are already starting a workflow with the main document and supporting documents as attachments. You want users, in D2, to be able to complete that workflow task and have the main document associated with a D2 lifecycle.

What I know is that D2 depends on an workflow tracker. Without this structure the client will have problems handling the workflow instance. So you can start the workflow with D2FS to setup all the required structures, as you mentioned, or you can use D2cWorkflowTracker directly (depends on the D2 Content API, quick and dirty, obviously less supported). Nevertheless, in any case, the task should appear as usual to users and the main document, the first attachment, will be in bold as expected.

As for the lifecycle, D2 only needs a valid configuration available for the document and a_status (or other configured attribute) to be filled. So if you fill that attribute, create a configuration and check the appropriate context users will be able to promote/demote the document and lifecycle activities, in the workflow, should work.

Cheers,

Cláudio

vijaysince89

Hi Cláudio,

So I understand after triggering the workflow in DFC we have to modify some thing in the d2c_workflow_tracker table. Can you provide me the details? I mean what we have to update in the d2c_workflow_tracker table? And if possible I want to attach the lifecycle created in D2-Config.

one more thing is that I need to learn D2FS programming. Do you have any sample code on triggering workflow and creating new content using D2FS ?

Thanks

CláudioGil

Hi again,


// ensure that D2 modules are loaded
D2Session.initTBOEx(session, false)

// create and setup tracker (you must know the configuration name)
ID2cWorkflowTracker tracker = D2cWorkflowTracker.newObject(session, "a name");
tracker.setWorkflowConfigName(configName);
tracker.setWorkflowTemplate(process);
tracker.setBoolean(ID2cWorkflowTracker.ATTR_SEND_NOTIF_ON_START, false);
tracker.setBoolean(ID2cWorkflowTracker.ATTR_SEND_NOTIF_BEFORE_END, false);

tracker.addAttachment(mainDoc,     null, true /* master */);
tracker.addAttachment(supportDoc1, null, false);
tracker.addAttachment(supportDoc2, null, false);

tracker.save();
tracker.startWorkflow(note);

-id: The id of the document
-caller_login: the login name of the user
-caller_domain: the domain of the user
-transition_type: "start" to attach
-target_state: name of the entry state

Regards,

Cláudio

vijaysince89

Hi Cláudio,

Where do I find the ID2cWorkflowTracker and D2cWorkflowTracker containing jar. I could not able to find this interface and class file in Java Stub libraries of D2FS.

Thanks

CláudioGil

I was not very detailed but when I mentioned "D2 Content API" I was referring to the API (jars) that was normally copied to the method server but that are also used by the D2 client. When you install D2, this corresponds to the "content" path you specify.

For short, they are in D2-API.jar or D2-API-4.1.0.jar depending where you look for.

Regards,

Cláudio

vijaysince89

Hi Cláudio,

Now I'm getting an error message like below.

Exception in thread "main" java.lang.ClassCastException: com.documentum.fc.client.DfDocument___PROXY cannot be cast to com.emc.d2.api.workflows.ID2cWorkflowTracker

any idea ?

Thanks

CláudioGil

That happens if you ignored the first 2 lines of my post. Here are the relevant lines again.


// ensure that D2 modules are loaded  
D2Session.initTBOEx(session, false)

In case you want to know, that error is due to how D2 registers TBOs (client side using internal APIs of DFC). The DAR you install with D2 does not include any TBO so, if you miss that line, there will be no custom implementation class associated with d2c_workflow_tracker and the default TBO only implements IDfDocument. With the above line of code D2cWofklowTracker is registered as the TBO for d2c_workflow_tracker and everything works as expected.

vijaysince89

Hi Cláudio,

Great ! you are absolutely right. But even after I included that line I'm comming accross the following error.

SLF4J: The requested version 1.5.8 by your slf4j binding is not compatible with [1.6]

SLF4J: See http://www.slf4j.org/codes.html#version_mismatch for further details.

Exception in thread "main" java.lang.NoSuchMethodError: org.slf4j.helpers.MessageFormatter.arrayFormat(Ljava/lang/String;[Ljava/lang/Object;)Ljava/lang/String;

This error occurs at the line " D2Session.initTBOEx(session, false) "

vijaysince89

Actually I've changed the Slf4j version and now the above problem is rectified but In the console screen I'm getting some list of output with an exception at last .

Console:-

20:13:48.730 [main] DEBUG 1 - jar:file:/C:/Users/353914/Desktop/D2/D2-API.jar!/C6-dbor.properties

20:13:48.732 [main] DEBUG 1 - jar:file:/C:/Users/353914/Desktop/D2/C2-API.jar!/C6-dbor.properties

20:13:48.733 [main] DEBUG 1 - jar:file:/C:/Users/353914/Desktop/D2/D2-Bin-API.jar!/C6-dbor.properties

20:13:48.733 [main] DEBUG 1 - jar:file:/C:/Users/353914/Desktop/D2/D2-Widget-API.jar!/C6-dbor.properties

20:13:48.733 [main] DEBUG 1 - jar:file:/C:/Users/353914/Desktop/D2/O2-API.jar!/C6-dbor.properties

20:13:49.065 [main] DEBUG 1 - Default Url for d2-cache.xml is jar:file:/C:/Users/353914/Desktop/D2/C6-Common.jar!/com/emc/common/java/cache/d2-cache.xml

20:13:49.067 [main] DEBUG 1 - C6 SAX PARSER : com.sun.org.apache.xerces.internal.jaxp.SAXParserFactoryImpl

20:13:49.081 [main] DEBUG n.s.e.config.ConfigurationFactory - Configuring ehcache from InputStream

20:13:49.091 [main] DEBUG net.sf.ehcache.config.BeanHandler - Ignoring ehcache attribute xmlns:xsi

20:13:49.091 [main] DEBUG net.sf.ehcache.config.BeanHandler - Ignoring ehcache attribute xsi:noNamespaceSchemaLocation

20:13:49.092 [main] DEBUG n.s.e.config.DiskStoreConfiguration - Disk Store Path: C:\Users\353914\AppData\Local\Temp\

20:13:49.107 [main] DEBUG n.s.e.config.ConfigurationHelper - No CacheManagerEventListenerFactory class specified. Skipping...

20:13:49.120 [main] DEBUG n.s.e.config.ConfigurationHelper - No BootstrapCacheLoaderFactory class specified. Skipping...

20:13:49.120 [main] DEBUG n.s.e.config.ConfigurationHelper - No CacheExceptionHandlerFactory class specified. Skipping...

20:13:49.121 [main] DEBUG n.s.e.config.ConfigurationHelper - No BootstrapCacheLoaderFactory class specified. Skipping...

20:13:49.121 [main] DEBUG n.s.e.config.ConfigurationHelper - No CacheExceptionHandlerFactory class specified. Skipping...

20:13:49.121 [main] DEBUG n.s.e.config.ConfigurationHelper - No BootstrapCacheLoaderFactory class specified. Skipping...

20:13:49.121 [main] DEBUG n.s.e.config.ConfigurationHelper - No CacheExceptionHandlerFactory class specified. Skipping...

20:13:49.121 [main] DEBUG n.s.e.config.ConfigurationHelper - No BootstrapCacheLoaderFactory class specified. Skipping...

20:13:49.121 [main] DEBUG n.s.e.config.ConfigurationHelper - No CacheExceptionHandlerFactory class specified. Skipping...

20:13:49.123 [main] DEBUG n.s.e.config.ConfigurationHelper - No BootstrapCacheLoaderFactory class specified. Skipping...

20:13:49.123 [main] DEBUG n.s.e.config.ConfigurationHelper - No CacheExceptionHandlerFactory class specified. Skipping...

20:13:49.123 [main] DEBUG n.s.e.config.ConfigurationHelper - No BootstrapCacheLoaderFactory class specified. Skipping...

20:13:49.123 [main] DEBUG n.s.e.config.ConfigurationHelper - No CacheExceptionHandlerFactory class specified. Skipping...

20:13:49.123 [main] DEBUG n.s.e.config.ConfigurationHelper - No BootstrapCacheLoaderFactory class specified. Skipping...

20:13:49.123 [main] DEBUG n.s.e.config.ConfigurationHelper - No CacheExceptionHandlerFactory class specified. Skipping...

20:13:49.123 [main] DEBUG n.s.e.config.ConfigurationHelper - No BootstrapCacheLoaderFactory class specified. Skipping...

20:13:49.123 [main] DEBUG n.s.e.config.ConfigurationHelper - No CacheExceptionHandlerFactory class specified. Skipping...

20:13:49.123 [main] DEBUG n.s.e.config.ConfigurationHelper - No BootstrapCacheLoaderFactory class specified. Skipping...