qvissak / ecommerce-supply-chain-management-chat-bot Goto Github PK

Typing log out successfully logs you out but the bot still knows your API key.

So that logicbroker keys do have have to be distributed - by typing "demo" the bot should default to Siena's API key.

Show line items for test0002 doesn't work but show line items for order test0002 works. Note the subtle difference.

Currently logout (yes/no) confirmation, help (hello) inquiry, and logicbroker api key verification randomization is used.

When using an order number greater than 10 characters, LUIS detects it as a LogicBroker Key

If you ask to show open orders, it gives you orders spanning a month, when it should default to two weeks. As well as giving it a range, it doesn't exactly work.

After logging in, verifying the API key, asking for some data, and then saying an utterance not recongized by luis - it defaults back to the hello.js dialog... but instead of prompting a "how can I help you" message - it asks for the API key yet again.

Bot should be able to support various dialogs from different files, should be able to ask the user for a Logicbroker API key, and should be able to show a help menu if the user does not know what to do

Upon querying the bot for certain orders of a given status for large date ranges, the bot throws an error not handled properly. The error throw is displayed to the user (raw) and breaks conversation flow.