in TBO delete functionality(virtual document case) can we get control that whether user has checked

Hi all,

i am customizing the delete operation using TBO...

as we have the

method doDestry() and doDestroyAllVersion() for info that whether user has selected all version or only selected version ......but in case of virtual document we have 2 more radio button so can we know whether user has chcked for deletion of all discendent or user has checked only virtual document since i have requirment i want to insert the data in table (if user has checked all discendent). if we can handle this in TBO it will be great help for me..

Note: we can get this in java class of delete component(if we customize) but i want to store only if all the validation is successful.......

Thanks in advance..................................

Find more posts tagged with

Documentum

Comments

DCTM_Guru

Probably not. You will need to customize the WDK component to do what you want. Keep in mind, TBOs are low level server methods. So most of the UI and business logic is encapsulated in the WDK component. This where you will need to change if you want to change business logic.

ujjwaltiwari

ok but if i have customize component class of delete document ....and store some value in variable like whether user has selected it or not how can we access those variable in our TBO class.....is there any way to access it... if not so how can we pass this as argument in doDestroy() or do DestryAllVersion()..........................

like we can add in SessionState................ any other option than SessionState..................

Francois Dauberlieu

TBO can't interact with Webtop, it is independant of any client.

Why not SessionState ?

ujjwaltiwari

Actually i want to understand if there is any way in which we can pass the argument to TBO. and i also want to avoid the variable addding into sesionstate. yes i am having this as my last option....

Francois Dauberlieu

Correction: you should say ONLY option, not LAST option ;-)

As said earlier, TBO's are triggered automatically and are independant of any client cusotmization, therefore, they can't communicate with Webtop directly, besides addin session parameters before it would be triggered

Francois Dauberlieu

That said, another way would be to have an aspect that adds the properties you need and in your Webtop customizastion,, attach this aspect and populate the values and in your TBO, read it.... That would most likely require much more coding than using SesisonState though...

ujjwaltiwari

Thanks Francois Dauberlieu. now i am going to use sessionstate.....

and thanks to you Johnny Gee for your reply .i also went through ur Tbo material for understanding the tbo..

Francois Dauberlieu

No probs.Please, mark the question **** answered then, no point in othere spending time on reading the thread...

DCTM_Guru

To add to what Francois stated, if you choose not to use aspects or session state, you can also create custom attributes to store session state info.

Francois Dauberlieu

Yeap, Johnny is right. Personally,

I'd rather use Aspects than extra attributes then because e aspect would only be applied to the document(s) beeing deleted whilst doc type attributes would be there for all objects and therefore add to the RDBMS....

My 2 cents

DCTM_Guru

I totally agree with your preference Francois. Has EMC resolved the issues with using aspects in Composer? We ran into a few issues about year ago that made it difficult for us to use aspects with Composer.

Francois Dauberlieu

I don;t know if it's fixed but I'd expect it is since we implemented our CAd integration into EPFM, EMC's new Plant and Facilities Management product, and EPFM uses aspects quite heavily...