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

seting a replicant as Required/Opational

System

Like we can make the container (replicant) as readonly using setReadOnly( readOnly, recurse), is there any method available by which we can make the replicants required or optional?

Find more posts tagged with

Comments

Adam Stoller

setReadOnly() seems to be the only function that has a recursion option.
setRequired(true|false) only acts on one item at a time, so you'd have to recurse through the desired items and do a setRequired(...) on each one individually.

--fish
Senior Consultant, Quotient Inc.
http://www.quotient-inc.com

Bhargav Coca

yes you can make the replicant optional. By this ,i mean if an end user enters any data in the replicant, it will be shown in the generated page, else it will vanish. One can always play with the presentation template to create any thing the way you want it, to be there or not. There is yet an other option where you can use a option tag before declaring you replicant in your dct and make it OPTIONAL. Which ever way you choose it to be convinient to you.
Jessica

Adam Stoller

"you can use a option tag before declaring you replicant in your dct and make it OPTIONAL"

Uhm - the only option tag in the DCT is for things like radio buttons and checkboxes - if you want to declare an item as being required or optional in the DCT you do so with the 'required' attribute, which is set to either "t" (required) or "f" (optional).

However, the original question seemed directed towards FormAPI manipulation of items to dynamically change them from required-to-optional or vice-versa, as opposed to the static declarations of those items within the DCT.

--fish
Senior Consultant, Quotient Inc.
http://www.quotient-inc.com