Requests List
Using the Requests List
The Requests list holds every accessible booking note, at any status, however it was created. It is the main working surface of the module, and the only place with search, filters, saved views and export.
Both roles see the same columns. What differs is which records appear: a Shipper sees their own organization's booking notes, a Freight Forwarder sees every booking note addressed to them across all the Shippers they work with. See Roles and Permissions.
What is on the page
- The table. One row per booking note. Around thirty columns are available, not all shown by default. Every one is documented in What Each Column Means.
- Column search. Each column header has its own search or filter control, matched to the type of data in it.
- Global search. At the top right, searching across content and fields at once.
- Created Date filter. A quick filter for narrowing by when booking notes were created.
- Reset and Refresh. Reset clears every applied filter and search. Refresh reloads the data without losing the current setup.
- View controls. For changing which columns appear and saving that arrangement.
- Export. Downloads the current contents of the list as CSV or Excel.
- + New Request. Starts a new booking note. See How to Create a Booking Note.
Reading a row
Three columns give most of what is needed at a glance:
- Portal Booking ID — the identifier assigned by Open Nexus. It is a link; select it to open the booking note.
- Status — where the booking note is in its lifecycle, and therefore what can be done with it. See What Each Status Means.
- Source — whether it was typed in manually, uploaded as a document, or received by email.
If Source is Upload, the File Name column shows the document the note came from. If it is Email, Sender shows who sent it.
Finding a booking note
Global search
The search box at the top right searches across the content and fields of all accessible booking notes at once. It is the right tool when something about the booking note is known but not which column holds it — a reference number, a port, a company name.
It covers, among others: File Name, Status, Source, Sender, External System ID, Transmission Status, Consignee, Loading Port, Destination Port, Cargo Ready Date, Latest Shipping Date and Shipper.
Column search
Every column has its own search control in the header, matched to the type of data it holds:
| Column type | Control |
|---|---|
| Text — Consignee, Shipper Reference, File Name | Type to search within that column |
| Date — CRD, Latest Shipping Date, Created At | Pick a date or range |
| Selection — Status, Source, Transmission Status | Choose from the available values |
Column searches apply independently. Filtering Status to Pending Review does not restrict what can then be searched in the Shipper column.
Filters are additive
Global search, column filters and the Created Date filter all apply at the same time, narrowing the list further with each one. Setting Status to Pending Review, Loading Port to Hong Kong and then typing a reference in global search leaves only the booking notes matching all three.
This is worth remembering when a booking note seems to have disappeared. In most cases a filter from earlier is still applied. Reset clears everything at once.
Filters stay applied until they are reset or the session changes. A combination needed permanently should be saved as a view instead.
Saving views
The list opens with a standard set of columns covering identification, participants, route and dates. This default is a starting point, not a limit — every column in What Each Column Means can be added.
A view is a saved arrangement: which columns are shown, in what order, with which filters applied.
How to build one
- Add or remove columns until the list shows what is needed.
- Apply any filters and column searches that should be part of the view.
- Save the arrangement and give it a name that describes what it is for.
Saved views persist between sessions. Switching between them changes both the columns and the filters in one action.
Views worth setting up
Awaiting decision (Freight Forwarder) — Status filtered to Pending Review, sorted oldest first, showing Shipper, Consignee, ports and CRD. This is the review queue.
Open booking notes (Shipper) — Status filtered to Draft and Pending Review, showing Consignee, Freight Forwarding Agent, CRD and Latest Shipping Date. Everything not yet settled.
Needs attention — Status filtered to Failed, showing File Name, Source and Sender. See How Documents and Emails Are Read.
Sailing soon — CRD filtered to the next two weeks, showing ports, container types and TEU.
Exporting to a spreadsheet
- Set up the list to show the required data: adjust columns, apply filters and searches.
- Select the export control and choose CSV or Excel.
Three rules govern the contents, all worth knowing before exporting:
Only the columns currently visible. A column not in the current view is not in the file. If something is missing, add the column and export again.
Only the rows left after filtering. Every filter and search narrows the export the same way it narrows the screen. Check what is applied before exporting something intended for sharing.
All matching rows, not just the ones on screen. Pagination does not limit the export. If the filters match four hundred booking notes and the first fifty are on screen, all four hundred are exported.
Excel keeps formatting and suits a file that will be read directly. CSV is plain text and suits loading into another system.
Build the view first, then export. A dedicated saved view for a recurring report removes the risk of exporting with last month's filters still applied.
Row actions
Each row ends with a set of icons. Hovering over one shows its label. Only actions permitted by the current role are enabled.
| Action | What it does |
|---|---|
| View | Opens the booking note in the current window |
| Open in a separate window | Opens it in a new window, leaving the list untouched |
| Duplicate | Creates a new booking note using this one's data |
Open in a separate window is useful when working through a filtered list: open a booking note, deal with it, close the window, and the list is unchanged — same filters, same scroll position.
Duplicating a booking note
Duplicate creates a new, editable booking note carrying the same information as an existing one. It saves re-entering data for a shipment that closely resembles a previous one. Available to both roles, at any status, including Approved and Rejected.
Copied: all booking note form data — participants, references, commercial terms, route, dates, containers and cargo entries.
Not copied:
| Not copied | Why |
|---|---|
| Uploaded documents and attachments | The new note is its own record, not tied to the original's source |
| Source document references | Same reason |
| Approval or rejection information | The new note has not been reviewed |
| Transmission status and history | Nothing has been transmitted for it |
| Processing history | It has not been through extraction |
The result is a new booking note with its own Portal Booking ID, in the initial editable status, opened ready for changes. The original is untouched, whatever its status.
Duplicating a rejected booking note is the normal way to correct and resubmit: the rejected record stays intact as history, and the duplicate is a fresh, editable note. See What Each Status Means.