After user clicks "Create service instance", there's no feedback about success or failure #457
Comments
This is a component of #763 |
Thinking of waiting on this until this page is further developed. |
@thisisdano @vz3: @msecret and I just discussed this. Given that we won't be picking up the Marketplace page in this PI, what are your thoughts of designing an MVP success/failure state that could be included in the current page here? |
From the marketplace prototype: Button default state Buttons replaced with loading indicator Success message appears. In success case, the action panel could be removed after ~2sec. Or an error message, with an opportunity to try again, or to cancel. (Error message should be more verbose, descriptive than this "friendly" one. |
This was completed by #944 |
👍 confirmation appears after success. |
I just tried this on staging, and this confirmation of success seems to disappear after only a couple of seconds. Could it stick around until it gets dismissed? Also the created message gets a few extra capital letters due to styling (they're not in the code here). |
That suggestion sounds good to me. I agree it kind of flashes with limited time to read and comprehend it. I'd put that in a new issue though. I think there are a few issues hanging around regarding messaging for success/failure and forms. |
Thanks, filed a new issue here: #991 |
Currently when you go to an org's Marketplace and fill out the "Create service instance" form, you click the final "Create service instance" button, and then the form disappears. You don't get feedback on whether you successfully created the instance, and you don't get instructions for what to do next.
Let's add helpful feedback here, so that users know that it worked (and what to do next). After successful creation, let's provide a note saying something like this:
Or after an unsuccessful effort at creation, something like this:
Some notes from Slack:
Notes from subsequent discussion:
Implementation notes:
Acceptance criteria:
The text was updated successfully, but these errors were encountered: