Quote:
Originally Posted by venganewt
You said the code is not complete -- I assume you intended to accomplish only the basic functionality (i.e., the Response Type list being dependent on the chosen Case Type, and each chosen Response Type populating the corresponding numbered paragraph), and not the more advanced functionality (i.e., having the "Common" responses appear as list items for all Response Types rather than "Common" itself being a Response Type, and the functionality I described in the highlighted portions of the template).
|
No, but I didn't want to go too far down the coding road only to find I was acting on the wrong premise. With Case Types, for example, the code presently only allows you to have one. Similarly, if you choose a Response Type, that type is removed from the next dropdown to prevent the same Response Type being chosen more than once. And, if the user goes back and changes a previously-selected Response Type, all subsequent Response Types that might have been chosen are deleted. Clearly, if users can switch Case Types, the current approach isn't going to work and responsibility for maintaining the nexus between Case Types and successive choices of Response Types may end up falling more heavily on the user.
I'm not sure what lies behind the error message you were getting, but it may cease to be an issue once the above is addressed.