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

Question 3 - TeamSite Forms: Logically Grouped Fields

cali2121

Autonomy Dev Community,

Does anyone know if it is possible to:

1) Have a series of associated form fields, that are all associated with one single label/header for those fields?

2) Have a free floating text box associated with a series of associated form fields?

3) Have flexibility in the form layout, where instructional text is placed to the right of a field or set of fields, instead of directly below it?

Any feedback would be appreciated. Thanks!

Find more posts tagged with

Comments

Rick Poulin

Starting to sound like a broken record, I'm sure.. Turns out you could have looped all of these questions into a single thread for us to answer "you can't" only once Smiley Tongue

1) Have a series of associated form fields, that are all associated with one single label/header for those fields?

Closest approximation is to use containers and/or tabs. Look it up in the docs.

2) Have a free floating text box associated with a series of associated form fields?

Not in any supported fashion, no.

3) Have flexibility in the form layout, where instructional text is placed to the right of a field or set of fields, instead of directly below it?

*giggles* @ flexibilility. I meant it when I mentioned "personal ****" in my answer to your first thread.

Adam Stoller

With respect to #2 - the closest thing that comes "supported" is rowcontinue="t" and a pre-populated textarea that is made read-only. However, this would only show up to the right of the first field, the other fields would all get pushed down.

I'm still working my way through your questions - but what I would strongly suggest (though it's effect is questionable) is to gather all of these together into a document (the diagrams and explanations of what you are attempting to do are very good) - and submit them to / through Support as a Feature Request. You might also CC Bill.Veghte@HP.com - the COO. I recently got a [form] email from him with the following:[indent]We’re investing to accelerate the innovation and importantly, we’re also investing to improve the customer experience, especially during implementation and post-sales support. Our goal is to combine the very best of Autonomy with the rigor of HP, which can bring a keen focus on customer satisfaction and building engineering processes that scale as the business grows.[/indent]It would be interesting to see what kind of response you get...

If you do file with Support - make a note of the case # and/or FR # (if they give you one) and post it here. A lot of us have struggled / given up struggling with the code used to render DCTs - but would probably be willing to lend their organization's names to the list of "interested customers" for them.

This is one of those things that GearUp was really good for - being able to "bend the ear" of the developers, product managers and such - unfortunately that kind of direct interaction no longer seems to exist.