API call to show error message to user in Web Portal, top-middle of the screen.

@grainovic , not sure if it fully covers your need, but when a command ends with an error, the error will be displayed on the top-middle of the screen as you described.

So the last step of a command that should fail might be raising an error with the relevant message.

This applies both to a topology driver (Authoring driver) command and to python scripts/drivers.

In addition, you can use the API to print messages to the output window. These messages can be html based, and be colored that way.

In the next major release, an indication on the button that opens the Output window will be available, similar to the indication on the Activity button, to notify the user about unread outputs.

See if these options help you.

Yaniv

I have to agree. Not being able to force a detailed error message into a web portal user's view is a HUGE problem. Yaniv, I like your suggestion of printing a message to the output window. That is an acceptable (and possibly superior) option to get an error message in front of a user. The only thing that's missing is an API call that will automatically open (raise) the output window.

• toOutputWindow("Error: Something went wrong!")
• outputWindow.Raise [This piece is missing!]

Depending on the level or nature of the error, the ability to use the API to call the same Error message notification used by the system would be of value. We get error messages when the code is bad, for example. But the ability to send that error message into the alert dialog box, also shows it in the activity feed for the Sandbox differently. Would be helpful o large deployments where CI/CD (or other scale automated launches take place) is using CloudShell.

In addition, if there were an API option to set the Sandbox condition/flag to 'Error True' then admins could possible filter the master sandbox listing in CloudShell by that flag. Being able to see the forrest for the trees in this case is always helpful for admins (it's a network issue all of these sandboxes share, that's why they are all erring out - stop that pipeline)

Hello Team Quali,

Status is still 'Active'. Any update?

Hi George,

I just wanted to get back to you on this idea.

Did you consider the work-around Yaniv suggested in this thread? Just to confirm, the error messages you are missing are from the setup/teardown scripts?

thanks,

Hi Pascal,

Yes, we end the command with an error to show the message. We see this as a workaround in absence of the API calls to control this aspect of UI. I'd like to have an API call to show messages while the command is still running.

Yes, we use the Output window, as well. I think that many users just ignore the output window.

Just to tack onto the conversation. An API call to programatticaly open/close the console output would be incredibly useful.

Hi,

Any update on this idea?