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

Multiple pages in DCT

ruler

Gurus,

I have a DCT spanning to multiple pages making life miserable for end users, is it possible to have a button like next on the DCT at end of each page and on clicking it should take to the other page instead of scrolling down.

If anybody has done this kind of thing please share idea and code snippets. I

thanks

Find more posts tagged with

Comments

Johnny

At the begining of your datatype declaration in your templating.cfg you can specify how many items to display on a page. This way you can group your fields into different screen pages.

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

In reality I have only ever used 1 item per page and made that item a container to group all relevant items. It does mean that your dct can become a little structured towards screen orientation.

John Cuiuli

story.JPG

dataStructure.JPG

case2.JPG

ruler

Hi John,

Thank you so much, its really encouraging response, if you dont mind can you explain in little more detail or may be a sample template will really help.

thanks in advance.

Johnny

That's as much detail as there is.

The parameter is used to control how many item elements in the dct you want to display on a single screen page.

The key thing to remember is that it only deals with top level items. So only those items that are not nested within other items.

Essentially if you have 10 top level item elements in your dct and you specify 2 items per page, then your form window will be paginated with 5 screens displaying 2 items on each screen. Ofcourse those two items could have many nested items within them via replicants and/or containers.

Have a read of the templating manual if you need anything more.

There is nothing special you need to do to your dct so a sample is not needed.

John Cuiuli

ruler

Thanks again John,

My only question is there is a common set of questions we ask in the DCTS, I want to group them and call it into the DCT through a callout. If I do this will the items-per-page attribute still work ?

newStory.JPG

Johnny

Im not sure if i follow you.

A callout exists within an item element.

Are you talking about inline commands??... they are different to callouts.

The end result of inline commands is to produce a complete DCT and it is this end result that you will be interested in.

John Cuiuli

gzevin

ruler and John -

these are called 'inline callouts', as opposed to 'CGI callouts'. So the term callouts is valid in both cases.

Now - - ruler - yes, because the inline callouts are invoked at the time the DCT is loaded, they could be used.

Greg Zevin, Ph.D. Comp. Sc.
Independent Interwoven Consultant/Architect
Sydney, AU

structure.PNG

Migrateduser

From the tst developers guide:
The
items-per-page attribute is used to specify the number of items on each page in a data
capture form. The items-per-page attribute applies only to top-level items; therefore, a
container with many items still displays on one page and this attribute has no impact.