Hi,

I'm seeking confirmation of what (I believe) I already know...

If I configure a "Collect Input" action within an Inbound Call Flow, and configure it to require (say) 5-10 digits, with a terminating DTMF of "#" (not included in input data) then there is no way the input can be longer than 10 digits, correct?

TIA

You are correct.  It will not accept 4 or fewer or more than 10 digits.  Are you seeing different?

Hi,

I'm seeking confirmation of what (I believe) I already know...

If I configure a "Collect Input" action within an Inbound Call Flow, and configure it to require (say) 5-10 digits, with a terminating DTMF of "#" (not included in input data) then there is no way the input can be longer than 10 digits, correct?

TIA

Thanks, Robert!

No, I'm not, however I have seen quite a few flows (written by a variety of engineers) where the Collect Input action's success path leads to a decision that checks that the returned data length is within the required range. This led me to wonder if there was a situation I was unaware of where this can happen.

I'm coming across the same thing where an exact number of digits is requested. If the caller does not enter the required digits, I expect the failure path to be taken, but I'm seeing the data length being verified in the next step on the Success path.

Based on my own understanding, and your response, it looks like this is merely an over-abundance of caution and unnecessary additional complication to the Flow. I didn't want to tidy up these Flows and then find that I have introduced errors that I was unaware of. 😣

You are correct.  It will not accept 4 or fewer or more than 10 digits.  Are you seeing different?

Hi,

I'm seeking confirmation of what (I believe) I already know...

If I configure a "Collect Input" action within an Inbound Call Flow, and configure it to require (say) 5-10 digits, with a terminating DTMF of "#" (not included in input data) then there is no way the input can be longer than 10 digits, correct?

TIA

From my experience, if you use 5 to 10 and you enter 4, it will wait for timeout and then take failure.  I believe that is the case for 11, but I do remember an issue early on where it would just accept the 10 and ignore the 11th.  

Thanks, Robert!

No, I'm not, however I have seen quite a few flows (written by a variety of engineers) where the Collect Input action's success path leads to a decision that checks that the returned data length is within the required range. This led me to wonder if there was a situation I was unaware of where this can happen.

I'm coming across the same thing where an exact number of digits is requested. If the caller does not enter the required digits, I expect the failure path to be taken, but I'm seeing the data length being verified in the next step on the Success path.

Based on my own understanding, and your response, it looks like this is merely an over-abundance of caution and unnecessary additional complication to the Flow. I didn't want to tidy up these Flows and then find that I have introduced errors that I was unaware of. 😣

You are correct.  It will not accept 4 or fewer or more than 10 digits.  Are you seeing different?

Hi,

I'm seeking confirmation of what (I believe) I already know...

If I configure a "Collect Input" action within an Inbound Call Flow, and configure it to require (say) 5-10 digits, with a terminating DTMF of "#" (not included in input data) then there is no way the input can be longer than 10 digits, correct?

TIA

Thanks, Robert!

No, I'm not, however I have seen quite a few flows (written by a variety of engineers) where the Collect Input action's success path leads to a decision that checks that the returned data length is within the required range. This led me to wonder if there was a situation I was unaware of where this can happen.

I'm coming across the same thing where an exact number of digits is requested. If the caller does not enter the required digits, I expect the failure path to be taken, but I'm seeing the data length being verified in the next step on the Success path.

Based on my own understanding, and your response, it looks like this is merely an over-abundance of caution and unnecessary additional complication to the Flow. I didn't want to tidy up these Flows and then find that I have introduced errors that I was unaware of. 😣

You are correct.  It will not accept 4 or fewer or more than 10 digits.  Are you seeing different?

Hi,

I'm seeking confirmation of what (I believe) I already know...

If I configure a "Collect Input" action within an Inbound Call Flow, and configure it to require (say) 5-10 digits, with a terminating DTMF of "#" (not included in input data) then there is no way the input can be longer than 10 digits, correct?

TIA

Hi Paul, I did need in the past to use the Input action between 11 and 15 digits, and next use Decision or Switch are used for rule business (if X digits the value is Y and is W digits Z) but out of this situation, you can consider the number entry only.

Att,

Thanks, Robert!

No, I'm not, however I have seen quite a few flows (written by a variety of engineers) where the Collect Input action's success path leads to a decision that checks that the returned data length is within the required range. This led me to wonder if there was a situation I was unaware of where this can happen.

I'm coming across the same thing where an exact number of digits is requested. If the caller does not enter the required digits, I expect the failure path to be taken, but I'm seeing the data length being verified in the next step on the Success path.

Based on my own understanding, and your response, it looks like this is merely an over-abundance of caution and unnecessary additional complication to the Flow. I didn't want to tidy up these Flows and then find that I have introduced errors that I was unaware of. 😣

You are correct.  It will not accept 4 or fewer or more than 10 digits.  Are you seeing different?

Hi,

I'm seeking confirmation of what (I believe) I already know...

If I configure a "Collect Input" action within an Inbound Call Flow, and configure it to require (say) 5-10 digits, with a terminating DTMF of "#" (not included in input data) then there is no way the input can be longer than 10 digits, correct?

TIA