Author Message
SteveBassett
Joined: Oct 5, 2015
Messages: 39
Offline
Our applications are failing when collecting the date 02/29/2016. It looks like the issue is occurring in the RDM (dated 2/27/2015).

########## RDM CHECK RESULT ##########
### Field Name: RESULT
### Prompt&Collect - Is Collection: false
### Prompt&Collect - VALUE: [undefined] VALID: [true]
######################################
### [RESULT] nextNode: RESPONSE
### [RESULT] nBestCollection Values: undefined
######################################

Has anyone dealt with this before?

Additional info...

RDM2:logResult | TRACE | outputVariables:utterance : 0 2 2 9 2 0 1 6]
RDM2:logResult | TRACE | outputVariables:value : undefined]
RDM2:logResult | TRACE | nBestValuesCollection : undefined]
RDM2:logResult | TRACE | disallowCollection : ]
RDM2:logResult | TRACE | PromptAndCollect:OTHER_SLOT : undefined]
RDM2:logResult | TRACE | outputVariables:confidence : 1]
RDM2:logResult | TRACE | outputVariables:inputType : dtmf]
RDM2:logResult | TRACE | outputVariables:returnCode : SUCCESS]
RDM2:logResult | TRACE | outputVariables:noMatchsRemaining : 2]
RDM2:logResult | TRACE | outputVariables:noInputRemaining : 2]
RDM2:logResult | TRACE | outputVariables:confirmationsRemaining : 2]
WilsonYu
Joined: Nov 6, 2013
Messages: 3950
Offline
It could be some recognition problem inside RDM2. Our team here has no control over it. It would be better if you contact Avaya support on this.
SteveBassett
Joined: Oct 5, 2015
Messages: 39
Offline
It turned out the grammars received from Avaya as part of out custom application delivery was missing one source line and did not returned the collected date.

var isLeap = new Date(yearSpoken,1,29).getDate() == 29;
if (isLeap == false) {SWI_disallow=1;}

We needed to add: " else RESULT = d;"

var isLeap = new Date(yearSpoken,1,29).getDate() == 29;
if (isLeap == false) {SWI_disallow=1;} else RESULT = d;
Go to:   
Mobile view