Catalog default on created Livelink item

Magnus_Salgo_(IDNordicAdmin_(Delete)_2300172)

We would like to change that when something is created in Livelink it will by default be displayed as a catalogue item in the Livelink interface instead of a list item. (dtree.catalog = 1)Question where is the best place to customize ?RegardsMagnus@ids.se

Find more posts tagged with

Comments

eLink User

Message from Hans Stoop <<A HREF="mailto:hstoop@opentext.com">hstoop@opentext.com> via eLink

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">eLink

In a DAPI callback for the creation of a node. It will then also work for items added by LAPI.

Consider that not all items support the catalog mode.

Hans Stoop

--------------
Register your subtypes in the OScript Registry:
https://knowledge.opentext.com/knowledge/livelink.exe?func=ll&objId=2454603
Consultant Partner Programs Europe
hstoop@opentext.com
+31 23 5652333
http://www.opentext.com/

-----Original Message-----
From: knowledge@opentext.com [mailto:knowledge@opentext.com]On Behalf Of eLink Discussion: Development Discussion
Sent: maandag 20 augustus 2001 16:13
To: eLink Recipient
Subject: Catalog default on created Livelink item

Catalog default on created Livelink item Posted by IDNordicAdmin (Salgo, Magnus) on 08/20/2001 10:10 AM

We would like to change that when something is created in Livelink it will by default be displayed as a catalogue item in the Livelink interface instead of a list item. (dtree.catalog = 1)

Question where is the best place to customize ?

Regards
Magnus@ids.se

eLink User

Message from magnus <<A HREF="mailto:magnus@ids.se">magnus@ids.se> via eLink

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">eLink

Thanks

Is there any problem if you set the a value for an item where it is not supported ....

Regards

magnus@ids.se

John W. Simon, Jr.

Magnus,If you don't already have it...you might want to look into creating an index on the catalog column in dtree. As we added more and more cataloged items our performance really began to suffer (until we added this index).Regards,John Simon

Pfizer_Developers

JohnThanks for the tip - improved performance considerably.At the moment we're going through a database tuning exercise. There are a number of hard-coded queries in the LiveLink code that are less than optimised. For example:"select * from notifymessages where userid in (select id from kuaf where deleted=1)" takes 160 seconds. Changing it to:"select * from notifymessages where userid in (select id+0 from kuaf where deleted=1)", reduces the query down to less than .5 second. Looks like the only way we can refine these queries is to create patches for each of the 'offending' scripts.Nick