Multiple Data Types - Single DCT

I have a situation where I have multiple data types and would like to use a single dct to display the appropriate Data Capture Form to the user after they have selected the data type from a pull down list box. Each data type has a unique Data Capture Form. I know the Interwoven doc says to split these up into single data capture form, but I wanted to see if there was a way to incorporate the multiple data capture forms into a single dynamic dct.

Any suggestions would be greatly appreciated.

Find more posts tagged with

Comments

Adam Stoller

I have a situation where I have multiple data types and would like to use a single dct to display the appropriate Data Capture Form to the user after they have selected the data type from a pull down list box. Each data type has a unique Data Capture Form. I know the Interwoven doc says to split these up into single data capture form, but I wanted to see if there was a way to incorporate the multiple data capture forms into a single dynamic dct.

Any suggestions would be greatly appreciated.

Primary suggestion - don't try to do it.

Alternative: You create a huge DCT with all the various fields you want in it and put together a lot of FormAPI code to toggle the visibility (and required-ness) of the various fields based upon a select list that is always visible.

The time to develop, debug, and maintain over the the long term makes the alternative a bad choice IMO.

nipper

Primary suggestion - don't try to do it.

Alternative: You create a huge DCT with all the various fields you want in it and put together a lot of FormAPI code to toggle the visibility (and required-ness) of the various fields based upon a select list that is always visible.

The time to develop, debug, and maintain over the the long term makes the alternative a bad choice IMO.

While I somewhat agree with the above statement, it is the requirement of way too many companies. I have some really fun JS on my current project. It works great and the customers love it. The ones that do not love it are the guys who will get to support this a year or two down the road.

Andy

frbcraig

Andy and Fish,

Thanks for your replies, they are much appreciated. We are trying to talk the data owner out of this requirement for the very reasons you suggest (supportability and maintainability - plus the cost of development). But, if we do have to go down this road - are there any examples showing the JavaScript that we can use as a model??

Craig

nipper

No but make your life easier, put the different "types" in different containers. Then make those visible or not per the type selected (say from a pulldown).

You will still have some complex parts (making various fields required or not depending if it is visible).

Finally one piece of advice. Make the type readonly after it is initially set. This means that a user cannot change the type in mid stream. Usually not a problem. However if you cannot do that, then you have a lot of ugly testing, going from type A to C, etc. I have found way too freaking many errors in corner cases there.

HTH

Andy

FurnaceFace

Env: TeamSite 6.7.1-SP1 on Solaris 10

Hello,

Good tips Ghoti & Nipper! I have a client who has pretty strong convictions about going down this road as well and each different data type (4 at the moment) has up to 6 visual format controls, sSome of which are in replicants. By this I mean, there are 3 visual format boxes on the regular form and 3 visual format controls that can be found in replicants.

I know there are issues with nested replicants that contain visual format controls and that there can be performance issues with too many VF controls on the same form (they are loaded on demand by the way). Does anyone have any advice on issues they had when implementing multiple data types into one DCT that contain many visual format controls?

Thanks,
/FF