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

Finish Button Issue

swati_27

Hi All,

We have around 25 DCT in our environment, we have one common field "name" across templates which we have recently made mandatory.

Users have already created a lot of content in the CMS and since we have made this "name" field mandatory at this instance we have observed two behavior:

1. On creation of new DCR the validation for "name" works as expected both on save and finish.

2. On opening an already saved dcr, clicking on save also works as expected and displays the message at the bottom sayng "required fields have not been filled".

3. On opening an already saved DCR, making changes to the content and leaving "name" field blank then clicking on finish also displays the error message.

4. On opening an already saved DCR, making NO changes to the content but simply clicking on finish doesn't display the error message at the bottom.

Scenario 4 is a little bit confusing as on some dataTypes it does display the message when simply opening and clicking on finish however on some dataType is doesn't display the error message.

What should be the expecetd behavior? Should the message be displayed or not?

Find more posts tagged with

Comments

swati_27

To add to it we are on TeamSite 7.3.2, RHEL. Any configuration file that we need to check. The logic on all the templates is same.

Rick Poulin

It's expected behaviour. Basically, when you make no changes, the form is not considered to be "dirty" and thus formspub doesn't bother actually trying to save (and thus, no validation). If you want to force validation for your new field no matter what, you'll have to use an onSave handler to do so.

swati_27

Thanks for your reply.

If this is the default behavior , why for some of the templates I am able to see the message even without any changes. Not sure on this? The logic is same accross all the templates. Out of 25 templates , 20 templates are showing the message on finish without performing any changes but only 5 are not displaying.

Adam Stoller

You're the one with access to the files - so only you can examine them to try to determine the differences between them that might cause some to display the error and others not to.

Rick Poulin

Those templates might have something in an onFormInit handler that always "dirties" the form.. but as ghoti said, we can't do much more than guess without seeing some code.