Thanks, Breno.
Yeah, in these cases, it isn't about breaking down business logic. It's literally a Collect Input, with the success path going to a Decision that simply verifies that an appropriate number of digits have been entered. If so, the input is processed and all is good. If not, it's treated the same as the failure path from the Collect Input.
I thought I was going mad, but it looks like this is redundant error checking and I can safely remove it. Like I said above, I was just concerned that there was some well-known edge case that makes this necessary. (Having seen it a few times, I was getting suspicious!)
------------------------------
Paul Simpson
Views expressed are my own and do not necessarily reflect those of my employer.
------------------------------
Original Message:
Sent: 04-30-2024 11:24
From: Breno Canyggia Ferreira Marreco
Subject: Maximum Data entry from Collect Input
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,
------------------------------
Breno Canyggia Ferreira Marreco
https://www.linkedin.com/in/brenocfm-40b62182/
Original Message:
Sent: 04-30-2024 10:28
From: Paul Simpson
Subject: Maximum Data entry from Collect Input
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. 😣
------------------------------
Paul Simpson
Views expressed are my own and do not necessarily reflect those of my employer.
Original Message:
Sent: 04-29-2024 20:37
From: Robert Wakefield-Carl
Subject: Maximum Data entry from Collect Input
You are correct. It will not accept 4 or fewer or more than 10 digits. Are you seeing different?
------------------------------
Robert Wakefield-Carl
ttec Digital
Sr. Director - Innovation Architects
Robert.WC@ttecdigital.com
https://www.ttecDigital.com
https://RobertWC.Blogspot.com
Original Message:
Sent: 04-29-2024 17:09
From: Paul Simpson
Subject: Maximum Data entry from Collect Input
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
#ArchitectureandDesign
#Implementation
------------------------------
Paul Simpson
Views expressed are my own and do not necessarily reflect those of my employer.
------------------------------