...

The dashboard shows a summary of all the booking types in one long paged list. Searching is available as well as sorting by fields. It contains only non-closed bookings.

...

Image Added

Display

Hyperlinks

A hyperlink exists on the Sales Order so that the user can open a booking in a new page.

...

Bookings can be sorted by header columns.

Filtering

Persistence

Filtering may be simple to start with, eg. filter on items which need attention, eg. dispatched but pre-alert not sent. Ultimately filtering should include countries, work types, statuses etc.is persistent for a user, ie. any filter saved will be saved and applied whenever the users goes back to the dashboard.

Implementation

Filtering is implemented in two stages. Full filtering includes the following:

• Country

• City

• Booking Type

• Booking Status

• Delivery Date From

• Delivery Date To

“Clear All” button clears the filters completely

Filter toggle toggles whether or not the filters are applied

Phase 1 Filtering

Phase 1 Filtering will include the following which can be selected individually as one item

• Booking Type

• Booking Status

• Delivery Date From

• Delivery Date To

Phase 2 Filtering

Phase 2 filtering will include all selection fields as in full filtering including the ability to

• select more than one item from a filter

• add and remove specific selections individually

Additional Filter on Completion Date

Enable filtering on completion date range

...

Alert Notifications Panel

Errors in the booking process where attention is required will be shown at the top of the booking dashboard. The sorting order will be those where the error is generated most recently at the top, with an ability to hide the rows if they have been dealt with or are not very important. Hidden notes can be shown again at any time using the “Hidden Notes” toggle.

Errors may be stored across all entities, including bookings. There is an internal code for the attention type, eg. Pre-Alert send failure. Associated with the internal code is a human-readable description, eg.

• Code = “Pre-Alert”, Error = “Fields missing in Dispatched”

• Code = “Pre-Alert”, Error = “Email failed to send”

• Code = “Booking Confirmation”, Error = “Booking Confirmation due”

• Code = “Booking Confirmation”, Error = “Scheduled date later than dispatched + 10 days”

• Design change to use pills for read/hidden

  Jira Legacy
  server System JIRA serverId b157ffa3-650f-3eac-ac6a-49d6a4f1db87 key WG-779

...

Archive Dashboard

This is the same layout as the Active Orders Dashboard. The only difference is the booking shown which are closed bookings only.

...