Select Box value not showing on RITM/TASK

Mike McCall · ‎07-12-2016

I currently have a select box variable with no actual "choices" defined. On the catalog item (submission) form, a catalog client script dynamically adds options when the page loads. Once the form is submitted, the database stores the selected text value, even though that value doesn't map to a real "choice."

As of Fuji Patch 11, I could open RITM or TASK records and see the text value showing on the form. When we upgraded to Helsinki Patch 1, those two form views stopped showing the text value; they now just default to "-- None --."

What's especially interesting is that I can preview RITM or TASK records and see the text value properly showing in the variable field. Actually opening the form view must be rendering the drop-down (while the preview just shows read-only text).

Mike McCall · ‎07-20-2016

It is a bug! (PRB679673, to be exact)

Sure enough, a drop-down variable value stored in the database just won't render on RITMs/TASKs when the drop-down list is generated on-the-fly (and not using regularly defined question choices).

I'm told a fix is coming in Istanbul, and there are at least two potential workarounds for now:

Create an additional script for RITM/TASK to query the Variable Ownership [sc_item_option_mtom] table and populate the value onLoad
Make the variable read-only after submission (e.g., using Read Roles)

Obviously, #2 involves committing to values that can't change after submission, but I got that commitment from my stakeholder, so we're taking the easy way out!

View solution in original post

Chuck Tomasi · ‎07-12-2016

Check your catalog client script and ensure the correct settings on these boxes.

Chuck Tomasi · ‎07-12-2016

FYI Create a catalog client script

Mike McCall · ‎07-12-2016

Thanks, Chuck! In this case, I'm actually not looking to apply the catalog client script beyond submission (though I'll never forget when those three checkboxes first became available--glorious!).

Once the record is submitted, I don't need to dynamically populate any options in the variable because the value doesn't need to be further updated. In the past, the selected value would just display. (If you investigated the drop-down, you'd find that it was one of those "non-selections" that show at the bottom of the list in blue.)

I'm not sure I'd ever consider this new behavior a "bug." I'm populating a variable with a value that's not actually a choice; shame on me!

However, it was definitely a nice workaround before upgrading to Helsinki, so I'd love to know if this was an expected change (or if there's a newer, shinier workaround I can put in place).

Chuck Tomasi · ‎07-12-2016

It must be a variable thing because invalid choice values on fields still show up in blue on the list

and unaffected on the form.

Kind of feels like a bug. If it were me, I'd open a HI ticket anyway just to see.