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

Can’t Preview in DCR View mode due to "required" fields

fiquebem

We’re using TS 6.7.2 SP2 on Windows.

We understand that, in DCR View mode, FormAPI/JavaScript is disabled. Because of that, FormAPI cannot dynamically flag required fields as optional. Thence, if FormsPublisher/Templating notices that required fields (actually, required only until FormAPI makes them optional) have not been populated, it figures the DCR at hand is incomplete so it doesn’t allow the user to proceed to Preview.

We could resolve this issue by analyzing all the Forms and determining which “required” fields can be made optional safely, without risks. We could mark all fields as optional and hope that FormAPI code is already in place to catch input errors. Or add such FormAPI code. This task could take a significant amount of time. We’re wondering whether you have any other suggestions. For example, is it possible to customize TS to allow Preview even when a DCR is “invalid,” at least when a user is simply viewing it?

Thanks!

S.

Find more posts tagged with

Comments

Adam Stoller

What you should do is reverse your FormAPI logic.
Any field which can be optional, should be defined as not required in the DCT and only made required by FormAPI.

nipper

Because of that, FormAPI cannot dynamically flag required fields as optional. Thence, if FormsPublisher/Templating notices that required fields (actually, required only until FormAPI makes them optional) have not been populated, it figures the DCR at hand is incomplete so it doesn’t allow the user to proceed to Preview.

We’re wondering whether you have any other suggestions. For example, is it possible to customize TS to allow Preview even when a DCR is “invalid,” at least when a user is simply viewing it?

Hey Shah

Hmm, I did not think that FAPI could override required, maybe it is only hidden or one of the other parameters

TST has the ability to save incomplete DCRs, I am not certain where that setting is defined, but that may help.

I agree with Fish that you should make handle it all on FAPI. If you remove the required parameter (for the fields in question) and on forminit, set those to required, then the functionality should be the same without too much rework,

HTH