Certified pick up v4.0.0
We are pleased to announce the release of Certified Pick up version 4.0.0!
Release date
This version is released on 28th of May 2024 to UAT.
CPu users must validate the changes in this version, along with each user's most important business scenario’s, as communicated during the CPu user groups. For any help regarding demo data to test those scenario’s, this can be requested via support@nxtport.com. Feedback on this version can be given until 30th of June 2024 (16th of June 2024).
This version is planned to be released on 14th of July 2024 30th of June 2024 to PRD.
Improvements
Features
As First Release Party or Transport Operator, I want to revoke a release right that had been revoked from me before. Given an FRP / TRO is taking part in a new chain of release right transfers, they can revoke the release right from entities lower down the chain, as long as it hadn’t been revoked by a party higher up the chain.
As Ship Agent when I update the TerminalNxtEntityId for a commercial release and there’s an active commercial release for that EquipmentNumber, BillOfLadingNumbers and TerminalNxtEntityId, then I get a validation exception
As Terminal Operator I want releaseId in response from pickup validation for Truck (sync)
ExpirationDateTime has been added to the notification sent when a commercial release is created (ReleaseLightChanged for Commercial Release “UNKNOWN” → “RELEASED”)
Bug fixes
General
Pick Up light had status “unknown” instead of “revoked” when a pickup was “assigned” and the commercial release was revoked by the Ship Agent
API
Pickup validation for Truck and Barge/Rail;
in case the carrierId is provided in the request and this is wrong, multiple contradicting “isValid’s” were returned. Implementation has been adapted so that 1 isValid is returned, which will state “false” in case the carrierId is incorrect. CarrierId is used to identify the release right.
logic to determine the “status” in response had been aligned between endpoints for Truck and Barge/Rail;
in case at least 1 greenlight is red, the status will be “blocked”
in case all greenlights are green and 1 yellow, the status will be the corresponding value from the yellow greenlight, for example “selectedforscan”
in case all greenlights are green, the status will be “released”, please note that isValid can be “false” when the Alfapass or transport operator identity is incorrect, this will be clarified in the errorMessage.
Documentation:
No actions can be taken for archived commercial releases (e.g. delete, transfer, assign pick-up,…) and no notifications are sent to other stakeholders other than the organisation requesting the action
UI
Update terminal code via new experience UI: TerminalCode was not changed when updated within range of aliases for TerminalNxtEntityId
Overrule Customs light feature in UI: validity of token from authentication with Alfapass is respected
Cinvio payment for Transport Operators in UI: tokens debiting is activated in both old and new experience
Search archived containers in new experience UI:
“Archived” checkbox had been disabled for Forwarder and Transport Operator
Issue had been resolved with requesting container details for an archived container
Search invoiced container as Forwarder in new experience UI: issue resolved when filtering by Bill of Lading
“Switch to new experience” pop-up has been removed when logging in to CPu, users are logged in to new experience by default.
Notifications
Ship Agent received a double notification when a commercial release is updated
Customs ReleaseLightChanged to “DOCUMENTARYCONTROL” notification is sent only once
Release right holder didn’t receive a notification when a commercial release is deleted via EDI
Customs
NGPS > CCRM hierarchy not respected for “TRANSSHIPMENT” and “TRANSFER” CCRM messages. NGPS messages which result in “SELECTEDFORSCAN” are always leading to determine the Customs light.