When restarting many Artifacts (Ports or Host Instances) the Expected State should be clearly visible in order to avoid wrong manipulation (for instance: restarting a port which should remain stopped).
Also, the Application or Artifcat should be Red only if an artifact is not in the Expected State, not if an artifact is stopped (which could be the Expected State).

From time to time I find myself wandering through the Alert History. At that times I often miss the capability to:
- Being able to see all records in the Alert History
- Have filtering capabilities like we know from Message Box queries and Graphical Flow
- Being able to show the actual mail which is being sent (I noticed this is in the database)

We use the API for managing BizTalk 360 from other 3rd party applications such as TFS. To prevent BizTalk 360 starting up an application mid deployment we have to use the api to get the full alarm config, and send it back with the "isAlertDisabled" flag off and the same to reenable it. Having a seperate method to enable/disable an alarm would be much simpler

We use SSO heavily for storing runtime configuration which currently can only be edited by SSO admins. Being able to make this available for the business or super users to edit would be useful

We have one requirement, customer wants to notify them, if we don’t have file to process. In this situation we can enable the Process Monitoring to notify them if we don’t have file to process. But this alarm has one drawback, it generates the critical error with failed message on configured port. That make sense for technical person but not for everyone. It would be nice, if we have capability to send the custom message in that situation to notify the customer.

Rather than all options under the 'set data filter' being 'and', would be nice to have an 'or' feature and the option to have multiple options.

i.e.
application is equal to ZZZ
AND

  fault code is equal to XXX

OR

  fault code is equal to YYY 

and

Currently you can see individual Message information with respect to tracking in the Graphical message Flow view in BT360.
I would like to see some reporting to do with tracking information.

Immediate email notification for threshold violation followed by persist duration before next email

When RL goes down, immediately 1 email,
wait for 10 minutes, & then the next email should go out.

The new maintenance window has no option to just remove and not delete the entire maintainence window

We use EDI a lot and are looking forward to some EDI enhancements
EDI parties editing information in BT360

Paging is good and bad. Good for server load, keeping the list short and manageable - but Export to Excel seems more broken with this feature

I do export the list to Excel and print it out and hang it on my whiteboard
With a proper description on each application it is very easy to see what each application does.

Please add the option to save entire list of application to excel rather than the paginated list.

We can group artifacts to support an outage. For example we can support an outage to an email system by grouping Artifacts that are pointed to that system and then click a "button" to disable all the send/receive ports pointing to that system. It integrates through SCOM using an API to but those same porting in maintenance mode, also.

Hi,
Is it possible to operate Servicebus queues from the Operation dashboard like reading the content of the queue, dead-letter queue and resubmit.

More control for the end user when downloading CSV Files.

this is because some people want to open the CSV in another way or within another applciation (Notepad, Notepad++, or.......)

When we create new host instance , If a host instance is not tied to an application, user cannot see the application. (host instance view for end user)

The ability to save error information along the suspended message.

It would be nice for Invalid files (not validated in the incoming pipeline) or suspended, that you could choose to add the file to the alarm mail sent.