microsoft
Create and manage ABS endpoints via Login UI (vs modal)
@vishwacsena @justinwilaby Question: when we "add" your ABS bots, are we downloading the .bot files locally? or connecting to them wherever they live through Azure? It affects step 5 below.
Basic flow: 1 - User selects "Add bots from Azure" (from Welcome page, My bots section or from File > Add bots from Azure) 2 - Modal with Azure sign in (email, password) 3 - Modal with list of all ABS bots (selectable by checkbox) 4 - User selects bots they want Emulator to remember and clicks Add button. 5 - Do we need a Save As modal for choosing a location? 6 - ABS bots now appear in Welcome, My bots section and in File > Open recent
@justinwilaby Updated flow on Invision: https://microsoft-fuse-design.invisionapp.com/d/main#/projects/prototypes/14863139
New sidebar design is also on InVision: https://microsoft-fuse-design.invisionapp.com/d/main#/projects/prototypes/15012340
Design in progress: https://microsoft-fuse-design.invisionapp.com/d/main#/projects/prototypes/15256213
@vishwacsena Will this work?
On Invision: "Select from Azure" selected "Configure manually" selected Entire flow for context
@mewa1024 - this does not seem right to me. On the outset, you are going to use this to add a local or a remote endpoint. May be these should be separated out as [+] -> add local endpoint (bot running locally) and add remote endpoint (bot running on azure).
For local endpoint, we should never show the ABS configuration since it is never relevant. We should also default the endpoint name to 'development' for this option.
For remote endpoint, we should follow along the same pattern as the other services - if you are logged in, show the list of endpoints available with an option to manually enter which would present the UX with all the fields above.
Thoughts?
@sgellock
@mewa1024 - any update? In any case we are not doing Login flows for 4.2. Moving this to 4.3.
@vishwac Hmm. We can separate out local and remote. Originally, we didn't distinguish between the two types of endpoint because we didn't want to add more UI to the New bot config menu:
I think this might affect the New Bot Config modal as well.