Cleaning - Cleaning departments and stations can now be made inactive
Cleaning departments and cleaning stations can be marked as "inactive"
Note: when a department is inactive the related stations are also considered as inactive.
Time administration - User access group field added to time record group
When a user access group is specified, it can only be accessed by members of this group.
In addition; a time record group can now be made "inactive"
Crossing orders - General improvements to crossing orders module
General improvements have been made to the crossing orders module:
•In the crossing provider definitions is now specified whether departure and arrival codes are mandatory, or only the external route code. When sending an edi booking, this will be checked. If not filled in (Crossings screen), an error will pop up for the user sending the booking.
•The procedure for sending consignment information has been improved. Sometimes the communication status was "Sent successfully", while the first part had an error and only the second part was successfully sent. This has been solved.
•It is now possible to change the crossing route on a crossing order that is not connected to the planning (within the same crossing provider account). This can be useful for crossing providers where it is possible to change a route while keeping the same booking number.
•The table valued functions dbo.SO_GetCrossingLegCustomsParty() and dbo.SO_GetLegCustomsParty() have been improved. These features now better take into account departure and arrival countries, to determine wether EU or UK EORI numbers should be used.
•Wiki articles have been written for general explanations and for how to handle things with crossing orders. See:
Crossing orders - ICS2 changes have been implemented in the Samskip edi connection
The changes required for ICS2 / new Safety & Security regulations have been implemented in the Samskip edi connection. Sender / Receiver data, as well as HS Codes will now be sent with the booking.
Crossing orders - Improvements in the P&O edi connection
A solution has been implemented for P&O edi bookings: in the main booking (without consignment details), a "dummy" weight will be sent for goods descriptions where the weight in Transpas is not filled in (yet).
This is because a value for the "weight" element is mandatory in the main booking, while this might be unknown at the time of making the booking. The actual weight will be provided via the "Send consignment information" functionality, where the actual weight is mandatory.
Crossing orders - Improvements in the Eurotunnel edi connection
A setting "ignoreUserMailAddress" has been added. A value of "1" (true) means: the border pass confirmation email will not be sent to the Transpas user that sent the booking. Instead, the default "borderPassConfirmMail" address will be used.
Crossing orders - ForSea Ferries has been changed to "Øresundslinjen"
The operator of the Helsingør <> Helsingborg line is not ForSea Ferries anymore, it is now Øresundslinjen. The API functionallity stays the same, only the URL has been changed, and an adjustment was necessary for the authentication token.
Crossing order - Improvements in the Finnlines / Grimaldi edi connection
The status of waitlisted bookings in the distant future will be checked less often, to prevent overloading of their API in cases of hundreds of waitlisted bookings in the next month for example.
Crossing orders - DFDS edi connection updated to latest version (v2.4.6)
The DFDS edi connection has been upgraded to the latest version.
The upcoming requirements for UK Safety & Security regulations have been implemented, like Seller & Buyer (including EORI numbers) for consignments.
Crossing orders - Scandlines - new features available in edi connection
Scandlines has added two features to their edi connection. These have been implemented into Transpas.
Crossing orders - Functionality for finding the "Departure" in Transpas improved
A parameter has been added to scalar function dbo.GetCrossingDepartureByDateTime and stored procedure dbo.sp_CrossingOrderExternalChange: @MarginInMinutes INT
This parameter can be used to apply a margin in finding the "Departure" in Transpas, when comparing the external departure date/time and departure date/time in Transpas.
For example, if the external departure date/time is "17:00", while the only Departure in Transpas is 16:30, a margin of 30 minutes is enough to regard this as the same departure.
Crossing orders - Improvements in the Finnlines / Grimaldi edi connection
The external departure date/time will now be processed to the crossing orders and planning (using a margin of 60 minutes).
When a booking has been moved to another departure (as detected in the process statuses procedure), it will be processed.
When updating or creating a Finnlines / Grimaldi booking, they determine the depature date/time based on the "External order id". If that number is wrong or has changed by Finnlines / Grimaldi, the associated departure date/time did not became clear in the planning in Transpas before.
This has been solved by this adjustment.