It is not possible to end a data process monitoring at 12h00am (midnight). Let say we want to monitor 7h00pm until 12h00am, the web interface got an error: "The end time should be atleast 15 mins later than the start time.". We have to set 23h45 or 00:15. So it is impossible to get a result at 12h00am.
If we set 23h45, we don't have the last 15 minutes of the day included in the monitoring. If we set 00h15, the first 15 minutes of the new day is part of the new day, not the last day.
So our results are not exact if we take a look in the data monitoring dashboard.

Paging for suspended messages is broken.

Version 8.8.2116.2405

I have 68 suspended messages from friday afternoon.
When I go take a look at them only the 10 first messages are shown.
Arrows/Paging does not work.

Changing 10/25/50/100 (filter) does not work.

When you click on suspended messages on dashboard you are sent to "Data Access/ Message Box (Queries)

The default setting for the SQL-expression is 10 making paging useless unless you go and change original expresson first.

Only after that will the paging work.

I think it would be best if paging-setting (default or in user profile) would be much more convenient.

Cheers.

BAM activity viewing problems in Biztalk360 v 8.3

Problem 1 FILTERS

The most glaring error is this
"Is Greater than" /FAILED WITH ( Results in : "Backend server error. Response Code: 400, Message: Bad Request [more..]" )

Marcus Blomberg at ASCOM has reported this issue earlier in
[#17141] Data Access > BAM: Backend server error

Less glaring, but equally importantly, I tested each filter and

Equal to /Works
Not equal to /works
Starts with /Failed
Ends with /Failed
Contains /Sometimes works
Does not contain /Failed
Is Contained in /Sometimes works
Is Less than /Works
Is less than or equal to

Is Greater or equal to /Works

Suggestion: Make all filters work

PROBLEM 2 BAM Column widths.

For example, the text
"serviceCallError Violation of PRIMARY KEY constraint 'PK__CallColl__3214EC074841BA76'. Cannot insert duplicate key in object 'dbo.CallCollection'. The duplicate key value is (WR00172179). "
only shows up as "serviceCallE..."

It takes few minutes to widen the column enough to read it.
We have to re-widen the column for each search.
This makes the view useless.

Suggestion 1: Make the initial total width twice as wide.

Suggestion 2: Either save all widths, or let widths be set in a config file, preferably differently for each Report.

3 EXCEL

Export to Excel only exports a maximum of 1000 rows.
We need many more than 1000 rows.
Had this worked, we could have used Excel filters and widths instead.

Suggestion : Add 10,000 rows to drop down box.

4 MULTILE FIELDS
Choosing multiple fields is tricky.
(This is a minor problem)

Suggestion: Make the rows choosable with a stroke of the key, like ALT-4 or add cumulatively with Shift, down-arrow.