Certified pick up v3.11.0
We are pleased to announce the release of Certified Pick up version 3.11.0!
Release date
This version is released on 19th of December 2023 to UAT.
This version is released on 27th of December to PRD.
Improvements
General
The logic for matching various messages with a commercial release has been optimised
All messages (Terminal Discharge, CCRM etc.):
If multiple identical active release rights are detected in CPu when processing a message (for example Terminal Discharge or CCRM), these messages will not be linked and feedback will be sent via notifications to the relevant entity sending the message. Identifiers used for detecting a “double” release right depend on the message that is being processed, below topic on “CCRM” describes the hierarchy for identifiers used in matching a CCRM meesage with a Commercial release. Documentation of notification to request sender in case of multiple release rights: https://documentation.nxtport.com/certified-pickup/notifications-for-terminal-operators#NotificationsforTerminalOperators-Multiplereleases
To give an example; in case there are 2 or more release rights in CPu with the same Equipment Number, Terminal and Stay Number, then the CCRM message will not be linked with the Commercial Release and Customs light is not updated.
Terminal Discharge / GateIn / GateOut and Release / Block / Unblock / Scanning:
StayNumber can be optionally provided in requests via API, when this identifier is present, it will be used to identify a Commercial Release. Adding StayNumber to these requests enables 1:1 matching with a commercial release, since EquipmentNumber + StayNumber is a unique key, using it is strongly recommended.
CCRM: hierarchy of identifiers used for matching a CCRM message with a commercial release has been adapted and is as follows;
Equipment Number and TerminalNxtEntityId and Stay Number
Equipment Number and TerminalNxtEntityId and IMO Number
Equipment Number and TerminalNxtEntityId
As [Terminal Operator or Ship Agent] I want to manually set the Customs light to green
When a CCRM message is not correctly sent by the Customs Authority, the Customs light remains “RED”. In such cases, the process agreed with Ship Agents and Terminal Operators can be used to determine whether the Customs light can be manually overruled. This features enables the Ship Agent and Terminal Operator to manually set the Customs light to “GREEN”.
As [any role] I want to search for notifications via API and UI in a time-window
This allows for more precise filtering on a specific date. Documentation per role:
UI
Transfer release right: “role” column has been added and it’s possible to transfer to any entity with Release Party or Transport Operator role
Accept + decline release right: “search” step with “terminal” filter has been removed, whenever the user clicks to accept or decline he sees the incoming release rights available to accept / decline
Release Party: “Bill of Lading” has been added as search parameter in transfer release right, revoke release right and search containers features
SCR
As Ship Agent using SCR I want to assign a pickup for Barge or Rail in CPu
As Ship Agent using SCR I want to revoke a pickup for Barge or Rail in CPu
Bugs
Customs light didn’t change to “PORTEQUALISATION” with color “YELLOW” when a GateIn message was sent by the Terminal Operator in an out-of-order scenario. Documentation for sending GateIn via API has been updated since “EquipmentStatus” attribute in the request was missing. Port Equalisation is solely set for Import containers.
When an Alfapass was assigned to a commercial release, this was visible as well for Ship Agent role. From now on, the assigned Alfapass is only visible to the Transport Operator.
Customs light notifications not delivered for Terminals with “releasedByDefault” config for Terminal Release light.