nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Replicant Performace issue

Reghu

Hi,
In my DCT, there is a replicant named CITY, which holds the cities across the world(max replicant size is 150).
I have a requirement to associate more than 100 cities(ie more than 100 replicant elements) in a single DCR.

The issue is, when I associate more than 90 - 100 elements the performance of the DCR is getting very slow, its not getting opened up most of the times.

Is there any limitation in TS, regarding the replicant size with respect to performance.

Please help me in this regard...

Thanks,
Reghu.

Find more posts tagged with

Comments

mstradling

To the best of my knowledge there is no limit in TeamSite/Forms Publisher as to the max number of replicant instances. The only limits come about as a result of the web client your using, and it's ability/efficiency at handing JavaScript.

You can squeeze the best performance out of the client by:
- Adding more memory to the box.
- Switching to Netscape/Firefox (which generally handles large quantities of JavaScript better than IE).

No matter what you do, I've found 50 to be about the highest usable number. With IE, when you get close to 100 you need to start adding a replicant, saving, closing the DCR and then re-opening it to add the next or the browser window just dies.

To give you some other options, how about using an inline to pull back a multi-select list? The selected values get stored as a comma seperated list and adding another city to the DCR is just a metter of scrolling to it, holding down CTRL and clicking on it.

JonathonG

To give you some other options, how about using an inline to pull back a multi-select list? The selected values get stored as a comma seperated list and adding another city to the DCR is just a metter of scrolling to it, holding down CTRL and clicking on it.

Or, if you have users like I do who think CTRL-click is too difficult, you can use checkboxes. It looks pretty ugly for that many values, but our users have actually liked the checkboxes better than the multi-select list we had in previous versions....go figure

Jonathon
Interwoven Developer
Allstate, Inc.

smenon

We have also made some changes to the product to handle these large replicant cases a little better.. As pointed out, when the number of replicants and the size of the DCR grows large, IE starts to perform very poorly at handling the large volume of javascript. There are a couple of best practice recommendations as well as small product enhancements that might make the user experience better in this case..

1. Load the form with the replicants all collapsed.
2. If the replicants are all collapsed, then how do users find the node that they want to update or add to. We have added a small feature that allows you to designate the value of a field in the replicant container as the title field. Forms Publisher will display the title field on all the collapsed replicants so that you know where to go to.
3. We have also added a simple keyword search field at the bottom of the page that renders the Form. Using this simple keyword search field, you can search for a value and hit next and it will take you to the node in the DCR that contains that value - even if the value was in a replicant that is collapsed. You can also hit next and navigate to the next instance of that keyword you used for search. You must recognize that this is a very simple string match search solution built specifically to find values on the form. You cannot run complex search queries or add constraints etc. This is not meant to be a full-blown client-side form searching utility.

This was released as a patch on top of TS 6.5 SP2 recently and you might want to look into using it. I have to check with Engineering, but I believe that this is also now part of the TS 6.7.0 codebase and so you should get it by default in TS 6.7.0

thanks

--Sunil Menon
Sr. Product Manager
Interwoven, Inc.

cemman01

We are on TS6.1 SP2 on Windows and IE is the only allowed browser. Our clients are using a large number of replicants and as mentioned in this thread, experience severe peformance issues.

Could you confirm if the fixes you have mentioned below apply to TS6.1SP2?

Thanks.

Frederik

2. If the replicants are all collapsed, then how do users find the node that they want to update or add to. We have added a small feature that allows you to designate the value of a field in the replicant container as the title field. Forms Publisher will display the title field on all the collapsed replicants so that you know where to go to.
...
This was released as a patch on top of TS 6.5 SP2 recently and you might want to look into using it.
...
--Sunil Menon
Sr. Product Manager
Interwoven, Inc.

Hi,

My end-users are asking for exactly this thing. We have TS 6.5 sp2 + patch ID 1614, which supposedly includes the fix

* Bug ID 62190 Add title attribute to replicant instance to enable labeling of collapsed replicants.

Yet I can't get it to work. Where are the exact specs for this feature?

I only have 1-2 days left to include this in an upcoming release... otherwise they'll have to wait months Smiley Sad

Frederik

After couple hours trial and error, I finally found the way to get this to work: one should use the attribute isTitle="t|f" on the item in the container/replicant that will give its name to the "collapsed container".

Unfortunately, what I need is more complicated. I need the container to get its name from an item in a deeper (nested) container.

Here's an example : (simplified) copy of my DCT (which dates from TS 5.5.2). I want the item /nav_module/level1/level/link/label to be the label for the replicant /nav_module/level1

[HTML]

navigation/nav_module

[/HTML]
Guess I'm out of luck Smiley Sad

Ideas, anyone?

cheers, Fred.

Frederik

Today I discovered a hack to set the replicant title via formAPI and regular HTML DOM... based on the ideas in this thread Setting Container Label Dynamically with FormAPI (frogman)

Here's some simplified code... (the original is using function call recursion because there's a nested structure of 7 levels).

CAVEAT: You shouldn't use replicant-render="collapsed", then it doesn't work for replicants that aren't shown yet on form load :-(

[HTML]<script> function setTitle(item, s) { // hacky way to get the ID of the HTML DOM object which contains the label text // http://devnet.interwoven.com/forums_vb/showthread.php?t=10141&page=1&pp=10 var title_ID = "replicant_instance_title_" + item.itemImpl.instanceID; try { //top.document.formframe.document.getElementById( title_ID ).innerHTML = s; // IE-only top.frames['formframe'].document.getElementById(title_ID).innerHTML = ".[" +s+ "]"; // IE + Fx :-) } catch (e) { } // Ignore for now. } function init() { var levelItems = IWDatacapture.getItem("/level1").getChildren(); for (var i=0; i < levelItems.length; i++){ var item = levelItems; var title = IWDatacapture.getItem(item.getName() + "/level/link/label").getValue(); setTitle(item, title); item.setCollapsed(true); } } IWEventRegistry.addFormHandler("onFormInit", init); </script>[/HTML]

Obviously this isn't long-term supported, but it's interesting workaround ;-)

Doesn't seem to work with Firefox, only IE so far.

EDIT: code sample fixed to be Fx and IE compliant

Frederik

FYI :
Filed a feature request: FR 69083 - Client wants to be able to set the "replicant title" via FormAPI.

yuvpurush

2. If the replicants are all collapsed, then how do users find the node that they want to update or add to. We have added a small feature that allows you to designate the value of a field in the replicant container as the title field. Forms Publisher will display the title field on all the collapsed replicants so that you know where to go to.
3. We have also added a simple keyword search field at the bottom of the page that renders the Form. Using this simple keyword search field, you can search for a value and hit next and it will take you to the node in the DCR that contains that value - even if the value was in a replicant that is collapsed. You can also hit next and navigate to the next instance of that keyword you used for search. You must recognize that this is a very simple string match search solution built specifically to find values on the form. You cannot run complex search queries or add constraints etc. This is not meant to be a full-blown client-side form searching utility.

This was released as a patch on top of TS 6.5 SP2 recently and you might want to look into using it. I have to check with Engineering, but I believe that this is also now part of the TS 6.7.0 codebase and so you should get it by default in TS 6.7.0

thanks

--Sunil Menon
Sr. Product Manager
Interwoven, Inc.

Hi,
Has anybody used this feature in 6.5 SP2. If yes, can you pls let me know the patch id of this above mentioned feature.

Frederik

number 2 above -> PatchId 1614: Patch 63625 for TeamSite 6.5.0 SP2 for Solaris; Build Date: 20051128
* Bug ID 62190: Add title attribute to replicant instance to enable labeling of collapsed replicants.

number 3 above (probably) -> PatchId 1625: Patch 64369 for TeamSite 6.5.0 SP2 for Solaris; Build Date: 20051219
* Bug ID 64368: Forms Publisher javascript/html reduction and DCR search capability for performance improvement of large forms with replicants.

We have PatchId 1614 installed and use the title attribute...

I have no clue about the other fix "(3)", but I would be interested in hearing of those who do use it.

yuvpurush

Hi Frederik,

Thanks a lot.