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

DCT Rules Change in 6.7.2 regarding tabs?

tvguide_dev

We just upgraded our test server and are experiencing this problem...

Invalid DCT: tab is defined in dct, all the containers, items, etc. must be within tabs

We have many forms that have hidden fields outside of tabs. They are all breaking. They work fine in 6.7.1sp1.

Moving the hidden items into tabs results in different output DCR paths. which are causing our Data Deploys to fail. And to top it off, our workflow extensions need to be re-written to find the hidden items after they've been moved into the tabs.

In short, this change is causing major pains. It may even be a dealbreaker. Where is it documented? Is there a workaround to changing all our existing code and files?

-Dan Tepper
TV Guide Online

Find more posts tagged with

Comments

vpatel

We just upgraded our test server and are experiencing this problem...

We have many forms that have hidden fields outside of tabs. They are all breaking. They work fine in 6.7.1sp1.

Moving the hidden items into tabs results in different output DCR paths. which are causing our Data Deploys to fail. And to top it off, our workflow extensions need to be re-written to find the hidden items after they've been moved into the tabs.

In short, this change is causing major pains. It may even be a dealbreaker. Where is it documented? Is there a workaround to changing all our existing code and files?

-Dan Tepper
TV Guide Online

Tabs have no impact on the output of the DCT's XML (DCRs). Tabs are there for visual purposes only and it may have some impact on FormAPI code that you may have. Your problem might be elsewhere.

tvguide_dev

You're right - I hadn't actually gotten as far as getting to the output, but formAPI definitely breaks and in our case this is going to require a significant amount of engineering and testing across some 20 forms and a dozen perl and javascript files we use for API extensions

Which only figures - because all our "unauthorized" hacks still work perfectly without modification.

-Dan

vpatel

Something still doesn't sound right. You can post your original DCT and see if you can get help here.

tvguide_dev

Thanks,

Actually it makes perfect sense, and when I add the Tab Name to my paths in our FormAPI code it all works as before.

Its just a lot of files to edit and retest and redeploy live. The kind of breaking change I would expect from MS - not Interwoven(!)

-Dan

tvguide_dev

Is it possible to make a tab hidden ?

vpatel

Thanks,

Actually it makes perfect sense, and when I add the Tab Name to my paths in our FormAPI code it all works as before.

Its just a lot of files to edit and retest and redeploy live. The kind of breaking change I would expect from MS - not Interwoven(!)

-Dan

I am still thinking that something else is causing it. You may want to post your DCT on here.

vpatel

Is it possible to make a tab hidden ?

Remove the tab?

ccprofessional

Is it possible to make a tab hidden ?

tabToBeRemoved.setVisible(false) hides all the content in the tab, but not the tab itself.

Adam Stoller

We just upgraded our test server and are experiencing this problem...

We have many forms that have hidden fields outside of tabs. They are all breaking. They work fine in 6.7.1sp1.

Moving the hidden items into tabs results in different output DCR paths. which are causing our Data Deploys to fail. And to top it off, our workflow extensions need to be re-written to find the hidden items after they've been moved into the tabs.

In short, this change is causing major pains. It may even be a dealbreaker. Where is it documented? Is there a workaround to changing all our existing code and files?

-Dan Tepper
TV Guide Online

It appears that the earlier version of TS may not have validated the DCTs according to the DTD, and now it is - so IMO, this is a case of user-error on the part of the DCT developers.

Looking at the TS671SP1 FormsPublisher Developer's Guide - where it shows the DCT DTD - it shows:

...
<!ELEMENT root-container(label?,((tab)+|(container|item| choice|dialog)+))>
...

Which, in English, means: A root-container element contains an optional label element followed (if present) by either one-or-more tabs or one-or-more container, item, choice, and/or dialog elements.

If you had tabs, and you had items outside any tabs - that does not conform to the DTD - and apparently the system is now catching it as a violation.

I suppose you could say that there was a bug in the previous version which allowed what was done before to work - but the DTD hasn't changed here, only the strictness to which it needs to be followed - and thus this is a "user-error" issue, not (any longer) a product bug.

tvguide_dev

Thanks for all the help and info. I guess we missed this in our original implementation.