Flexible menu systems - arbitrary values for 'goto' step syntax
I think it would be REALLY useful if in my code I could output "<goto=2000>" (where '2000' is an abitrary number that I can map to a particular system state/menu option) and the next input I recieve from the bot would have a step of "2001".
This would enable developers to build far more flexible menu structures and handle input without having to process the entire previous set of user input values to establish in what state the bot is in.
Effectively, developers can set an arbitrary value of 'step' to track bot/application state, where each step value can map to a unique application function/state.
is this be possible? It would make life a LOT easier :-)
Infact, if this were possible, perhaps 'step' could be a text value? whereby I sent "<goto=MAIN-MENU>" and you could reply with a step of "MAIN-MENU_1"
Comments are currently closed for this discussion. You can start a new one.
2 Posted by Dave Hoff on 27 Jul, 2009 01:41 PM
Thanks for the suggestion. Interesting idea. We're talking this over internally. Anyone else have a need for this functionality?
3 Posted by tcarnell on 27 Jul, 2009 02:36 PM
I suppose what I'm really after is a form of session support that would enable an 'end-point' application to store/retrieve state data against a particular 'chat session', for example. If imified always supplied the end-point with same value for a 'session_id' parameter for a given 'chat' then the above requirement would not be needed:
$sessionId = $REQUEST['session_id']; (where $sessionId = IMIFIFIED=123456789-blablabla)
I think this would probably be the ideal solution and would be far more poweful than for just menu navigation.
(BTW, thanks for the feedback above)
Support Staff 4 Posted by Adam Kalsey on 27 Jul, 2009 05:01 PM
You could always track the session and conversation yourself. We have
a number of customers who have complex conversation tracking needs.
They're tracking their own sessions.
5 Posted by tcarnell on 29 Jul, 2009 03:41 PM
ok, great - I'll try doing this. I will try using the combination of
request[userkey] + request[botkey] as key against which to store 'session' data.
thanks.
Support Staff 6 Posted by Adam Kalsey on 29 Jul, 2009 03:53 PM
The userkey is unique for each bot. So if you have the same AIM user
interacting with two bots, you'll have a different userkey for each
conversation.
7 Posted by mlucas on 14 Oct, 2010 07:30 PM
It looks like we've answered this for you, so we're going to mark this question as resolved. If you have any questions, you can re-open this issue or send a new one in and we'll be glad to help.
-Matt Lucas
IMified Support
mlucas closed this discussion on 14 Oct, 2010 07:30 PM.