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

Requiring comments

Trey

I have an approval task where I would like to make commenting required. Is this possible to do without digging in deep into the interface, or do I just make it something I train our users to always do?

Currently we are running TS 6.1 and going to 6.5 soon.

Thanks in advance.

Trey Wentz
Ferguson Enterprises, Inc.
e-mail: trey.wentz@ferguson.com

Find more posts tagged with

Comments

Lozza

I reckon there are two solutions to this:

The first is definitely the least unpleasant option for all concerned.

Trey

#2 sounds like I good thought, but what I am really hoping for is an option to validate it as it is done (like you can do with a dcr and forms publisher or with the built in validation a dcr has). Any other thoughts on this one or does that sound like a feature request in to IW?

Trey Wentz
Ferguson Enterprises, Inc.
e-mail: trey.wentz@ferguson.com

iwovGraduate

I would suggest you call support and file a feature request regardless of whether you find a workaround or not. The more customers request something, the more chances it will be done.