Improve UI feedback on asynchronous operations

[kolodziejczykm]

[Build]
17.6 2018/01/18

[Steps to reproduce]
I'm using a administrator account with technology provider / supplier roles

1. Subscribe to the OpenStack service
2. Go to "My subscriptions"
3. Click on the OpenStack service in "available for usage" table
4. In the service Details click and execute: Start -> Stop -> Resume

[Expected result]
User should be notified that he cannot perform "Resume" action on "Stopped" service.

[Observed result]
User is getting communicate: "The operation Resume has been successfully executed."

On the OpenStack dashboard service is still "Offline" after clicking resume.

[GoebelL]

@kolodziejczykm
Note that the operations are executed asynchronously and are potentially long running. To keep things simple this subscription details tab gives just little but immediate feedback. There is a separate view for tracking the operation queues. Check out account > operations.

[GoebelL]

More precisely, OSCM technical services can be composed with asynchronous as well as with synchronous operations. For this OpenStack service given here, all operations are defined as 'asynchronous'.
However the display in the subscription details is independent of the particular execution mode.
I do agree that the success message for execution is misleading at this point, in case the operation is scheduled but still pending.
Let's check if we can improve this. I guess this asynchronous case can be distinguished somehow. If so, I suggest to add a message with proper wording, like "The operation X has been scheduled successfully. See Account > Operations for details.".
(One note for implementation: Take care that the marketplace menu is localized. Incorporate a placeholder with the message for injecting the localized "Account > Operation" part).