Combination View Flat View Tree View
Threads [ Previous | Next ]
Hi,

I've noticed 2 potential bugs in Studio 5 (build 200605181826), which persist even after I've upgraded it to 5.1.3

1)I love that you've included known element data in the Substitution tg window, but the element data for the confidence should be 'value_confidence' instead of what's currently there which says 'confidence' and doesn't work.

2) When I test either the Date or Time elements thru a web browser the element data for the date.value is never filled in. The value_confidence is populated if I submit it, but not the 'date.value'

http://localhost:8080/Audium/Server?dateCollectField=20060131&collect_confidence=0.9

I've also tried the Time element, that also doesn't populate the time.value variable. The Digit and Number element work correctly though. The only big difference I see are that the field name for the Date and Time elements use a mixture of upper/lower case, whereas the Number and Digit elements use all lower case for their field names.

By the way, the 'Date with Confirm' element works okay.

Are these known bugs? Or am I doing something wrong?


Thanks, Janine

RE: Studio 5.1 bug?
Answer
11/28/06 10:39 PM as a reply to Janine Graves.
Janine,

While the "value_confidence" is the name of the variable that should be used in Substitutions, note that "confidence" works as well. If you look at the activity logs, for example Digits element, both confidence and value_confidence are set. Note that all elements with confirm will set two confidence variables - "value_confidence" and "confirmation_confidence". The elements without confirmation should set "value_confidence" only, as defined in the Element Specification. However, for backward compatibility, both "confidence" and "value_confidence" are set.

You are correct thou, only "value_confidence" should be visible in Substitutions. Note, however, that both variables - value_confidence and confidence - work fine and you should not be getting errors

The second topic refers to Call Services and testing using web browser, not Studio. We will look into this issue and post the update.

Regards,
Michael