Integration nav discoverability

[syndesis-bot]

@sjcox-rh	2017-10-11

This is in response to Christina Lin's email in regards to going back and forth within an integration workflow.

I know the intent is to have the ability to click on start and finish within the integrations panel to revisit that step of the workflow, but the current build doesn't allow that so that could be a big part of her confusion.

Also, just want to make sure that the integration panel utilizes hover states on items that are clickable (start and finish connection and sub items). That would give an additional hint to the user that you could interact with those items.

Just met with @dongniwang and @amysueg and we discussed potentially bringing back the full sub menus under each connection within the integration panel (shown below).

This way the user could click on each sub step as any time (when the menu is expanded) to go back and change something. Currently we hide additional sub steps once the user has completed them, but by showing them, it might be more obvious that you can interact with that panel to go back and forth.

Also, would it be possible to always show the "cancel" button in the toolbar? This way, if all else fails, it's easy to exit the flow and start over.

[syndesis-bot]

@rhuss	2017-10-12

Sounds like a good solution to me. I wonder whether we can make the use case "Oh shit, I've chosen the wrong connection and what to cancel this (without cancelling the whole integration)" more accessible. I know, this could be achieved by just pressing "Choosing a connection" again, but maybe an extra "Cancel connection" button on step 2 and 3 (choose an action & configure action) is more intuitive?

BTW, is this an older screenshot ? Because I think it mixes "Connectors" and "Connections" here (this are different entities, this page is only about "Connections"). Also the button "Create API Connector" confuses me here a bit, because I wouldn't expect it at this place.

[syndesis-bot]

@gashcrumb	2017-10-27

So what should the hover states on the left panel look like? Even with that the user needs to hover to know that those can be clicked. Maybe those items should look more like links?

Note that some of this stems from the summit demo when we took out the ability to go backwards through the page flow. I think the main reason was that this was done via a Back button in a sort of wizard style, but that button lived in the main toolbar (where the Cancel button is in the mockup) and then it wasn't clear what was going to happen when you clicked it, i.e. does it go back a page, or cancel out of the editor or ?

Now, when you revisit a connection (click on a configured connection in the editor) we currently go right to the action configuration if it's available. Should this instead go to the action selection page? Or even the connection select page? Should we consider having a summary page perhaps for this case that kinda branches the page flow out, i.e. I click on a connection and go to a page that has some kind of summary and then links to change connection, action or go to the connection configuration?

Or maybe each page in the flow should maintain a list of entries that link back to previous pages like underneath the page title?

[syndesis-bot]

@gashcrumb	2017-10-27

Also something to consider -> #249

[mcada]

Can we please continue the discussion and decide what to do about it? It is kind of inconvenient that if you missclick start or finish step while creating integration you have to actually create and delete the step if you want to change it.

[deeleman]

Can we please continue the discussion and decide what to do about it?

+1. We'll require a more specific spec in regards of what needs to be done from an UI POV.

@amysueg once the UXD folks agree on the course of action, could you open a new issue, superseding this one (hence closing this one and replicating its labels there), with an outlined list of UI changes and expected interactions?

This way we can benefit from the new issue description format, which makes things more clear to us UI folks from a delivery POV. You ca also edit the current description with the new acceptance criteria here.

Thanks! :)

[amysueg]

@deeleman yes, sounds good.

I believe this goes to something @kcbabo has spoken about before, which is that after GA and once we have actual customer feedback, we may need to revisit some of the basic assumptions and behaviors of the IVP.

fyi @dongniwang @sjcox-rh

[paoloantinori]

hey guys, can you update on the progress on this? also, could you remove the "tp1" reference in the description, that is misleading and shouldn't appear there.

[amysueg]

UXD met to discuss the approach.

We noted that "add a step" and "add a connection" when in the middle of the integration flow include a Cancel button as an option within each step as this example shows:

That Cancel button is currently missing from the Start & Finish connection steps. Adding the Cancel button on each panel will address the problem raised in this issue. For example, add the Cancel button to the left of the Choose Action button here:

In addition, add the Cancel button in the upper right on the breadcrumb bar when creating the integration. At any given point, the Cancel button is available so that the user can exit the process.

@sjcox-rh @dongniwang

[dongniwang]

Closing this issue since new design is in place per above comment.