I'm using followup in my result-view. When user answer with "yes or
no" thats works well.
But what if the user answer with something else like "I don't know" it
will start the default-action .
I want to handle that case to re-display the result-view with the same
input values (properties).
I am now able to experience the behavior that you desire. "Yes" takes me to the on-confirm step, "No" takes me to the on-deny step, and "I don't know" keeps me on the same view and asks the same question again.
Addressing your issue may require the team to investigate your code. In order to do so, please experience the behavior again, and submit a support ticket with the "Contact Support" option in the Bixby Developer Studio's Help menu.
Related
We have an language learning Action, where the user can ask say anything they want. When they say "dinner", our Action immediately quits, without saying the cancel response.
We tried several other Actions and they all behave the same way.
Except Google Translate that says "Something went wrong".
Is there a way for our Action to react on "dinner" somehow?
I think you should make another intent where you can mention "dinner" as a training phrase. Then you can give a response against that training phrase. This might solve your problem.
Let's say this user needs to answer A - B - C - D - E sth like this in the pre-interview setting for a job. Let's say while getting question C, this user wants to ask some questions like salary or sth, then this person got the answer for the questions.
After this person got the answer if the user says "go back" or "back," I want the user to get the question C again. So currently, because of the context piled up, if that user remembers the question and answer correctly like "yes", it smoothly goes to D question. But people can forget. Also, if it's 'required' like number or something I can just put prompt and put the question again, but in case of simple question like yes or no, i don't know how.
The thing you are looking for is follow-up intents. They allow you to perform specific actions when a user says yes or no. Follow the links below to know how to build follow-up intents to suit your application needs.
Official Dialogflow Guide - https://dialogflow.com/docs/contexts/follow-up-intents
Medium Article with Example - https://medium.com/google-developer-experts/mastering-follow-up-intents-with-dialogflow-851b75b83f5a
I'm using Cucumber and running BDD tests.
I'm unsure how to test that I stay on the same page. Suggestions are appreciated.
"Staying on the same page" doesn't seem valuable to me. As a user, I don't care that I stay on the same page.
I might care that, for instance, if I was looking at my basket, when I finish , I am still looking at my basket.
If I'm looking at an Acme 2000 Super Widget, when I finish, I'm still looking at the Acme 2000 Super Widget.
I often find a lot of BDD problems can be answered if I ask, "Can you give me an example of that?" So, can you give me an example of a page that you might want to stay on?
Those specific examples end up being scenarios. Your rule, "should stay on the same page", can go in the explanation at the top of the feature file to explain the examples below.
If you aren't using a one page app then you should just be able to assert based on the url. If you are using watir then
assert_equal 'http://www.yourpage.com', #browser.url
If you are using a different framework then there will be an equivalent.
Perhaps i am being stupid by asking this just now, but...
I notice that if I edit the input fields with chrome tools programmer they are changed in the page...what about the security?
Anyone know something about this?
Always validate user input server side.
I am creating a menu with the linux utility dialog (see below) and I have heard that it is possible to make a tree-like structure for those checklists. However I cannot find any type in the manpage that creates such a thing? Is it really possible - and if yes: how?
See http://i51.tinypic.com/2ir9qfl.png vs http://i56.tinypic.com/35jasmh.png for how it actually looks like and how it should look like. The original pic was created using dialog --checklist.
First and foremost thank you for the answerz. However the ambiguity of the word 'dialog' and the lack of a correct side by side comparison (couldn't double-check as I was unexpectedly hurried - sorry) made the question difficult to understand.
Hope this helps:
How it looks like: http://i51.tinypic.com/2ir9qfl.png
How it should look like: http://i56.tinypic.com/35jasmh.png
I still want to use the 'dialog' utility - I just want a tree-like view that shows that allows to group some items for better overview. It should be the front-end for a rather complex script that can checkout, compile, fetch and do some other fancy stuff, and the person who wanted me to do this script said that he is sure a tree-like view in dialog is possible as he had seen it before, could however not supply me with the necessary code.
You cannot use the Linux dialog utility to do a single page checklist hierarchy
Instead, create a series of menus to achieve the same semantic structure, far from optimal though, I'll grant you.
The other option is to write a script (in perl/python/ruby perhaps) which uses the ncurses/curses library to build this section of the UI. See here (python example) to help you get started.
Note.
The person who said they had seen a tree like view composed in dialog has either...
Seen it done with a patched/non-standard version of dialog which may exist. (?!)
Saw a custom made ncurses/curses app that provided a similar UI to dialog, hence the confusion.
For more info on ncurses/curses see http://www.linuxselfhelp.com/HOWTO/NCURSES-Programming-HOWTO/
The sample you posted will be difficult to match in formatting, but bash/ksh/zsh all support the select construct, which builds a menu and allows you to process the results of the selection.
PS3="Choose an option "
select opt in start mid end quit
do
case $opt in
start) echo "starting";;
mid) echo "Standing by";;
end) echo "Standing by";;
quit) break;;
esac
done
Example run
1) start
2) mid
3) end
4) quit
Choose an option
1
starting
4
# prompt >
Depending on your requirments, you may need to wrap this a continuous loop, i.e.
while true ; do
select ...
done
I don't think it will be possible to center the question tree as your example.
I hope this helps.
P.S. as you appear to be a new user, if you get an answer that helps you please remember to mark it as accepted, and/or give it a + (or -) as a useful answer.