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 multi page forms...?

kjackson

Hi,

I have been reading the FormAPI documentation that ships with TS and in a number of pages it refers to "mulit-page" forms hwoever I can find no further information. EG. how do you create a multi-page form...?

Any suggestions or pointers to further documetation would be appreciated. I have tried searching devnet but have found nothing useful.

Regards,
Kerryn

Find more posts tagged with

Comments

mogoo

Are you trying to get multiple pages in the DCT? If so, all you've gotta do is add the items-per-page attribute to the data-type tag in templating.cfg...

<data-type name="WHATEVER" dcr-type="iwov" items-per-page="1">

-maureen

bodo

Hello,
I think it's not working with dcr-type="xml" ? (We are using dcrs based on an own dtd)
Greetings,
Bodo

mogoo

Don't know about dcr-type="xml", haven't used it...
Are you using replicants? It doesn't work with replicants.
maureen

Johnny

It only works with the top level items.

So the only practical way of using them is to group each page inside a container tag.

Like mogoo mentioned, it wont page break items inside a replicant ---> only top level items.

John Cuiuli
Consultant
Sydney, Australia

kjackson

Thanks for the information. Can you direct me to some documentation on details of how this works?

Thanks,
Kerryn

mogoo

Kerryn-
The only place I've seen it mentioned BRIEFLY is p.91 of the v5.5 Templating Guide... I mostly just figured it out by trial and error. Most fields are considered 1 item... replicants are 1 item, even if the user adds 100 of them in the DCR... containers are 1 item -- so you can put 10 fields inside a container, and those 10 will appear on 1 page.
Hope that helps!
maureen

Adam Stoller

It's not so much what constitutes "1 item" as it is what constitutes a "root item". E.g.:

<item name="A"><text/></item>
<item name="A"><replicant><item name="B"><text/></item></replicant></item>
<container name="A"><item name="B"><text/></item></container>

In all 3 cases above the element with the name "A" is considered a root element - the element with the name "B" is *not* a root element (even though it may still represent a single item in and of itself). The number of "root" items is what is used to determine how may fit on a page.

As has been said, a replicant can contain any number of sub-items, as can a container element - the number of sub-elements is *not* used to determine how many fields appear on a page.

--fish
(Interwoven Senior Technical Consultant)

mogoo

well illustrated, ghoti! Thanks for the clarification...