TBO not triggering while importing a document in DA

I am unable to figure out why the TBO is not being triggered on submit while importing a document in documentum administrator. I have also checked the logs and it doesn't show anything.what could be the possible reason or issues behind the same?I do not find any error with the TBO code.have also tried reloading it .But still it is not being triggered. Can anyone please help with this and provide pointers?

Find more posts tagged with

Comments

DCTM_Guru

Does this work in Webtop? I have seen certain webtop functionality that doesnt work in DA, even though the functionality is exposed like Webtop. I think testing of DA is focused on admin features and not content management features.

Francois Dauberlieu

which method are yourextending ? Are you sure you're extending the right ones ?

DCTM_Guru

Make sure you package matches your class name.

RaviJha

Hi Prerna,

Are you selecting your custom type object as the type while importing? You should have extended doSave/doSetFile/doSetContent etc to see them in action during an import.

It is also important to note that if you have extended doSetFile/doSetContent/doSetStream it will not be called if the content goes through ACS as content never comes to appserver in this case.

Regards,

Ravi

RaviJha

If it is not confidential, you may want to post the TBO code for better assistance.

vjagoncalves

Some times, TBO's doesn't seems to be updated for me, do not know why.

I usually do a simple test, I create a TBO that only throws an exception on Save. If it doesn't work, I use to clean all caches...CS, web server, browser...

Francois Dauberlieu

Actually, I just realized that none of us asked the 1st and most important question:

Is your global registry information correct in the dfc.properties file of DA ?

akashmishra17

Can you able to find out any error in error-log?? also please check you have over ride the correct method.

One more thing you need to remeber is : used Lifecycle is correctly ataching or not, that you can find out in logs as well as your object via Webtop or Webpublisher.

Check your deployment procedure is correct, you have imported all the required jars and browse the correct class name in General Tab.

and if possible kindly provide your logs and code.