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; } } }

FormAPI and Replicants

hessian

This has been asked and almost answered a few times so I thought I'd try again in case the state of the art has been advanced or become better understood...

How does one add an itemhandler to a field in a newly created instance of a replicant? All I want to do is show hide things based on checkbox clicks. Is there a "new replicant" event that I can use to trigger an exhaustive relooping through all replicant instances or, more efficiently, the one just opened, to set handlers?

Also, regarding callout buttons... I assume I've still got to tie these to hidden dummy fields in order to hide/show them. Has anyone done this inside a replicant?

INTERWOVEN: In future documentation, do your corporate self a favor and please write the "hard" stuff first! For example, I'd love to see some copy-n-paste FormAPI examples dealing with "realworld" templates where replicants and nested replicants are commonplace. The small amount of effort expended to do this would more than pay off by reducing the noise here and on tech support calls and increasing the productivity and happiness of your customers. And, when creating these realworld examples, you'll probably wind up enhancing the QA effort and discover a few feature holes too.

Find more posts tagged with

Comments

Migrateduser

As far as I know, this is the only way, and it's not really supported (may break with future releases).

http://devnet.interwoven.com/forums/cgi-bin/showthreaded.pl?Cat=&Board=PRODUCTS_TEMPLATING&Number=29817&Search=true&Forum=All_Forums&Words=addListener&Match=Entire%20Phrase&Searchpage=0&Limit=25&Old=allposts&Main=29686

Not sure about the callouts question.

Dwayne

If the goal is to have an item handler for every instance of a given item in a replicant, it's actually pretty simple (although not documented). Just treat the replicant as if it were a single item in the path to the target item. As an example, if you've got a replicant called "Paragraphs" that contains a field called "Bold", and you want an item handler to be notified whenever the "Bold" item changes, then you could use something like this:

IWEventRegistry.addItemHandler("/Paragraphs/Bold", "onChange", myBoldHandlerFunction);

Now all of the "Bold" items in the "Paragraphs" will call myBoldHanderFunction whenever they change.

--

Current project: TS 5.5.2/6.1 W2K

Migrateduser

This syntax does work, but since it's not documented, will it continue to work in future releases, and if so, why isn't it documented? This saves a lot of hassle.

test.rptdesign

hessian

THANKS! for highlighting a link I glossed over previously. The technique still works as of TS 6.1.0 Windows.

hessian

FYI: This did not work for me and my nested replicant until I used the full path (/root/container/text/text_attribute). Very nice how items in new instances of replicants are "handled" automatically. THANKS!

bboyle

what do you mean it's not documented? It's documented to work exactly as you said! Smiley Happy

https://support.interwoven.com/library/manuals/templating/html/formapi1.0/formapi_6.html#SEC6

Node c is a replicant. The address of the first instance is `/a/c[1]', while that of second instance is `/a/c[2]', and so on.

To intercept the `onItemChange' event on all instances of node c item, simply register a handler to the address `/a/c':

IWEventRegistry.addItemHandler("/a/c", "onItemChange", handle_c_changed);

This is called the prototype path for all c instances. Note that a prototype can only be used in registering event handlers for replicants. It cannot be used in finding items.

pawlr

I understand all of the above postings for this thread, but I'm still unable to do something I'm trying to do.. basically I have replicants of pairs of data (a select pulldown and a textarea). I want the select pulldown to to trigger an event function that modifies the corresponding text item for each replicant. Is there a way to get the "index number" of what replicant you're on so you can use that to set the value of the corresponding text item?

Any help is appreciated.. I noticed in the documentation that "It cannot be used in finding items. ".. does this mean I can't do what I want here?

Edited by pawlr on 08/12/04 03:11 PM (server time).

herald10

Heres something I suggest.

function init()
{
IWEventRegistry.addItemHandler("/XPATH/TO/REPLICANT","onItemChange",initialize);
}

function initialize(item)
{
var itemname = item.getName();
}

init();

Here if you can output the itemname using an alert, you can see the index number. You can use some regex to grab the index number you are looking for.

HTH
-H

pawlr

this sounds like it should work, I'll give it a try, THANKS A LOT!

pawlr

That totally worked.. I'll post the code if anyone cares.

Migrateduser

Please consider submitting the code to the technical library, where it will be easier to find code snippets in the future.

Thanks.

lissa

Jamagui

I'm not sure if any of the above solutions solve my problem. I'm trying to show/hide multiple items that are nested within multiple replicants, such as replicant/replicant/replicant/itemOne
replicant/replicant/replicant/itemTwo.
Is there a way to address to these items and account for all replicant possibilities? It, of course, works if I place position numbers after each replicant, but I need it to work for all replicant positions. We are currently using 5.5.2.

herald10

As far as I know, you will have to use a loop construct to execute setVisible to false on all the replicant items. you can access the generic replicant only while associating with the item handlers.

Hope that helps,
-H

Anip

Hi - did you ever post the code anywhere? I'm interested to see it.

cheers
Ani